subnet.im

103.186.84.0/24

GNET INC.AS22427

GNET INC.AS9294

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

76%

58 of 76 vantage points

RPKI

No ROA

Registry

APNICUS

Allocated 14th April 2022

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.186.84.0/24, fanning out from AS9294, AS22427 toward the vantage points that see it. Each path is written out in full beneath the graph.AS22427GNET INC.OriginAS9294GNET INC.AS9002RETN LimitedAS8529Zain Omantel Inte…AS2914NTT America, Inc.AS35280F5 Networks SARLAS9294GNET INC.OriginAS18013ASLINE LIMITEDAS17476CloudRadium (HK) …AS23673Cogetel Online, C…AS25091IP-Max SAAS8298IPng Networks GmbHAS8551Bezeq Internation…AS42013Together Communic…
  1. London, UK22427929490028529This path
  2. Sao Paulo224279294291435280This path
  3. Singapore9294180131747623673This path
  4. Amsterdam2242792949002250918298This path
  5. Oregon, US2242792949002855142013This 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

76%

Seen by 58 of 76 full-feed vantage points

Partially 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
United States
Allocated
14th April 2022
Allocation block
103.186.84.0/23
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.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 103.186.84.0/24
PrefixAddressesOriginVisibility
103.186.85.0/24256AS22427GNET INC.59/76
103.186.85.0/24256AS9294GNET INC.17/76

History

  1. AS2242731st October 2026 — present
  2. AS92947th November 2026 — present
  3. AS92946th November 2026 — 6th November 2026
  4. AS929430th October 2026 — 31st October 2026
  5. AS2242728th October 2026 — 30th October 2026
  6. AS929427th October 2026 — 28th October 2026
  7. AS2242725th October 2026 — 27th October 2026
  8. AS929424th October 2026 — 25th October 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.186.84.0/24 in the calculator/24 reference

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