185.30.221.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
RUAllocated 17th July 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS60437seen on 211 paths from 80 vantage points
- Peer of AS57420seen on 261 paths from 80 vantage points
- Peer of AS43298seen on 3,059 paths from 91 vantage points
- Peer of AS35598seen on 8,340 paths from 130 vantage points
- Peer of AS20485seen on 4,730 paths from 2 vantage points
DEOne path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.
Every path we see
- London, UK6043757420432981374098529This path
- Amsterdam6043757420432983559820485213151Shown above
- Singapore60437574204329835598202984174132337This path
- Sao Paulo6043757420432983559820298412993356266213This path
- Oregon, US604375742043298355982029846762693920130This path
Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.
Route visibility
100%
Seen by 80 of 80 full-feed vantage points
Globally propagatedObserved at 5 of our collectors.
What this percentage counts
The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.
It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.
Registry and RPKI
- RIR
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Russia
- Allocated
- 17th July 2013
- Allocation block
- 185.30.220.0/22
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 185.30.220.0/22 | 1k | AS60437FORA-BANK Joint-Stock Commercial Bank | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 185.30.220.0/24 | 256 | AS60437FORA-BANK Joint-Stock Commercial Bank | 19/80 |
History
- AS6043712th August 2026 — present
Why these dates start where they do
A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.
Open 185.30.221.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.