subnet.im

39.109.88.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 5th April 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 39.109.88.0/24 as seen from London, UK, read outward from the origin: AS137969 → AS136491 → AS216458 → AS4134 → AS8529. Each hop is listed with its network name beneath the graph.AS137969HONG KONG BRIDGE …OriginAS136491TIDALPORT INTERNA…AS216458Hardcore Communic…AS4134China Telecom Bac…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS137969seen on 1 path from 1 vantage point
  2. Peer of AS136491seen on 13 paths from 2 vantage points
  3. Peer of AS216458seen on 142 paths from 1 vantage point
  4. Peer of AS4134seen on 57,640 paths from 1 vantage 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. Singapore149175134578132337This path
  2. London, UK13796913649121645841348529Shown above
  3. Sao Paulo14917513457829143356266213This path
  4. Oregon, US14917513457829142335220130This path
  5. Amsterdam1491751379699304154126939213151This 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
Hong Kong SAR China
Allocated
5th April 2011
Allocation block
39.109.88.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 39.109.88.0/24
ROA prefixAuthorised originMax length
39.109.88.0/24AS137969/24
39.109.88.0/24AS141768/24
39.109.88.0/24AS149175/24
39.109.88.0/22AS137969/22
39.109.88.0/22AS141768/22

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 39.109.88.0/24
PrefixAddressesOriginVisibility
39.109.89.0/24256AS149175UNION FU WAH DIGITAL TECHNOLOGY LIMITED80/80

History

  1. AS14917512th August 2026 present
  2. AS13796912th 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 39.109.88.0/24 in the calculator/24 reference

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