subnet.im

2605:9cc0:c0d::/48

Amazon Gov CloudAS8987

AS21664 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Subnets

65,536 × /64

/48 block

Visibility

81%

51 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: 4 observed paths to 2605:9cc0:c0d::/48, fanning out from AS8987 toward the vantage points that see it. Each path is written out in full beneath the graph.AS8987Amazon Gov CloudOriginAS16509Amazon.com, Inc.AS6453TATA Communicatio…AS2914NTT America, Inc.AS35280F5 Networks SARLAS2914NTT America, Inc.AS6453TATA Communicatio…AS35280F5 Networks SARLAS6939Hurricane Electri…AS132337AxclusiveAS174Cogent Communicat…AS6453TATA Communicatio…AS25091IP-Max SAAS8298IPng Networks GmbH
  1. London, UK8987165096453291435280This path
  2. Sao Paulo8987165092914645335280This path
  3. Singapore89871650964536939132337This path
  4. Amsterdam8987165091746453250918298This 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

81%

Seen by 51 of 63 full-feed vantage points

Partially propagated

Observed at 4 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:c0d::/48
ROA prefixAuthorised originMax length
2605:9cc0:c0d::/48AS14618/48
2605:9cc0:c0d::/48AS16509/48
2605:9cc0:c0d::/48AS21664/48
2605:9cc0:c0d::/48AS40045/48
2605:9cc0:c0d::/48AS8987/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

Prefixes of the same length sharing a parent block with 2605:9cc0:c0d::/48
PrefixAddressesOriginVisibility
2605:9cc0:c0c::/4865.5k × /64AS16509Amazon.com, Inc.43/63

History

  1. AS898720th October 2026 — present
  2. AS2166410th November 2026 — 11th November 2026
  3. AS2166410th November 2026 — 10th November 2026
  4. AS216649th November 2026 — 9th November 2026
  5. AS216647th November 2026 — 8th November 2026
  6. AS216647th November 2026 — 7th November 2026
  7. AS216646th November 2026 — 6th November 2026
  8. AS216644th November 2026 — 5th November 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.