subnet.im

2402:2200:8000::/35

At a glance

Subnets

536,870,912 × /64

/35 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

APNICMY

Allocated 6th May 2010

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 2402:2200:8000::/35 as seen from Singapore, read outward from the origin: AS24090 → AS24514 → AS9930 → AS132337. Each hop is listed with its network name beneath the graph.AS24090Universiti Sains …OriginAS24514MINISTRY OF HIGHE…AS9930TIME dotCom BhdAS132337Axclusive

Seen from Singapore

  1. Peer of AS24090seen on 1,740 paths from 142 vantage points
  2. Peer of AS24514seen on 6,573 paths from 142 vantage points
  3. Peer of AS9930seen on 828 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. London, UK2409024514993051907This path
  2. Singapore24090245149930132337Shown above
  3. Amsterdam240902451499306939213151This path
  4. Sao Paulo24090245149930719532590This 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
Malaysia
Allocated
6th May 2010
Allocation block
2402:2200::/32
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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 2402:2200:8000::/35
PrefixAddressesOriginVisibility
2402:2200:a000::/35537M × /64AS24090Universiti Sains Malaysia (USM)62/62

History

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