SUBNET.IM

2001:500:127::/48

Verisign Anycast GB 0AAS396549

Verisign Anycast DE 0EAS397197

Verisign Anycast JP 0EAS396605

Verisign Anycast GB 0HAS397194

Verisign Anycast US 0OAS396555

Verisign Anycast US 2UAS397203

Verisign Anycast JP 0DAS36623

Verisign Anycast US 1IAS396574

Verisign Anycast US 2RAS397200

Verisign Anycast NL 0LAS396566

Verisign Anycast GB 0JAS40717

Verisign Anycast GB 0GAS397193

Verisign Anycast GB 0BAS396550

Verisign Anycast US 0LAS396545

Verisign Anycast US 2MAS19836

Announced by more than one origin AS (MOAS).

At a glance

Subnets

65,536 × /64

/48 block

Visibility

31%

19 of 62 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 21st April 2015

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.

OriginVantage points
AS path graph: 4 observed paths to 2001:500:127::/48, fanning out from AS396549, AS396555, AS397197 toward the vantage points that see it. Each path is written out in full beneath the graph.AS397197Verisign Anycast …OriginAS7342VeriSign Infrastr…AS213151Christian ElsenAS51907Kanton ZugAS396549Verisign Anycast …OriginAS7342VeriSign Infrastr…AS132337AxclusiveAS396555Verisign Anycast …OriginAS7342VeriSign Infrastr…AS7195EdgeUnoAS32590Valve Corporation
  1. Amsterdam3971977342213151This path
  2. London, UK397197734251907This path
  3. Singapore3965497342132337This path
  4. 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

31%

Seen by 19 of 62 full-feed vantage points

Seen by few vantage points

Observed 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

Route Origin Authorisations covering 2001:500:127::/48
ROA prefixAuthorised originMax length
2001:500:127::/48AS10515/48
2001:500:127::/48AS19836/48
2001:500:127::/48AS20172/48
2001:500:127::/48AS20362/48
2001:500:127::/48AS20431/48
2001:500:127::/48AS211369/48
2001:500:127::/48AS21313/48
2001:500:127::/48AS22547/48
2001:500:127::/48AS25485/48
2001:500:127::/48AS27544/48
2001:500:127::/48AS32651/48
2001:500:127::/48AS36616/48
2001:500:127::/48AS36617/48
2001:500:127::/48AS36618/48
2001:500:127::/48AS36619/48
2001:500:127::/48AS36620/48
2001:500:127::/48AS36621/48
2001:500:127::/48AS36622/48
2001:500:127::/48AS36623/48
2001:500:127::/48AS36624/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.

History

  1. AS1983612th August 2026 — present
  2. AS39660512th August 2026 — present
  3. AS39720012th August 2026 — present
  4. AS3662312th August 2026 — present
  5. AS39655512th August 2026 — present
  6. AS39719412th August 2026 — present
  7. AS39719712th August 2026 — present
  8. AS39720312th August 2026 — present
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.