SUBNET.IM

43.240.0.0/22

At a glance

Addresses

1,024

/22 block

Visibility

6%

5 of 80 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 8th August 2014

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: 2 observed paths to 43.240.0.0/22, fanning out from AS4837 toward the vantage points that see it. Each path is written out in full beneath the graph.AS4837China Unicom Back…OriginAS4134China Telecom Bac…AS8529Zain Omantel Inte…AS9808China Mobile Back…AS58453China Mobile Inte…AS15802Emirates Integrat…AS8966Etisalat (E&)AS132337Axclusive
  1. London, UK483741348529This path
  2. Singapore4837980858453158028966132337This 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

6%

Seen by 5 of 80 full-feed vantage points

Seen by few vantage points

Observed at 2 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
8th August 2014
Allocation block
43.240.0.0/22
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 43.240.0.0/22
ROA prefixAuthorised originMax length
43.240.0.0/22AS23650/24
43.240.0.0/22AS4134/24
43.240.0.0/22AS4837/24
43.240.0.0/22AS56046/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 43.240.0.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.43.240.0.0/22AS4837This prefix43.240.0.0/24AS2365043.240.1.0/24AS2365043.240.2.0/24AS2365043.240.3.0/24AS23650

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

No less specific announcement covers this prefix.

Sibling prefixes

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

History

  1. AS483712th 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 43.240.0.0/22 in the calculator/22 reference

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