SUBNET.IM

2001:dc7:1::/48

China Internet Network Infomation CenterAS24406

China Internet Network Infomation CenterAS24409

China Internet Network Infomation CenterAS24151

Announced by more than one origin AS (MOAS).

At a glance

Subnets

65,536 × /64

/48 block

Visibility

52%

32 of 62 vantage points

RPKI

No ROA

Registry

APNICCN

Allocated 13th September 2004

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 2001:dc7:1::/48, fanning out from AS24406, AS24409 toward the vantage points that see it. Each path is written out in full beneath the graph.AS24406China Internet Ne…OriginAS21859Zenlayer IncAS51907Kanton ZugAS24409China Internet Ne…OriginAS10111Zeofast NetworkAS6939Hurricane Electri…AS213151Christian ElsenAS4837China Unicom Back…AS12956Telxius (Telefoni…AS32590Valve CorporationAS4766Korea TelecomAS132337Axclusive
  1. London, UK244062185951907This path
  2. Amsterdam24409101116939213151This path
  3. Sao Paulo2440648371295632590This path
  4. Singapore2440648374766132337This 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

52%

Seen by 32 of 62 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
APNIC — Asia-Pacific
Country
China
Allocated
13th September 2004
Allocation block
2001:dc7::/32
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2001:dc7: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.2001:dc7::/32AS241512001:dc7::/48AS241512001:dc7:1::/48AS24406This prefix2001:dc7::/48AS244062001:dc7::/48AS24409

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 2001:dc7:1::/48
PrefixAddressesOriginVisibility
2001:dc7::/324.3B × /64AS24151China Internet Network Infomation Center60/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2001:dc7:1::/48
PrefixAddressesOriginVisibility
2001:dc7::/4865.5k × /64AS24151China Internet Network Infomation Center4/62
2001:dc7::/4865.5k × /64AS24406China Internet Network Infomation Center4/62
2001:dc7::/4865.5k × /64AS24409China Internet Network Infomation Center54/62

History

  1. AS2415112th August 2026 — present
  2. AS2440912th August 2026 — present
  3. AS2440612th 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.