110.43.152.0/21
China Telecom Shanghai IDC NetworkAS4811
China Unicom Shanghai networkAS17621
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/21 block
Visibility
59 of 80 vantage points
RPKI
Registry
CNAllocated 4th March 2009
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS4811seen on 223,333 paths from 141 vantage points
- Peer of AS4134seen on 25,463 paths from 3 vantage points
- Peer of AS4766seen on 70,419 paths from 2 vantage points
KR
SGOne 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, UK481141348529This path
- Sao Paulo481141343356266213This path
- Singapore481141344766132337Shown above
- Oregon, US48114134693920130This path
- Amsterdam176214837551134549213151This 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
74%
Seen by 59 of 80 full-feed vantage points
Partially 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
- 4th March 2009
- Allocation block
- 110.40.0.0/14
- 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 110.43.128.0/19 | 8.2k | AS59019Beijing Kingsoft Cloud Internet Technology Co., Ltd | 1/80 |
| 110.43.0.0/16 | 65.5k | AS59019Beijing Kingsoft Cloud Internet Technology Co., Ltd | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 110.43.144.0/21 | 2k | AS4811China Telecom Shanghai IDC Network | 59/80 |
| 110.43.144.0/21 | 2k | AS17621China Unicom Shanghai network | 21/80 |
History
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 110.43.152.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.