subnet.im

42.83.131.0/24

China Internet Network Infomation CenterAS24406

China Internet Network Infomation CenterAS24151

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

89%

71 of 80 vantage points

RPKI

No ROA

Registry

APNICCN

Allocated 10th March 2011

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 42.83.131.0/24 as seen from Amsterdam, read outward from the origin: AS24406 → AS33071 → AS6939 → AS213151. Each hop is listed with its network name beneath the graph.AS24406China Internet Ne…OriginAS33071ISC F-ROOT ORD1AS6939Hurricane Electri…AS213151Christian Elsen

Seen from Amsterdam

  1. 1AS24406China Internet Network Infomation CenterCNOrigin
    Peer of AS24406seen on 301 paths from 87 vantage points
  2. 2AS33071ISC F-ROOT ORD1US
    Peer of AS33071seen on 375 paths from 109 vantage points
  3. 3AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 309,709 paths from 2 vantage points
  4. 4AS213151Christian ElsenDEVantage 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. Singapore2415121859132337This path
  2. Amsterdam24406330716939213151Shown above
  3. London, UK244061754712998529This path
  4. Sao Paulo24406330716939266213This path
  5. Oregon, US2440633071693920130This 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

89%

Seen by 71 of 80 full-feed vantage points

Partially propagated

Observed at 5 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
10th March 2011
Allocation block
42.83.128.0/17
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 42.83.131.0/24
PrefixAddressesOriginVisibility
42.83.130.0/24256AS24151China Internet Network Infomation Center28/80
42.83.130.0/24256AS24406China Internet Network Infomation Center52/80

History

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

Open 42.83.131.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.