subnet.im

2001:503:231d::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

17%

11 of 64 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 3rd June 2004

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: 3 observed paths to 2001:503:231d::/48, fanning out from AS396659, AS396714, AS396729 toward the vantage points that see it. Each path is written out in full beneath the graph.AS396714Verisign Anycast …OriginAS26415VeriSign Global R…AS32590Valve CorporationAS396659Verisign Anycast …OriginAS26415VeriSign Global R…AS35280F5 Networks SARLAS396729Verisign Anycast …OriginAS26415VeriSign Global R…AS132337Axclusive
  1. Amsterdam3967142641532590This path
  2. Sao Paulo3966592641535280This path
  3. Singapore39672926415132337This 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

17%

Seen by 11 of 64 full-feed vantage points

Seen by few vantage points

Observed 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
3rd June 2004
Allocation block
2001:503:231d::/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

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

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS39671412th October 2026 — present
  2. AS39719920th October 2026 — present
  3. AS3967476th October 2026 — present
  4. AS4064716th October 2026 — present
  5. AS39676112th August 2026 — present
  6. AS39668213th October 2026 — present
  7. AS39664222nd October 2026 — present
  8. AS39666112th October 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.