subnet.im

2405:3440:a::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

62 of 63 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 23rd August 2019

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 2405:3440:a::/48 as seen from Sao Paulo, read outward from the origin: AS138311 → AS138296 → AS9583 → AS4755 → AS6453 → AS35280. Each hop is listed with its network name beneath the graph.AS138311Limerick Technolo…OriginAS138296Juweriyah Network…AS9583Sify LimitedAS4755TATA Communicatio…AS6453TATA Communicatio…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS138311seen on 502 paths from 138 vantage points
  2. Peer of AS138296seen on 9,461 paths from 138 vantage points
  3. Peer of AS9583seen on 28,136 paths from 138 vantage points
  4. Peer of AS4755seen on 1,220,806 paths from 138 vantage points
  5. Peer of AS6453seen on 653,191 paths from 6 vantage points
  6. 6AS35280F5 Networks SARLFRVantage 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, UK13831113829695834755645335280This path
  2. Sao Paulo13831113829695834755645335280Shown above
  3. Amsterdam138311138296958347556453250918298This path
  4. Singapore1383111382969583475564536939132337This 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 62 of 63 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
23rd August 2019
Allocation block
2405:3440::/32
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 2405:3440:a::/48
ROA prefixAuthorised originMax length
2405:3440::/32AS138311/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 2405:3440:a::/48
PrefixAddressesOriginVisibility
2405:3440:b::/4865.5k × /64AS138311Limerick Technologies Pvt Ltd63/63

History

  1. AS13831126th October 2026 — present
  2. AS13831112th August 2026 — 25th October 2026
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.