subnet.im

2401:b60:e202::/48

Hytron Network Services LimitedAS17433

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 15th June 2023

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 2401:b60:e202::/48 as seen from Sao Paulo, read outward from the origin: AS17433 → AS137409 → AS32590. Each hop is listed with its network name beneath the graph.AS17433Hytron Network Se…OriginAS137409GSL Networks Pty …AS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS17433Hytron Network Services LimitedHKOrigin
    Peer of AS17433seen on 3,914 paths from 134 vantage points
  2. 2AS137409GSL Networks Pty LTDAU
    Peer of AS137409seen on 39,434 paths from 8 vantage points
  3. 3AS32590Valve CorporationUSVantage 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. Amsterdam17433137409213151This path
  2. Sao Paulo1743313740932590Shown above
  3. Singapore17433138997132337This path
  4. London, UK174333491900251907This 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

98%

Seen by 61 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
15th June 2023
Allocation block
2401:b60::/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:b60:e202::/48
ROA prefixAuthorised originMax length
2401:b60:e202::/48AS17433/48

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 2401:b60:e202::/48
PrefixAddressesOriginVisibility
2401:b60:e203::/4865.5k × /64AS151407Hytron Network Services Limited61/62

History

  1. AS1743312th 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.