subnet.im

240b:e003::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

APNICCN

Allocated 22nd December 2022

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 240b:e003::/32 as seen from London, UK, read outward from the origin: AS24363 → AS23910 → AS23911 → AS6939 → AS51907. Each hop is listed with its network name beneath the graph.AS24363CERNET2 IX at Sha…OriginAS23910China Next Genera…AS23911China Next Genera…AS6939Hurricane Electri…AS51907Kanton Zug

Seen from London, UK

  1. Peer of AS24363seen on 1,037 paths from 61 vantage points
  2. Peer of AS23910seen on 5,200 paths from 62 vantage points
  3. Peer of AS23911seen on 8,685 paths from 56 vantage points
  4. Peer of AS6939seen on 132,979 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. Amsterdam2436323910239116939213151This path
  2. London, UK243632391023911693951907Shown above
  3. Sao Paulo243632391023911693932590This path
  4. Singapore2436323910239116939132337This 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 61 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
22nd December 2022
Allocation block
240b:e000::/26
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.

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 240b:e003::/32
PrefixAddressesOriginVisibility
240b:e002::/324.3B × /64AS4538China Education and Research Network Center1/62
240b:e002::/324.3B × /64AS138371CERNET2 regional IX at Ocean University of China61/62

History

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