59.107.238.0/24
At a glance
Addresses
/24 block
Visibility
81 of 81 vantage points
RPKI
Registry
CNAllocated 22nd March 2006
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 AS207550seen on 8,134 paths from 81 vantage points
- Peer of AS214432seen on 32,136 paths from 81 vantage points
- Peer of AS17497seen on 45,181 paths from 143 vantage points
- Peer of AS3491seen on 42,387 paths from 32 vantage points
- Peer of AS6939seen on 988,025 paths from 1 vantage point
HK
GB
USOne 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, UK207550214432174973491129935280This path
- Sao Paulo207550214432174973491645335280This path
- Singapore2075502144321749734914766132337This path
- Oregon, US207550214432174973491693920130Shown above
- Amsterdam2075502144321749734916762250918298This 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
100%
Seen by 81 of 81 full-feed vantage points
Globally 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
- APNIC — Asia-Pacific
- Country
- China
- Allocated
- 22nd March 2006
- Allocation block
- 59.107.128.0/17
- 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.
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 |
|---|---|---|---|
| 59.107.239.0/24 | 256 | AS9304HGC Global Communications Limited | 81/81 |
History
- AS20755022nd 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.
Open 59.107.238.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.