subnet.im

2401:4a00::/32

HKBN Enterprise Solutions LimitedAS17444

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 8th April 2010

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 2401:4a00::/32 as seen from London, UK, read outward from the origin: AS17444 → AS10103 → AS9269 → AS3257 → AS9002 → AS51907. Each hop is listed with its network name beneath the graph.AS17444HKBN Enterprise S…OriginAS10103HK Broadband Netw…AS9269Hong Kong Broadba…AS3257GTT Communication…AS9002RETN LimitedAS51907Kanton Zug

Seen from London, UK

  1. 1AS17444HKBN Enterprise Solutions LimitedHKOrigin
    Peer of AS17444seen on 21,812 paths from 142 vantage points
  2. 2AS10103HK Broadband Network Ltd.HK
    Peer of AS10103seen on 69,108 paths from 142 vantage points
  3. 3AS9269Hong Kong Broadband Network Ltd.HK
    Peer of AS9269seen on 11,557 paths from 63 vantage points
  4. 4AS3257GTT Communications Inc.US
    Peer of AS3257seen on 334,233 paths from 27 vantage points
  5. 5AS9002RETN LimitedGB
    Peer of AS9002seen on 325,294 paths from 2 vantage points
  6. 6AS51907Kanton ZugCHVantage 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. Singapore1744410103132337This path
  2. Amsterdam174441010346356939213151This path
  3. Sao Paulo17444101034635693932590This path
  4. London, UK174441010392693257900251907Shown 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

100%

Seen by 62 of 62 full-feed vantage points

Globally propagated

Observed at 4 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
8th April 2010
Allocation block
2401:4a00::/32
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 2401:4a00::/32
ROA prefixAuthorised originMax length
2401:4a00::/32AS10103/32
2401:4a00::/32AS17444/32
2401:4a00::/32AS9269/32
2401:4a00::/32AS9381/32

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. AS1744412th 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.

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