2403:ad80:5000::/38
At a glance
Subnets
/38 block
Visibility
63 of 64 vantage points
RPKI
Registry
HKAllocated 23rd November 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS134835seen on 144 paths from 144 vantage points
- Peer of AS138195seen on 2,406 paths from 144 vantage points
- Peer of AS150684seen on 2,892 paths from 144 vantage points
- Peer of AS3491seen on 134,137 paths from 63 vantage points
- Peer of AS1299seen on 513,361 paths from 6 vantage points
KR
SE
FROne 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
- Amsterdam134835138195150684349117432590This path
- London, UK1348351381951506843491129935280Shown above
- Sao Paulo1348351381951506843491645335280This path
- Singapore13483513819515068434916939132337This 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 63 of 64 full-feed vantage points
Globally propagatedObserved 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
- Hong Kong SAR China
- Allocated
- 23rd November 2015
- Allocation block
- 2403:ad80::/32
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2403:ad80:5000::/38 | AS134835 | /38 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2403:ad80:5020::/48 | 65.5k × /64 | AS219329FLASH EDGE INFORMATION TECHNOLOGY LLC | 64/64 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS13483523rd September 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.