SUBNET.IM

2407:2a00::/44

At a glance

Subnets

1,048,576 × /64

/44 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 18th February 2011

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.

  1. Amsterdam55832132220174394755645334549213151This path
  2. London, UK558321322201743947556453900251907This path
  3. Sao Paulo5583213222017439475564531295632590This path
  4. Singapore5583213222017439475564536939132337This 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
18th February 2011
Allocation block
2407:2a00::/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 2407:2a00::/44
ROA prefixAuthorised originMax length
2407:2a00::/44AS55832/44
2407:2a00::/32AS55832/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2407:2a00::/44: 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:2a00::/32AS558322407:2a00::/44AS55832This prefix2407:2a00:10::/44AS558322407:2a00:2::/48AS558322407:2a00:3::/48AS55832

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:2a00::/44
PrefixAddressesOriginVisibility
2407:2a00::/324.3B × /64AS55832HOME SYSTEMS PVT.LTD62/62

More specific announcements

Announcements contained within 2407:2a00::/44
PrefixAddressesOriginVisibility
2407:2a00:2::/4865.5k × /64AS55832HOME SYSTEMS PVT.LTD62/62
2407:2a00:3::/4865.5k × /64AS55832HOME SYSTEMS PVT.LTD62/62

Sibling prefixes

Prefixes of the same length sharing a parent block with 2407:2a00::/44
PrefixAddressesOriginVisibility
2407:2a00:10::/441M × /64AS55832HOME SYSTEMS PVT.LTD62/62

History

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