SUBNET.IM

2401:5e40:c100::/40

Industrial Cyber Security Center of ExcellenceAS63798

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

97%

60 of 62 vantage points

RPKI

No ROA

Registry

APNICJP

Allocated 23rd June 2017

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 2401:5e40:c100::/40, fanning out from AS63798 toward the vantage points that see it. Each path is written out in full beneath the graph.AS63798Industrial Cyber …OriginAS2907Science Informati…AS6939Hurricane Electri…AS213151Christian ElsenAS32590Valve CorporationAS132337AxclusiveAS41913Computerline GmbHAS34288Kantonsschule ZugAS51907Kanton Zug
  1. Amsterdam6379829076939213151This path
  2. Sao Paulo637982907693932590This path
  3. Singapore6379829076939132337This path
  4. London, UK6379829076939419133428851907This 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
Japan
Allocated
23rd June 2017
Allocation block
2401:5e40::/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 2401:5e40:c100::/40: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2401:5e40:8000::…AS637702401:5e40:c100::…AS63798This prefix

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 2401:5e40:c100::/40
PrefixAddressesOriginVisibility
2401:5e40:8000::/332.1B × /64AS63770Industrial Cyber Security Center of Excellence62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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