SUBNET.IM

2402:b801::/40

Neighbourhood CableAS18371

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

97%

60 of 62 vantage points

RPKI

No ROA

Registry

APNICAU

Allocated 6th August 2012

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 2402:b801::/40, fanning out from AS18371 toward the vantage points that see it. Each path is written out in full beneath the graph.AS18371Neighbourhood Cab…OriginAS2764AAPT LimitedAS4826Vocus Connect Int…AS132337AxclusiveAS6939Hurricane Electri…AS213151Christian ElsenAS9002RETN LimitedAS51907Kanton ZugAS7195EdgeUnoAS32590Valve Corporation
  1. Singapore1837127644826132337This path
  2. Amsterdam18371276448266939213151This path
  3. London, UK1837127644826900251907This path
  4. Sao Paulo1837127644826719532590This 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
Australia
Allocated
6th August 2012
Allocation block
2402:b801::/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.

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 2402:b801::/40
PrefixAddressesOriginVisibility
2402:b801:100::/4016.8M × /64AS18371Neighbourhood Cable60/62

History

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