subnet.im

2606:9300:17::/48

Not announced at this prefix length

We do not see 2606:9300:17::/48 announced as its own route. The most specific announcement covering it is 2606:9300::/32, originated by AS16904 (Arvig Enterprises 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 13th December 2011

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
13th December 2011
Allocation block
2606:9300::/32
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 2606:9300:17::/48
ROA prefixAuthorised originMax length
2606:9300::/32AS16904/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2606:9300:17::/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.2606:9300::/32AS169042606:9300:17::/48This 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 2606:9300:17::/48
PrefixAddressesOriginVisibility
2606:9300::/324.3B × /64AS16904Arvig Enterprises Inc.61/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. AS169045th November 2026 — 5th November 2026
  2. AS169042nd November 2026 — 2nd November 2026
  3. AS1690431st October 2026 — 1st November 2026
  4. AS1690430th October 2026 — 31st October 2026
  5. AS1690429th October 2026 — 29th October 2026
  6. AS1690425th October 2026 — 25th October 2026
  7. AS1690420th October 2026 — 20th October 2026
  8. AS1690418th October 2026 — 18th 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.