SUBNET.IM

115.240.0.0/13

Reliance Jio Infocomm LimitedAS55836

At a glance

Addresses

524,288

/13 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 8th September 2008

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 115.240.0.0/13 as seen from Singapore, read outward from the origin: AS55836 → AS64049 → AS132337. Each hop is listed with its network name beneath the graph.AS55836Reliance Jio Info…OriginAS64049Reliance Jio Info…AS132337Axclusive

Seen from Singapore

  1. 1AS55836Reliance Jio Infocomm LimitedINOrigin
    Peer of AS55836seen on 571,522 paths from 141 vantage points
  2. 2AS64049Reliance Jio Infocomm Pte. Ltd.SG
    Peer of AS64049seen on 8,473 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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, UK55836640498529This path
  2. Singapore5583664049132337Shown above
  3. Amsterdam558366404934549213151This path
  4. Sao Paulo55836640493356266213This path
  5. Oregon, US5583664049693920130This 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

99%

Seen by 79 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
8th September 2008
Allocation block
115.240.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 115.240.0.0/13
ROA prefixAuthorised originMax length
115.240.0.0/13AS55836/13

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 115.240.0.0/13: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.115.240.0.0/13AS55836This prefix115.240.0.0/14AS55836115.240.0.0/15AS55836115.241.0.0/17AS55836115.242.0.0/17AS55836115.240.128.0/18AS55836+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

No less specific announcement covers this prefix.

Sibling prefixes

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

History

  1. AS5583612th 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 115.240.0.0/13 in the calculator/13 reference

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