subnet.im

116.196.15.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 10th April 2007

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 116.196.15.0/24 as seen from London, UK, read outward from the origin: AS134700 → AS4058 → AS6453 → AS8529. Each hop is listed with its network name beneath the graph.AS134700Sinoycloud LimitedOriginAS4058CITIC Telecom Int…AS6453TATA Communicatio…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS134700seen on 3,438 paths from 80 vantage points
  2. Peer of AS4058seen on 6,257 paths from 88 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. Singapore1347004058132337This path
  2. London, UK134700405864538529Shown above
  3. Oregon, US1347004058693920130This path
  4. Amsterdam1347004058645334549213151This path
  5. Sao Paulo134700405864533356266213This 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

99%

Seen by 79 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
China
Allocated
10th April 2007
Allocation block
116.196.0.0/17
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 116.196.15.0/24
ROA prefixAuthorised originMax length
116.196.15.0/24AS134700/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. AS13470012th 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 116.196.15.0/24 in the calculator/24 reference

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