58.23.0.0/16
Not announced at this prefix length
We do not see 58.23.0.0/16 announced as its own route. The most specific announcement covering it is 58.22.0.0/15, originated by AS4837 (China Unicom Backbone). Traffic to addresses in this block follows that route.
At a glance
Addresses
/16 block
Visibility
RPKI
Registry
CNAllocated 29th April 2005
AS paths to this prefix
No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.
Registry and RPKI
- RIR
- APNIC — Asia-Pacific
- Country
- China
- Allocated
- 29th April 2005
- Allocation block
- 58.22.0.0/15
- Status
- allocated
- Origin validation
- Unknown
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 58.22.0.0/15 | AS4837 | /15 |
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 |
|---|---|---|---|
| 58.22.0.0/15 | 131k | AS4837China Unicom Backbone | 80/81 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 58.23.0.0/24 | 256 | AS4837China Unicom Backbone | 81/81 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS483722nd September 2026 — 24th September 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 58.23.0.0/16 in the calculator/16 reference
Routing data derived from RouteViews MRT archives and public registry data.