2001:500:122::/48
Verisign Anycast DE 0FAS397198
Verisign Anycast US 1IAS396574
Verisign Anycast JP 0EAS396605
Verisign Anycast DE 0PAS397209
Verisign Anycast US 2YAS397206
Verisign Anycast GB 0GAS397193
Verisign Anycast FR 0GAS396600
Verisign Anycast US 1JAS396575
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/48 block
Visibility
16 of 62 vantage points
RPKI
Registry
USAllocated 21st April 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS19836seen on 305 paths from 89 vantage points
- Peer of AS7342seen on 473 paths from 22 vantage points
- Peer of AS6939seen on 309,709 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
- Amsterdam1983673426939213151Shown above
- London, UK198367342900251907This path
- Sao Paulo198367342719532590This path
- Singapore1983673426939132337This 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
26%
Seen by 16 of 62 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- ARIN — North America
- Country
- United States
- Allocated
- 21st April 2015
- Allocation block
- 2001:500:120::/43
- 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 |
|---|---|---|
| 2001:500:122::/48 | AS10515 | /48 |
| 2001:500:122::/48 | AS19836 | /48 |
| 2001:500:122::/48 | AS20172 | /48 |
| 2001:500:122::/48 | AS20362 | /48 |
| 2001:500:122::/48 | AS20431 | /48 |
| 2001:500:122::/48 | AS211369 | /48 |
| 2001:500:122::/48 | AS21313 | /48 |
| 2001:500:122::/48 | AS22547 | /48 |
| 2001:500:122::/48 | AS25485 | /48 |
| 2001:500:122::/48 | AS27544 | /48 |
| 2001:500:122::/48 | AS32651 | /48 |
| 2001:500:122::/48 | AS36616 | /48 |
| 2001:500:122::/48 | AS36617 | /48 |
| 2001:500:122::/48 | AS36618 | /48 |
| 2001:500:122::/48 | AS36619 | /48 |
| 2001:500:122::/48 | AS36620 | /48 |
| 2001:500:122::/48 | AS36621 | /48 |
| 2001:500:122::/48 | AS36622 | /48 |
| 2001:500:122::/48 | AS36623 | /48 |
| 2001:500:122::/48 | AS36624 | /48 |
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 |
|---|---|---|---|
| 2001:500:123::/48 | 65.5k × /64 | AS19836Verisign Anycast US 2M | 1/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS36623Verisign Anycast JP 0D | 2/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS40717Verisign Anycast GB 0J | 2/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS211369Verisign Anycast FR 0E | 1/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS396545Verisign Anycast US 0L | 1/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS396549Verisign Anycast GB 0A | 19/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS396550Verisign Anycast GB 0B | 1/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS396555Verisign Anycast US 0O | 3/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS396566Verisign Anycast NL 0L | 2/62 |
| 2001:500:123::/48 | 65.5k × /64 | AS396574Verisign Anycast US 1I | 2/62 |
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.
Routing data derived from RouteViews MRT archives and public registry data.