subnet.im

103.43.10.0/23

I LAYER LIMITEDAS137899

At a glance

Addresses

512

/23 block

Visibility

97%

74 of 76 vantage points

RPKI

No ROA

Registry

APNICHK

Allocated 14th November 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: 5 observed paths to 103.43.10.0/23, fanning out from AS137899 toward the vantage points that see it. Each path is written out in full beneath the graph.AS137899I LAYER LIMITEDOriginAS40779VoltNet incAS2914NTT America, Inc.AS35280F5 Networks SARLAS23673Cogetel Online, C…AS25091IP-Max SAAS8298IPng Networks GmbHAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS8551Bezeq Internation…AS42013Together Communic…
  1. Sao Paulo13789940779291435280This path
  2. Singapore13789940779291423673This path
  3. Amsterdam137899407792914250918298This path
  4. London, UK13789940779291412998529This path
  5. Oregon, US1378994077929141299855142013This 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

97%

Seen by 74 of 76 full-feed vantage points

Globally 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
Hong Kong SAR China
Allocated
14th November 2014
Allocation block
103.43.8.0/22
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.

CoveringMore specific
Prefix hierarchy for 103.43.10.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.103.43.8.0/22AS401696103.43.8.0/22AS401701103.43.10.0/23AS137899This prefix103.43.8.0/23AS137899103.43.11.0/24AS35876

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 103.43.10.0/23
PrefixAddressesOriginVisibility
103.43.8.0/221kAS401696cognetcloud INC1/76
103.43.8.0/221kAS401701cognetcloud INC75/76

More specific announcements

Announcements contained within 103.43.10.0/23
PrefixAddressesOriginVisibility
103.43.11.0/24256AS35876VoltNet inc76/76

Sibling prefixes

Prefixes of the same length sharing a parent block with 103.43.10.0/23
PrefixAddressesOriginVisibility
103.43.8.0/23512AS137899I LAYER LIMITED74/76

History

  1. AS1378991st November 2026 — present
  2. AS40170112th August 2026 — 1st November 2026
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 103.43.10.0/23 in the calculator/23 reference

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