2001:500:30ff::/48
Verisign Anycast GB 0AAS396549
Verisign Anycast NL 0LAS396566
Verisign Anycast US 0OAS396555
Verisign Anycast US 0JAS396543
Verisign Anycast GB 0BAS396550
Verisign Anycast NL 0MAS396567
Verisign Anycast US 2UAS397203
Verisign Anycast US 1MAS396576
Verisign Anycast FR 0DAS396547
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/48 block
Visibility
26 of 62 vantage points
RPKI
Registry
USAllocated 18th May 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Adjacentseen on 824 paths from 75 vantage points
- Peer of AS7342seen on 24 paths from 3 vantage points
- Peer of AS34549seen on 716,762 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, UK396549734251907This path
- Singapore3965497342132337This path
- Amsterdam396549734234549213151Shown above
- Sao Paulo3965557342719532590This 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
42%
Seen by 26 of 62 full-feed vantage points
Partially propagatedObserved at 3 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
- 18th May 2010
- Allocation block
- 2001:500:30ff::/48
- 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:30ff::/48 | AS10515 | /48 |
| 2001:500:30ff::/48 | AS19836 | /48 |
| 2001:500:30ff::/48 | AS20172 | /48 |
| 2001:500:30ff::/48 | AS20362 | /48 |
| 2001:500:30ff::/48 | AS20431 | /48 |
| 2001:500:30ff::/48 | AS211369 | /48 |
| 2001:500:30ff::/48 | AS21313 | /48 |
| 2001:500:30ff::/48 | AS22547 | /48 |
| 2001:500:30ff::/48 | AS25485 | /48 |
| 2001:500:30ff::/48 | AS27544 | /48 |
| 2001:500:30ff::/48 | AS32651 | /48 |
| 2001:500:30ff::/48 | AS36616 | /48 |
| 2001:500:30ff::/48 | AS36617 | /48 |
| 2001:500:30ff::/48 | AS36618 | /48 |
| 2001:500:30ff::/48 | AS36619 | /48 |
| 2001:500:30ff::/48 | AS36620 | /48 |
| 2001:500:30ff::/48 | AS36621 | /48 |
| 2001:500:30ff::/48 | AS36622 | /48 |
| 2001:500:30ff::/48 | AS36623 | /48 |
| 2001:500:30ff::/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
No prefix of the same length in the same parent block is announced.
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.