subnet.im

2408:4016:1::/48

Not announced at this prefix length

We do not see 2408:4016:1::/48 announced as its own route. The most specific announcement covering it is 2408:4000::/22, originated by AS37963 (Hangzhou Alibaba Advertising Co.,Ltd.). Traffic to addresses in this block follows that route.

At a glance

Subnets

65,536 × /64

/48 block

Visibility

Unknown

RPKI

Unknown

Registry

APNICCN

Allocated 21st December 2015

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
APNIC — Asia-Pacific
Country
China
Allocated
21st December 2015
Allocation block
2408:4000::/22
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 2408:4016:1::/48
ROA prefixAuthorised originMax length
2408:4016::/32AS24429/48
2408:4000::/22AS37963/48
2408:4000::/22AS45102/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2408:4016:1::/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.2408:4000::/22AS379632408:4016:1::/48This prefix2408:4016::/48AS24429

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 2408:4016:1::/48
PrefixAddressesOriginVisibility
2408:4000::/224.4T × /64AS37963Hangzhou Alibaba Advertising Co.,Ltd.62/64

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2408:4016:1::/48
PrefixAddressesOriginVisibility
2408:4016::/4865.5k × /64AS24429Alibaba Cloud62/64

History

  1. AS2442925th September 2026 — 25th September 2026
  2. AS2442924th September 2026 — 24th September 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.