subnet.im

2001:df1:6000::/48

8 Kallang SectorAS131217

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

APNICSG

Allocated 21st May 2013

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 2001:df1:6000::/48 as seen from Sao Paulo, read outward from the origin: AS131217 → AS8220 → AS7195 → AS32590. Each hop is listed with its network name beneath the graph.AS1312178 Kallang SectorOriginAS8220COLTAS7195EdgeUnoAS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS1312178 Kallang SectorSGOrigin
    Peer of AS131217seen on 82 paths from 82 vantage points
  2. 2AS8220COLTGB
    Peer of AS8220seen on 3,397 paths from 4 vantage points
  3. 3AS7195EdgeUnoCO
    Peer of AS7195seen on 329,420 paths from 3 vantage points
  4. 4AS32590Valve CorporationUSVantage 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, UK1312178220673051907This path
  2. Sao Paulo1312178220719532590Shown above
  3. Singapore13121713988323856132337This path
  4. Amsterdam131217139883238569002213151This 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
Singapore
Allocated
21st May 2013
Allocation block
2001:df1:6000::/48
Status
assigned
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 2001:df1:6000::/48
PrefixAddressesOriginVisibility
2001:df1:6001::/4865.5k × /64AS150183Infineon Technologies Asia Pacific Pte Ltd61/62

History

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