SUBNET.IM

2408:4016:6::/48

Alibaba CloudAS24429

Hangzhou Alibaba Advertising Co.,Ltd.AS37963

Announced by more than one origin AS (MOAS).

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 21st December 2015

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 2408:4016:6::/48, fanning out from AS24429 toward the vantage points that see it. Each path is written out in full beneath the graph.AS24429Alibaba CloudOriginAS51907Kanton ZugAS7552Viettel GroupAS213151Christian ElsenAS3356Lumen (Level 3)AS32590Valve CorporationAS21859Zenlayer IncAS4229Zenlayer IncAS132337Axclusive
  1. London, UK2442951907This path
  2. Amsterdam244297552213151This path
  3. Sao Paulo24429335632590This path
  4. Singapore24429218594229132337This 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

98%

Seen by 61 of 62 full-feed vantage points

Globally 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
APNIC — Asia-Pacific
Country
China
Allocated
21st December 2015
Allocation block
2408:4000::/22
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 2408:4016:6::/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:6::/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:7::/48AS244292408:4016:6::/48AS24429This prefix2408:4016:7::/48AS37963

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

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2408:4016:6::/48
PrefixAddressesOriginVisibility
2408:4016:7::/4865.5k × /64AS24429Alibaba Cloud60/62
2408:4016:7::/4865.5k × /64AS37963Hangzhou Alibaba Advertising Co.,Ltd.1/62

History

  1. AS3796312th August 2026 — present
  2. AS2442912th August 2026 — present
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.