subnet.im

103.102.41.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

APNICPK

Allocated 11th October 2017

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 103.102.41.0/24 as seen from Sao Paulo, read outward from the origin: AS153844 → AS138655 → AS38193 → AS174 → AS6453 → AS35280. Each hop is listed with its network name beneath the graph.AS153844Riderz Network Br…OriginAS138655Trans World Enter…AS38193Transworld Associ…AS174Cogent Communicat…AS6453TATA Communicatio…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS153844seen on 512 paths from 137 vantage points
  2. Peer of AS138655seen on 6,372 paths from 139 vantage points
  3. Peer of AS38193seen on 80,014 paths from 118 vantage points
  4. Peer of AS174seen on 576,294 paths from 51 vantage points
  5. Peer of AS6453seen on 641,871 paths from 6 vantage points
  6. 6AS35280F5 Networks SARLFRVantage 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. London, UK153844138655381938529This path
  2. Singapore15384413865538193463523673This path
  3. Oregon, US15384413865538193693920130This path
  4. Amsterdam153844138655381936762250918298This path
  5. Sao Paulo15384413865538193174645335280Shown above

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

99%

Seen by 75 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
Pakistan
Allocated
11th October 2017
Allocation block
103.102.40.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.102.41.0/24
ROA prefixAuthorised originMax length
103.102.41.0/24AS153844/24
103.102.40.0/23AS153844/23

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.102.41.0/24
PrefixAddressesOriginVisibility
103.102.40.0/24256AS153844Riderz Network Broadband (Private) Limited75/76

History

  1. AS15384420th October 2026 — present
  2. AS15384412th October 2026 — 19th October 2026
  3. AS5889512th August 2026 — 6th 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.102.41.0/24 in the calculator/24 reference

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