SUBNET.IM

2404:ff40:7000::/36

Zenlayer IncAS4229

Zenlayer IncAS21859

Announced by more than one origin AS (MOAS).

At a glance

Subnets

268,435,456 × /64

/36 block

Visibility

97%

60 of 62 vantage points

RPKI

No ROA

Registry

APNICSG

Allocated 28th June 2019

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 2404:ff40:7000::/36, fanning out from AS4229 toward the vantage points that see it. Each path is written out in full beneath the graph.AS4229Zenlayer IncOriginAS132337AxclusiveAS6939Hurricane Electri…AS213151Christian ElsenAS32590Valve CorporationAS3491PCCW Global (HK) …AS9002RETN LimitedAS51907Kanton Zug
  1. Singapore4229132337This path
  2. Amsterdam42296939213151This path
  3. Sao Paulo4229693932590This path
  4. London, UK42293491900251907This 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
Singapore
Allocated
28th June 2019
Allocation block
2404:ff40::/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 2404:ff40:7000::/36
PrefixAddressesOriginVisibility
2404:ff40:6000::/36268M × /64AS4229Zenlayer Inc62/62

History

  1. AS2185912th August 2026 — present
  2. AS422912th 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.