2620:74:20::/48
Verisign Anycast GB 0AAS396549
Verisign Anycast US 0OAS396555
Verisign Anycast NL 0LAS396566
Verisign Anycast US 2UAS397203
Verisign Anycast GB 0BAS396550
Verisign Anycast FR 0EAS211369
Verisign Anycast US 1MAS396576
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/48 block
Visibility
19 of 64 vantage points
RPKI
Registry
USAllocated 6th May 2010
AS paths to this prefix
One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.
- Amsterdam36625734232590This path
- London, UK396549734235280This path
- Singapore3965667342132337This path
- Sao Paulo201727342645335280This 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
30%
Seen by 19 of 64 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:20::/48 | AS10515 | /48 |
| 2620:74:20::/48 | AS19836 | /48 |
| 2620:74:20::/48 | AS20172 | /48 |
| 2620:74:20::/48 | AS20431 | /48 |
| 2620:74:20::/48 | AS211369 | /48 |
| 2620:74:20::/48 | AS21313 | /48 |
| 2620:74:20::/48 | AS22547 | /48 |
| 2620:74:20::/48 | AS25485 | /48 |
| 2620:74:20::/48 | AS27544 | /48 |
| 2620:74:20::/48 | AS32651 | /48 |
| 2620:74:20::/48 | AS36616 | /48 |
| 2620:74:20::/48 | AS36617 | /48 |
| 2620:74:20::/48 | AS36618 | /48 |
| 2620:74:20::/48 | AS36619 | /48 |
| 2620:74:20::/48 | AS36620 | /48 |
| 2620:74:20::/48 | AS36621 | /48 |
| 2620:74:20::/48 | AS36622 | /48 |
| 2620:74:20::/48 | AS36623 | /48 |
| 2620:74:20::/48 | AS36624 | /48 |
| 2620:74:20::/48 | AS36625 | /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:21::/48 | 65.5k × /64 | AS27544Verisign Anycast NL 0N | 2/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS32651Verisign Anycast NL 0H | 1/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS36631Verisign Anycast US 1A | 9/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS396544Verisign Anycast US 0K | 1/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS396545Verisign Anycast US 0L | 3/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS396551Verisign Anycast GB 0C | 3/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS396560Verisign Anycast DE 0G | 5/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS396583Verisign Anycast US 1Q | 3/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS396609Verisign Anycast US 1Z | 1/64 |
| 2620:74:21::/48 | 65.5k × /64 | AS396615Verisign Anycast NL 0D | 8/64 |
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.