SUBNET.IM

2403:8340::/36

Akari NetworksAS38136

At a glance

Subnets

268,435,456 × /64

/36 block

Visibility

94%

58 of 62 vantage points

RPKI

No ROA

Registry

APNICTW

Allocated 6th September 2018

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 2403:8340::/36 as seen from Singapore, read outward from the origin: AS38136 → AS983 → AS137409 → AS132337. Each hop is listed with its network name beneath the graph.AS38136Akari NetworksOriginAS983Akari Networks LLCAS137409GSL Networks Pty …AS132337Axclusive

Seen from Singapore

  1. 1AS38136Akari NetworksHKOrigin
    Peer of AS38136seen on 7,692 paths from 142 vantage points
  2. 2AS983Akari Networks LLCUS
    Peer of AS983seen on 3,977 paths from 142 vantage points
  3. 3AS137409GSL Networks Pty LTDAU
    Peer of AS137409seen on 6,062 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Sao Paulo3813698313740932590This path
  2. Singapore38136983137409132337Shown above
  3. Amsterdam3813698334916939213151This path
  4. London, UK38136983349133561557651907This 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

94%

Seen by 58 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
Taiwan
Allocated
6th September 2018
Allocation block
2403:8340::/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 2403:8340::/36: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2403:8340::/32AS381362403:8340::/36AS38136This prefix2403:8340:1000::…AS38136

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 2403:8340::/36
PrefixAddressesOriginVisibility
2403:8340::/324.3B × /64AS38136Akari Networks60/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2403:8340::/36
PrefixAddressesOriginVisibility
2403:8340:1000::/36268M × /64AS38136Akari Networks62/62

History

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