SUBNET.IM

2401:be00::/32

Changping District, BeijingAS55641

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

53%

33 of 62 vantage points

RPKI

No ROA

Registry

APNICCN

Allocated 23rd April 2010

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 2401:be00::/32, fanning out from AS55641 toward the vantage points that see it. Each path is written out in full beneath the graph.AS55641Changping Distric…OriginAS133111CERNET New Techno…AS23910China Next Genera…AS23911China Next Genera…AS132337AxclusiveAS4635HKIX Route ServersAS6939Hurricane Electri…AS213151Christian ElsenAS32590Valve CorporationAS41913Computerline GmbHAS34288Kantonsschule Zug⋯
  1. Singapore556411331112391023911132337This path
  2. Amsterdam55641133111239102391146356939213151This path
  3. Sao Paulo5564113311123910239114635693932590This path
  4. London, UK556411331112391023911463569394191334288→ ⋯This 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

53%

Seen by 33 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
23rd April 2010
Allocation block
2401:be00::/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 2401:be00::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2401:be00::/32AS55641This prefix2401:be00::/48AS237242401:be00::/48AS1331192401:be00::/48AS556412401:be00:5::/48AS55641

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 2401:be00::/32
PrefixAddressesOriginVisibility
2401:be00::/4865.5k × /64AS23724China Telecom Beijing IDC Network26/62
2401:be00::/4865.5k × /64AS133119China Unicom IP network9/62
2401:be00::/4865.5k × /64AS55641Changping District, Beijing27/62
2401:be00:5::/4865.5k × /64AS55641Changping District, Beijing33/62

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS5564112th 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.