SUBNET.IM

125.20.0.0/15

Bharti Airtel Ltd.AS9498

At a glance

Addresses

131,072

/15 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 3rd August 2005

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 125.20.0.0/15 as seen from Amsterdam, read outward from the origin: AS9498 → AS213151. Each hop is listed with its network name beneath the graph.AS9498Bharti Airtel Ltd.OriginAS213151Christian Elsen

Seen from Amsterdam

  1. 1AS9498Bharti Airtel Ltd.INOrigin
    Peer of AS9498seen on 35,152 paths from 2 vantage points
  2. 2AS213151Christian 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. Amsterdam9498213151Shown above
  2. London, UK94988529This path
  3. Singapore9498132337This path
  4. Oregon, US9498693920130This path
  5. Sao Paulo949834913356266213This 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

100%

Seen by 80 of 80 full-feed vantage points

Globally propagated

Observed at 5 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
3rd August 2005
Allocation block
125.16.0.0/13
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 125.20.0.0/15
ROA prefixAuthorised originMax length
125.20.0.0/15AS9498/24
125.16.0.0/13AS9498/13

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 125.20.0.0/15: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.125.16.0.0/13AS9498125.20.0.0/15AS9498This prefix125.20.0.0/16AS9498125.21.0.0/16AS9498125.20.32.0/21AS9498125.20.216.0/21AS9498125.21.88.0/21AS9498+19 more

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 125.20.0.0/15
PrefixAddressesOriginVisibility
125.16.0.0/13524kAS9498Bharti Airtel Ltd.79/80

Sibling prefixes

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

History

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

Open 125.20.0.0/15 in the calculator/15 reference

Routing data derived from RouteViews MRT archives and public registry data.