subnet.im

2602:f7a7:21::/48

ZHU-YUAN JIANGAS216123

At a glance

Subnets

65,536 × /64

/48 block

Visibility

21%

13 of 63 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 7th November 2024

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 2602:f7a7:21::/48 as seen from Singapore, read outward from the origin: AS216123 → AS6939 → AS132337. Each hop is listed with its network name beneath the graph.AS216123ZHU-YUAN JIANGOriginAS6939Hurricane Electri…AS132337Axclusive

Seen from Singapore

  1. 1AS216123ZHU-YUAN JIANGTWOrigin
    Peer of AS216123seen on 45 paths from 18 vantage points
  2. 2AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 478,416 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. Singapore2161236939132337Shown 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.

Route visibility

21%

Seen by 13 of 63 full-feed vantage points

Seen by few vantage points

Observed at 1 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
ARIN — North America
Country
United States
Allocated
7th November 2024
Allocation block
2602:f7a7::/40
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 2602:f7a7:21::/48
ROA prefixAuthorised originMax length
2602:f7a7:21::/48AS216123/48
2602:f7a7::/40AS399624/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 2602:f7a7:21::/48
PrefixAddressesOriginVisibility
2602:f7a7:20::/4865.5k × /64AS206434CHENG-CHIH TSAI63/63

History

  1. AS21612316th October 2026 — present
  2. AS21612312th August 2026 — 16th October 2026
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.