subnet.im

2001:df2:4c0::/48

Bhima Riddhi Broadband Private LimitedAS150630

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 21st February 2023

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2001:df2:4c0::/48 as seen from London, UK, read outward from the origin: AS150630 → AS55352 → AS55836 → AS64049 → AS51907. Each hop is listed with its network name beneath the graph.AS150630Bhima Riddhi Broa…OriginAS55352Microscan Interne…AS55836Reliance Jio Info…AS64049Reliance Jio Info…AS51907Kanton Zug

Seen from London, UK

  1. 1AS150630Bhima Riddhi Broadband Private LimitedINOrigin
    Peer of AS150630seen on 540 paths from 141 vantage points
  2. 2AS55352Microscan Internet LimitedIN
    Peer of AS55352seen on 9,184 paths from 141 vantage points
  3. 3AS55836Reliance Jio Infocomm LimitedIN
    Peer of AS55836seen on 571,522 paths from 141 vantage points
  4. 4AS64049Reliance Jio Infocomm Pte. Ltd.SG
    Peer of AS64049seen on 9,431 paths from 2 vantage points
  5. 5AS51907Kanton ZugCHVantage 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. Amsterdam150630553525583664049213151This path
  2. London, UK15063055352558366404951907Shown above
  3. Singapore150630553525583664049132337This path
  4. Sao Paulo150630553525583664049335632590This 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
India
Allocated
21st February 2023
Allocation block
2001:df2:4c0::/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:4c0::/48
ROA prefixAuthorised originMax length
2001:df2:4c0::/48AS150630/48
2001:df2:4c0::/48AS17665/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

No prefix of the same length in the same parent block is announced.

History

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