SUBNET.IM

240a:a85e::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 1st April 2021

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 240a:a85e::/32 as seen from London, UK, read outward from the origin: AS144792 → AS38255 → AS6939 → AS51907. Each hop is listed with its network name beneath the graph.AS144792APNIC ASN blockOriginAS38255China Education a…AS6939Hurricane Electri…AS51907Kanton Zug

Seen from London, UK

  1. Peer of AS144792seen on 60 paths from 60 vantage points
  2. Peer of AS38255seen on 225,483 paths from 135 vantage points
  3. Peer of AS6939seen on 132,979 paths from 2 vantage points
  4. 4AS51907Kanton 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. Amsterdam144792382556939213151This path
  2. London, UK14479238255693951907Shown above
  3. Sao Paulo14479238255693932590This path
  4. Singapore144792382556939132337This 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

97%

Seen by 60 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
China
Allocated
1st April 2021
Allocation block
240a:a000::/20
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 240a:a85e::/32
ROA prefixAuthorised originMax length
240a:a85e::/32AS144792/32
240a:a85e::/32AS23910/32
240a:a85e::/32AS4538/32

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 240a:a85e::/32
PrefixAddressesOriginVisibility
240a:a85f::/324.3B × /64AS4538China Education and Research Network Center2/62
240a:a85f::/324.3B × /64AS144793APNIC ASN block60/62

History

  1. AS453812th August 2026 present
  2. AS14479212th 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.