45.115.24.0/24
At a glance
Addresses
/24 block
Visibility
55 of 76 vantage points
RPKI
Registry
HKAllocated 14th April 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS211422seen on 55 paths from 55 vantage points
- Peer of AS200010seen on 287 paths from 76 vantage points
- Peer of AS213382seen on 212 paths from 65 vantage points
- Peer of AS264409seen on 18,316 paths from 111 vantage points
- Peer of AS3257seen on 225,174 paths from 52 vantage points
- Peer of AS1299seen on 321,664 paths from 1 vantage point
- Peer of AS8551seen on 1,077,002 paths from 1 vantage point
TR
FR
BR
US
SE
IL
PSOne 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
- Sao Paulo21142220001021338226440935280This path
- Amsterdam211422200010213382264409250918298This path
- London, UK21142220001021338226440969398529This path
- Oregon, US21142220001021338226440932571299855142013Shown 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
72%
Seen by 55 of 76 full-feed vantage points
Partially 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
- 14th April 2015
- Allocation block
- 45.115.24.0/22
- 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 45.115.25.0/24 | 256 | AS206264Amarutu Technology Ltd | 76/76 |
History
- AS21142231st October 2026 — present
- AS2081855th November 2026 — 10th November 2026
- AS20818529th October 2026 — 5th November 2026
- AS21142231st October 2026 — 31st October 2026
- AS21142222nd October 2026 — 30th October 2026
- AS20818512th August 2026 — 6th October 2026
- AS21142227th September 2026 — 5th October 2026
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 45.115.24.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.