38.54.16.0/23
Kaopu Cloud HK LimitedAS138915
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/23 block
Visibility
61 of 80 vantage points
RPKI
Registry
USAllocated 16th April 1991
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS154177seen on 24,057 paths from 80 vantage points
- Peer of AS138915seen on 1,272 paths from 54 vantage points
- Peer of AS7473seen on 159,605 paths from 111 vantage points
- Peer of AS6461seen on 62,575 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
HK
SG
DEOne 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
- Singapore138915132337This path
- London, UK154177138915747364618529This path
- Sao Paulo15417713891534913356266213This path
- Oregon, US1541771389153491693920130This path
- Amsterdam1541771389157473646134549213151Shown above
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
76%
Seen by 61 of 80 full-feed vantage points
Partially propagatedObserved at 5 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
- ARIN — North America
- Country
- United States
- Allocated
- 16th April 1991
- Allocation block
- 38.0.0.0/8
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 38.0.0.0/8 | 16.8M | AS174Cogent Communications, LLC | 78/80 |
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
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.
Open 38.54.16.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.