subnet.im

2001:f20:2000:2::/64

At a glance

Subnets

1 × /64

/64 block

Visibility

2%

1 of 62 vantage points

RPKI

Invalid

Registry

APNICID

Allocated 25th 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:f20:2000:2::/64 as seen from Singapore, read outward from the origin: AS9875 → AS38154 → AS45147 → AS55818 → AS132337. Each hop is listed with its network name beneath the graph.AS9875PT Pasifik Sateli…OriginAS38154PT Pasifik Sateli…AS45147PT NAP Info Linta…AS55818Matrix Cable Inte…AS132337Axclusive

Seen from Singapore

  1. Peer of AS9875seen on 4,350 paths from 142 vantage points
  2. Peer of AS38154seen on 4,909 paths from 142 vantage points
  3. Peer of AS45147seen on 10,595 paths from 104 vantage points
  4. Peer of AS55818seen on 1,062 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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. Singapore9875381544514755818132337Shown 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

2%

Seen by 1 of 62 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
APNIC — Asia-Pacific
Country
Indonesia
Allocated
25th June 2004
Allocation block
2001:f20::/32
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2001:f20:2000:2::/64
ROA prefixAuthorised originMax length
2001:f20:2000::/36AS9875/48

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2001:f20:2000:2::/64: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2001:f20:2000::/…AS98752001:f20:2000:2:…AS9875This prefix

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 2001:f20:2000:2::/64
PrefixAddressesOriginVisibility
2001:f20:2000::/4865.5k × /64AS9875PT Pasifik Satelit Nusantara62/62

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. AS987512th 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.