SUBNET.IM

2001:df2:d101::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 26th July 2023

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 2001:df2:d101::/48 as seen from Amsterdam, read outward from the origin: AS136707 → AS55836 → AS64049 → AS4637 → AS6939 → AS213151. Each hop is listed with its network name beneath the graph.AS136707The Kalupur Comme…OriginAS55836Reliance Jio Info…AS64049Reliance Jio Info…AS4637Telstra Internati…AS6939Hurricane Electri…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS136707seen on 140 paths from 140 vantage points
  2. Peer of AS55836seen on 571,522 paths from 141 vantage points
  3. Peer of AS64049seen on 57,985 paths from 57 vantage points
  4. Peer of AS4637seen on 84,316 paths from 62 vantage points
  5. Peer of AS6939seen on 309,709 paths from 2 vantage points
  6. 6AS213151Christian ElsenDEVantage 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, UK136707558366404951907This path
  2. Singapore1367075583664049132337This path
  3. Sao Paulo1367075583664049719532590This path
  4. Amsterdam136707558366404946376939213151Shown 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

97%

Seen by 60 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
India
Allocated
26th July 2023
Allocation block
2001:df2:d101::/48
Status
assigned
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:df2:d101::/48
ROA prefixAuthorised originMax length
2001:df2:d101::/48AS136707/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 2001:df2:d101::/48
PrefixAddressesOriginVisibility
2001:df2:d100::/4865.5k × /64AS136707The Kalupur Commercial Co-operative Bank Limited61/62

History

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