subnet.im

2a06:9801:1588::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

32%

20 of 63 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 2nd February 2026

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 2a06:9801:1588::/48 as seen from Singapore, read outward from the origin: AS204464 → AS199746 → AS204464 → AS205941 → AS400587 → AS35133 → AS6939 → AS132337. Each hop is listed with its network name beneath the graph.AS204464SharedServ LtdOriginAS199746SharedServ LtdAS204464SharedServ LtdAS205941Lungu Stefan Gabr…AS400587Ryamer, LLCAS35133Eranium B.V.AS6939Hurricane Electri…AS132337Axclusive

Seen from Singapore

  1. Peer of AS204464seen on 20 paths from 20 vantage points
  2. Peer of AS199746seen on 22 paths from 20 vantage points
  3. Peer of AS204464seen on 590 paths from 138 vantage points
  4. Peer of AS205941seen on 509 paths from 55 vantage points
  5. Peer of AS400587seen on 232 paths from 20 vantage points
  6. Peer of AS35133seen on 3,684 paths from 68 vantage points
  7. Peer of AS6939seen on 478,416 paths from 2 vantage points
  8. 8AS132337AxclusiveSGVantage 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. Singapore204464199746204464205941400587351336939132337Shown 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

32%

Seen by 20 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
RIPE NCC — Europe, Middle East, Central Asia
Country
United Kingdom
Allocated
2nd February 2026
Allocation block
2a06:9800::/29
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 2a06:9801:1588::/48
ROA prefixAuthorised originMax length
2a06:9801:1588::/48AS204464/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 2a06:9801:1588::/48
PrefixAddressesOriginVisibility
2a06:9801:1589::/4865.5k × /64AS218789Soundvia LLC62/63

History

  1. AS2044645th November 2026 — present
  2. AS20446430th October 2026 — 3rd November 2026
  3. AS20446427th October 2026 — 30th October 2026
  4. AS20446412th October 2026 — 12th 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.