subnet.im

2405:6040::/32

Airgenie Communications Private LimitedAS134021

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 9th October 2019

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 2405:6040::/32 as seen from London, UK, read outward from the origin: AS134021 → AS9583 → AS8220 → AS15576 → AS51907. Each hop is listed with its network name beneath the graph.AS134021Airgenie Communic…OriginAS9583Sify LimitedAS8220COLTAS15576NTS workspace AGAS51907Kanton Zug

Seen from London, UK

  1. 1AS134021Airgenie Communications Private LimitedINOrigin
    Peer of AS134021seen on 2,366 paths from 142 vantage points
  2. 2AS9583Sify LimitedIN
    Peer of AS9583seen on 2,823 paths from 14 vantage points
  3. 3AS8220COLTGB
    Peer of AS8220seen on 93,898 paths from 4 vantage points
  4. 4AS15576NTS workspace AGCH
    Peer of AS15576seen on 442,038 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. Singapore1340219583132337This path
  2. Amsterdam13402195836939213151This path
  3. Sao Paulo1340219583693932590This path
  4. London, UK134021958382201557651907Shown 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

100%

Seen by 62 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
9th October 2019
Allocation block
2405:6040::/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:6040::/32
ROA prefixAuthorised originMax length
2405:6040::/32AS134021/40

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2405:6040::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2405:6040::/32AS134021This prefix2405:6040::/34AS1340212405:6040:4000::…AS1340212405:6040:8000::…AS1340212405:6040:c000::…AS134021

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. AS13402112th 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.