91.217.21.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
RUAllocated 17th August 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS39494seen on 222 paths from 142 vantage points
- Peer of AS44112seen on 80 paths from 80 vantage points
- Peer of AS48287seen on 2,537 paths from 106 vantage points
- Peer of AS5537seen on 571 paths from 67 vantage points
- Peer of AS39561seen on 836 paths from 61 vantage points
- Peer of AS59796seen on 12,523 paths from 109 vantage points
- Peer of AS33891seen on 3,787 paths from 2 vantage points
SK
DE
AEOne 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
- Amsterdam394944411248287199599123896939213151This path
- London, UK39494441124828755373956159796338918529Shown above
- Sao Paulo39494441124828755373956159796338913356→ ⋯This path
- Singapore3949444112482875537395615979633891132337This path
- Oregon, US39494441124828755373956159796338913257→ ⋯This 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 August 2010
- Allocation block
- 91.217.20.0/23
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 91.217.20.0/24 | 256 | AS48287JSC "RU-CENTER" | 80/80 |
History
- AS3949412th 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 91.217.21.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.