subnet.im

103.196.68.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICAU

Allocated 17th September 2015

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.196.68.0/24 as seen from Sao Paulo, read outward from the origin: AS38549 → AS45158 → AS64098 → AS134090 → AS137409 → AS266213. Each hop is listed with its network name beneath the graph.AS38549Viewbank Rise Net…OriginAS45158TASMANETAS64098TASMANETAS134090LeaptelAS137409GSL Networks Pty …AS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. Peer of AS38549seen on 198 paths from 109 vantage points
  2. Peer of AS45158seen on 2,203 paths from 141 vantage points
  3. Peer of AS64098seen on 2,284 paths from 46 vantage points
  4. Peer of AS134090seen on 10,974 paths from 135 vantage points
  5. Peer of AS137409seen on 12,063 paths from 2 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, UK3854938195325733568529This path
  2. Singapore3854945158640984826132337This path
  3. Oregon, US385493819532572335220130This path
  4. Sao Paulo385494515864098134090137409266213Shown above
  5. Amsterdam3854945158640984826154126939213151This 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
Australia
Allocated
17th September 2015
Allocation block
103.196.68.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.196.68.0/24
ROA prefixAuthorised originMax length
103.196.68.0/24AS38549/24
103.196.68.0/24AS58606/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.196.68.0/24
PrefixAddressesOriginVisibility
103.196.69.0/24256AS58606Viewbank Rise Networks15/80

History

  1. AS3854912th 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.196.68.0/24 in the calculator/24 reference

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