SUBNET.IM

2407:a300:2::/48

DIGITAL NETWORK ASSOCIATES PRIVATE LIMITEDAS132497

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

No ROA

Registry

APNICIN

Allocated 25th July 2013

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 4 observed paths to 2407:a300:2::/48, fanning out from AS132497 toward the vantage points that see it. Each path is written out in full beneath the graph.AS132497DIGITAL NETWORK A…OriginAS17762Tata Teleservices…AS4755TATA Communicatio…AS6453TATA Communicatio…AS34549meerfarbig GmbH &…AS213151Christian ElsenAS9002RETN LimitedAS51907Kanton ZugAS12956Telxius (Telefoni…AS32590Valve CorporationAS6939Hurricane Electri…AS132337Axclusive
  1. Amsterdam132497177624755645334549213151This path
  2. London, UK1324971776247556453900251907This path
  3. Sao Paulo13249717762475564531295632590This path
  4. Singapore13249717762475564536939132337This 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 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
25th July 2013
Allocation block
2407:a300::/32
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2407:a300:2::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2407:a300::/32AS1324972407:a300:2::/48AS132497This prefix2407:a300:3::/48AS132497

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 2407:a300:2::/48
PrefixAddressesOriginVisibility
2407:a300::/324.3B × /64AS132497DIGITAL NETWORK ASSOCIATES PRIVATE LIMITED62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2407:a300:2::/48
PrefixAddressesOriginVisibility
2407:a300:3::/4865.5k × /64AS132497DIGITAL NETWORK ASSOCIATES PRIVATE LIMITED62/62

History

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