SUBNET.IM

103.10.148.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICID

Allocated 21st July 2011

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 103.10.148.0/22 as seen from London, UK, read outward from the origin: AS136102 → AS17451 → AS6453 → AS8529. Each hop is listed with its network name beneath the graph.AS136102PT Arupa Cloud Nu…OriginAS17451Biznet NetworksAS6453TATA Communicatio…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS136102seen on 194 paths from 34 vantage points
  2. Peer of AS17451seen on 10,693 paths from 86 vantage points
  3. Peer of AS6453seen on 89,408 paths from 35 vantage points

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, UK1361021745164538529Shown above
  2. Singapore13610217995137367132337This path
  3. Amsterdam136102179951373666939213151This path
  4. Sao Paulo136102179951373666939266213This path
  5. Oregon, US13610217995137366693920130This 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

100%

Seen by 80 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
21st July 2011
Allocation block
103.10.148.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 103.10.148.0/22
ROA prefixAuthorised originMax length
103.10.148.0/22AS136102/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

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

History

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

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