subnet.im

2401:b400:3::/48

CONAC (China Organizational Name Administration Center)AS58448

At a glance

Subnets

65,536 × /64

/48 block

Visibility

84%

52 of 62 vantage points

RPKI

No ROA

Registry

APNICCN

Allocated 7th September 2009

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 2401:b400:3::/48 as seen from Singapore, read outward from the origin: AS58448 → AS4808 → AS4837 → AS4766 → AS132337. Each hop is listed with its network name beneath the graph.AS58448CONAC (China Orga…OriginAS4808China Unicom Beij…AS4837China Unicom Back…AS4766Korea TelecomAS132337Axclusive

Seen from Singapore

  1. 1AS58448CONAC (China Organizational Name Administration Center)CNOrigin
    Peer of AS58448seen on 600 paths from 140 vantage points
  2. 2AS4808China Unicom Beijing Province NetworkCN
    Peer of AS4808seen on 175,195 paths from 141 vantage points
  3. 3AS4837China Unicom BackboneCN
    Peer of AS4837seen on 13,167 paths from 3 vantage points
  4. 4AS4766Korea TelecomKR
    Peer of AS4766seen on 70,419 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Sao Paulo58448480848371295632590This path
  2. Singapore58448480848374766132337Shown above
  3. Amsterdam5844848084837551134549213151This path
  4. London, UK584484808483712993428851907This 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

84%

Seen by 52 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
7th September 2009
Allocation block
2401:b400::/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.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2401:b400:3::/48
PrefixAddressesOriginVisibility
2401:b400:2::/4865.5k × /64AS58448CONAC (China Organizational Name Administration Center)60/62

History

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