223.9.200.0/21
At a glance
Addresses
/21 block
Visibility
9 of 76 vantage points
RPKI
Registry
CNAllocated 1st July 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS132153seen on 633 paths from 137 vantage points
- Peer of AS4134seen on 1,477 paths from 22 vantage points
- Peer of AS6461seen on 8,377 paths from 9 vantage points
- Peer of AS7473seen on 3,922 paths from 3 vantage points
- Peer of AS9304seen on 2,043 paths from 1 vantage point
- Peer of AS38623seen on 83,119 paths from 1 vantage point
US
SG
HK
KHOne 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
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
12%
Seen by 9 of 76 full-feed vantage points
Seen by few vantage pointsObserved 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
- China
- Allocated
- 1st July 2010
- Allocation block
- 223.8.0.0/13
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 223.8.0.0/13 | AS4134 | /13 |
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 |
|---|---|---|---|
| 223.8.0.0/13 | 524k | AS4134China Telecom Backbone | 75/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 223.9.192.0/21 | 2k | AS142404China Telecom | 9/76 |
History
- AS13215312th October 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 223.9.200.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.