SUBNET.IM

240e:14::/36

CHINATELECOM Fujian province Fuzhou 5G networkAS140329

At a glance

Subnets

268,435,456 × /64

/36 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 20th May 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 240e:14::/36, fanning out from AS140329 toward the vantage points that see it. Each path is written out in full beneath the graph.AS140329CHINATELECOM Fuji…OriginAS4134China Telecom Bac…AS34549meerfarbig GmbH &…AS213151Christian ElsenAS12956Telxius (Telefoni…AS32590Valve CorporationAS4766Korea TelecomAS132337AxclusiveAS3356Lumen (Level 3)AS15576NTS workspace AGAS51907Kanton Zug
  1. Amsterdam140329413434549213151This path
  2. Sao Paulo14032941341295632590This path
  3. Singapore14032941344766132337This path
  4. London, UK140329413433561557651907This 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

98%

Seen by 61 of 62 full-feed vantage points

Globally 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
20th May 2010
Allocation block
240e::/24
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 240e:14::/36
ROA prefixAuthorised originMax length
240e:14::/36AS140329/36
240e:14::/31AS4134/31

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 240e:14::/36: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.240e:14::/31AS4134240e::/24AS4134240e::/20AS4134240e:14::/36AS140329This prefix240e:14:1000::/36AS140330

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 240e:14::/36
PrefixAddressesOriginVisibility
240e:14::/318.6B × /64AS4134China Telecom Backbone61/62
240e::/241.1T × /64AS4134China Telecom Backbone61/62
240e::/2017.6T × /64AS4134China Telecom Backbone59/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 240e:14::/36
PrefixAddressesOriginVisibility
240e:14:1000::/36268M × /64AS140330CHINATELECOM Fujian province Xiamen 5G network61/62

History

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