103.145.58.0/23
At a glance
Addresses
/23 block
Visibility
28 of 80 vantage points
RPKI
Registry
HKAllocated 14th November 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS997seen on 186 paths from 62 vantage points
- Peer of AS23961seen on 6,671 paths from 141 vantage points
- Peer of AS137409seen on 10,471 paths from 15 vantage points
- Peer of AS6830seen on 2,150 paths from 2 vantage points
- Peer of AS58299seen on 25,347 paths from 2 vantage points
- Peer of AS41051seen on 25,385 paths from 2 vantage points
SG
US
AU
EU
CH
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
- London, UK997239611374098529This path
- Singapore997239611374098966132337This path
- Sao Paulo997239611374097195262355266213This path
- Amsterdam9972396113740968305829941051213151Shown 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
35%
Seen by 28 of 80 full-feed vantage points
Seen by few vantage pointsObserved 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
- APNIC — Asia-Pacific
- Country
- Hong Kong SAR China
- Allocated
- 14th November 2019
- Allocation block
- 103.145.58.0/23
- 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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 103.145.58.0/24 | 256 | AS997Beyotta Services LLP | 80/80 |
| 103.145.59.0/24 | 256 | AS997Beyotta Services LLP | 80/80 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS99712th 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.
Open 103.145.58.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.