SUBNET.IM

240c:ca02::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

6%

4 of 62 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 29th January 2019

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: 1 observed path to 240c:ca02::/32, fanning out from AS138371 toward the vantage points that see it. Each path is written out in full beneath the graph.AS138371CERNET2 regional …OriginAS23910China Next Genera…AS4134China Telecom Bac…AS15802Emirates Integrat…AS8966Etisalat (E&)AS132337Axclusive
  1. Singapore138371239104134158028966132337This 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.

Route visibility

6%

Seen by 4 of 62 full-feed vantage points

Seen by few vantage points

Observed at 1 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 January 2019
Allocation block
240c:c000::/20
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 240c:ca02::/32
ROA prefixAuthorised originMax length
240c:ca02::/32AS138371/32
240c:ca02::/32AS4538/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 240c:ca02::/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.240c:c000::/20AS23910240c:ca03::/32AS4538240c:ca02::/32AS138371This prefix240c:ca03::/32AS138371

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 240c:ca02::/32
PrefixAddressesOriginVisibility
240c:c000::/2017.6T × /64AS23910China Next Generation Internet CERNET262/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 240c:ca02::/32
PrefixAddressesOriginVisibility
240c:ca03::/324.3B × /64AS4538China Education and Research Network Center2/62
240c:ca03::/324.3B × /64AS138371CERNET2 regional IX at Ocean University of China4/62

History

  1. AS453812th August 2026 present
  2. AS13837112th 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.