217.66.128.0/21
AS24961 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/21 block
Visibility
76 of 76 vantage points
RPKI
Registry
DEAllocated 6th November 2000
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS13301seen on 443 paths from 139 vantage points
- Peer of AS24961seen on 4,275 paths from 33 vantage points
- Peer of AS3356seen on 839,047 paths from 6 vantage points
US
FROne 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
- Amsterdam13301249618298This path
- London, UK13301249618529This path
- Singapore133012496123673This path
- Sao Paulo1330124961335635280Shown above
- Oregon, US1330124961855142013This 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 76 of 76 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
- Germany
- Allocated
- 6th November 2000
- Allocation block
- 217.66.128.0/21
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 217.66.128.0/21 | AS13301 | /21 |
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 |
|---|---|---|---|
| 217.66.136.0/21 | 2k | AS41998NetCom BW GmbH | 76/76 |
History
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 217.66.128.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.