subnet.im

103.172.35.0/24

At a glance

Addresses

256

/24 block

Visibility

98%

78 of 80 vantage points

RPKI

Valid

Registry

APNICID

Allocated 23rd August 2021

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 103.172.35.0/24 as seen from Singapore, read outward from the origin: AS58821 → AS4800 → AS23764 → AS132337. Each hop is listed with its network name beneath the graph.AS58821PT Lintas Jaringa…OriginAS4800PT Aplikanusa Lin…AS23764China Telecom Glo…AS132337Axclusive

Seen from Singapore

  1. Peer of AS58821seen on 1,352 paths from 80 vantage points
  2. Peer of AS4800seen on 17,370 paths from 120 vantage points
  3. Peer of AS23764seen on 6,509 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Amsterdam58821480023764213151This path
  2. London, UK58821480012998529This path
  3. Singapore58821480023764132337Shown above
  4. Oregon, US588214800693920130This path
  5. Sao Paulo588214800237643356266213This 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 78 of 80 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
Indonesia
Allocated
23rd August 2021
Allocation block
103.172.34.0/23
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 103.172.35.0/24
ROA prefixAuthorised originMax length
103.172.35.0/24AS58821/24
103.172.34.0/23AS58821/24

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.172.35.0/24
PrefixAddressesOriginVisibility
103.172.34.0/24256AS58821PT Lintas Jaringan Nusantara80/80

History

  1. AS14972512th August 2026 present
  2. AS5882112th 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 103.172.35.0/24 in the calculator/24 reference

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