2001:500:7967::/48
Verisign Anycast GB 0HAS397194
Verisign Anycast JP 0CAS397199
Verisign Anycast FR 0GAS396600
Verisign Anycast SE 0DAS396602
Verisign Anycast US 0LAS396545
Verisign Anycast US 1QAS396583
Verisign Anycast SG 0GAS396604
Verisign Anycast US 0KAS396544
Verisign Anycast FR 0BAS396546
Verisign Anycast NL 0AAS396613
Announced by more than one origin AS (MOAS).
AS397193 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Subnets
/48 block
Visibility
12 of 65 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 London, UK.
Seen from London, UK
- Peer of AS397194seen on 232 paths from 23 vantage points
- Peer of AS7342seen on 6,730 paths from 147 vantage points
- Peer of AS1299seen on 512,950 paths from 6 vantage points
SE
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
- London, UK3971947342129935280Shown above
- Sao Paulo3965457342645335280This path
- Singapore3663173426939132337This path
- Amsterdam39660073421299250918298This 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
18%
Seen by 12 of 65 full-feed vantage points
Seen by few vantage pointsObserved at 4 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:7967::/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:7967::/48 | AS10515 | /48 |
| 2001:500:7967::/48 | AS19836 | /48 |
| 2001:500:7967::/48 | AS20172 | /48 |
| 2001:500:7967::/48 | AS20362 | /48 |
| 2001:500:7967::/48 | AS20431 | /48 |
| 2001:500:7967::/48 | AS211369 | /48 |
| 2001:500:7967::/48 | AS21313 | /48 |
| 2001:500:7967::/48 | AS22547 | /48 |
| 2001:500:7967::/48 | AS25485 | /48 |
| 2001:500:7967::/48 | AS27544 | /48 |
| 2001:500:7967::/48 | AS32651 | /48 |
| 2001:500:7967::/48 | AS36616 | /48 |
| 2001:500:7967::/48 | AS36617 | /48 |
| 2001:500:7967::/48 | AS36618 | /48 |
| 2001:500:7967::/48 | AS36619 | /48 |
| 2001:500:7967::/48 | AS36620 | /48 |
| 2001:500:7967::/48 | AS36621 | /48 |
| 2001:500:7967::/48 | AS36622 | /48 |
| 2001:500:7967::/48 | AS36623 | /48 |
| 2001:500:7967::/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.