subnet.im

2605:9cc0:c0a::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

3%

2 of 63 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 31st January 2020

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: 2 observed paths to 2605:9cc0:c0a::/48, fanning out from AS16509 toward the vantage points that see it. Each path is written out in full beneath the graph.AS16509Amazon.com, Inc.OriginAS6453TATA Communicatio…AS15412Flag Telecom UK L…AS15802Emirates Integrat…AS8966Etisalat (E&)AS35280F5 Networks SARL
  1. London, UK1650964531541215802896635280This path
  2. Sao Paulo1650964531541215802896635280This 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

3%

Seen by 2 of 63 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
31st January 2020
Allocation block
2605:9cc0::/32
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 2605:9cc0:c0a::/48
ROA prefixAuthorised originMax length
2605:9cc0:c0a::/48AS14618/48
2605:9cc0:c0a::/48AS16509/48
2605:9cc0:c0a::/48AS21664/48
2605:9cc0:c0a::/48AS40045/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. AS1650911th November 2026 — present
  2. AS216647th November 2026 — 7th November 2026
  3. AS1650931st October 2026 — 31st October 2026
  4. AS1650929th October 2026 — 29th October 2026
  5. AS1650925th October 2026 — 25th October 2026
  6. AS1650924th October 2026 — 25th October 2026
  7. AS1650922nd October 2026 — 22nd October 2026
  8. AS165095th October 2026 — 5th October 2026
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.