subnet.im

2600:f0f0:c12a::/48

Not announced at this prefix length

We do not see 2600:f0f0:c12a::/48 announced as its own route. The most specific announcement covering it is 2600:f000::/24, originated by AS16509 (Amazon.com, Inc.). Traffic to addresses in this block follows that route.

At a glance

Subnets

65,536 × /64

/48 block

Visibility

Unknown

RPKI

Unknown

Registry

ARINUS

Allocated 25th March 2022

AS paths to this prefix

No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.

Registry and RPKI

RIR
ARIN — North America
Country
United States
Allocated
25th March 2022
Allocation block
2600:f000::/24
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 2600:f0f0:c12a::/48
ROA prefixAuthorised originMax length
2600:f0f0:c100::/40AS14618/48
2600:f0f0:c100::/40AS16509/48
2600:f0f0:c100::/40AS21664/48
2600:f0f0::/28AS16509/28
2600:f000::/24AS16509/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2600:f0f0:c12a::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2600:f000::/24AS165092600:f0f0:c12a::…This prefix

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 2600:f0f0:c12a::/48
PrefixAddressesOriginVisibility
2600:f000::/241.1T × /64AS16509Amazon.com, Inc.60/63

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. AS146187th November 2026 — 7th November 2026
  2. AS146181st November 2026 — 2nd November 2026
  3. AS146181st November 2026 — 1st November 2026
  4. AS1461823rd October 2026 — 27th October 2026
  5. AS1461822nd October 2026 — 23rd October 2026
  6. AS1461820th October 2026 — 20th October 2026
  7. AS1461819th October 2026 — 19th October 2026
  8. AS1461817th October 2026 — 17th 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.