SUBNET.IM

2001:f00::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICTH

Allocated 4th June 2004

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 2001:f00::/32 as seen from Singapore, read outward from the origin: AS3836 → AS4621 → AS4651 → AS132337. Each hop is listed with its network name beneath the graph.AS3836Thai Social/Scien…OriginAS4621UniNet ThailandAS4651The Communication…AS132337Axclusive

Seen from Singapore

  1. Peer of AS3836seen on 219 paths from 141 vantage points
  2. Peer of AS4621seen on 28,146 paths from 140 vantage points
  3. Peer of AS4651seen on 4,564 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. Amsterdam383646214651213151This path
  2. London, UK38364621465151907This path
  3. Singapore383646214651132337Shown above
  4. Sao Paulo383646214651719532590This 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
Thailand
Allocated
4th June 2004
Allocation block
2001:f00::/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 2001:f00::/32
ROA prefixAuthorised originMax length
2001:f00::/32AS3836/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. AS383612th 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.