subnet.im

240a:4172::/31

NINGXIA BROADCAST&TV NETWORK CO.,LTDAS63621

At a glance

Subnets

8,589,934,592 × /64

/31 block

Visibility

15%

9 of 62 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 29th December 2017

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 240a:4172::/31 as seen from London, UK, read outward from the origin: AS63621 → AS146788 → AS4134 → AS29075 → AS39040 → AS51907. Each hop is listed with its network name beneath the graph.AS63621NINGXIA BROADCAST…OriginAS146788China Broadcastin…AS4134China Telecom Bac…AS29075IELO-LIAZO SERVIC…AS39040NTS workspace AGAS51907Kanton Zug

Seen from London, UK

  1. 1AS63621NINGXIA BROADCAST&TV NETWORK CO.,LTDCNOrigin
    Peer of AS63621seen on 109 paths from 14 vantage points
  2. 2AS146788China Broadcasting Network Co., LtdCN
    Peer of AS146788seen on 5,247 paths from 20 vantage points
  3. 3AS4134China Telecom BackboneCN
    Peer of AS4134seen on 407 paths from 2 vantage points
  4. 4AS29075IELO-LIAZO SERVICES SASFR
    Peer of AS29075seen on 1,076 paths from 2 vantage points
  5. 5AS39040NTS workspace AGCH
    Peer of AS39040seen on 8,440 paths from 2 vantage points
  6. 6AS51907Kanton ZugCHVantage 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. London, UK636211467884134290753904051907Shown above
  2. Singapore636211467884134158028966132337This 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

15%

Seen by 9 of 62 full-feed vantage points

Seen by few vantage points

Observed at 3 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
29th December 2017
Allocation block
240a:4000::/21
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 240a:4172::/31
ROA prefixAuthorised originMax length
240a:4172::/31AS63621/31

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

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

History

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