2620:74:2a::/48
Verisign Anycast US 2PAS397195
Verisign Anycast US 0OAS396555
Verisign Anycast SE 0DAS396602
Verisign Anycast US 2UAS397203
Verisign Anycast US 0WAS396563
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/48 block
Visibility
19 of 65 vantage points
RPKI
Registry
USAllocated 6th May 2010
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 AS396555seen on 316 paths from 56 vantage points
- Peer of AS7342seen on 6,449 paths from 147 vantage points
- Peer of AS2914seen on 445,995 paths from 6 vantage points
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, UK105157342129935280This path
- Sao Paulo3965557342291435280Shown above
- Singapore39720373426939132337This path
- Amsterdam1051573421299250918298This 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
29%
Seen by 19 of 65 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
- 6th May 2010
- Allocation block
- 2620:74:20::/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 |
|---|---|---|
| 2620:74:2a::/48 | AS10515 | /48 |
| 2620:74:2a::/48 | AS19836 | /48 |
| 2620:74:2a::/48 | AS20172 | /48 |
| 2620:74:2a::/48 | AS20362 | /48 |
| 2620:74:2a::/48 | AS20431 | /48 |
| 2620:74:2a::/48 | AS211369 | /48 |
| 2620:74:2a::/48 | AS21313 | /48 |
| 2620:74:2a::/48 | AS22547 | /48 |
| 2620:74:2a::/48 | AS25485 | /48 |
| 2620:74:2a::/48 | AS27544 | /48 |
| 2620:74:2a::/48 | AS32651 | /48 |
| 2620:74:2a::/48 | AS36616 | /48 |
| 2620:74:2a::/48 | AS36617 | /48 |
| 2620:74:2a::/48 | AS36618 | /48 |
| 2620:74:2a::/48 | AS36619 | /48 |
| 2620:74:2a::/48 | AS36620 | /48 |
| 2620:74:2a::/48 | AS36621 | /48 |
| 2620:74:2a::/48 | AS36622 | /48 |
| 2620:74:2a::/48 | AS36623 | /48 |
| 2620:74:2a::/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 |
|---|---|---|---|
| 2620:74:2b::/48 | 65.5k × /64 | AS21313Verisign Anycast FR 0A | 3/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS36629Verisign Anycast DE 0L | 15/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS36631Verisign Anycast US 1A | 3/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS40717Verisign Anycast GB 0J | 3/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS396550Verisign Anycast GB 0B | 2/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS396566Verisign Anycast NL 0L | 23/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS396567Verisign Anycast NL 0M | 1/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS396583Verisign Anycast US 1Q | 3/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS396600Verisign Anycast FR 0G | 1/65 |
| 2620:74:2b::/48 | 65.5k × /64 | AS396604Verisign Anycast SG 0G | 3/65 |
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.