Network · data from 2026-11-12
AS58854 kaopy - Kaopu Cloud
Registry name: kaopy - Kaopu Cloud, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58854, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 211.155.96.0/22 | Valid | Other origin onlycovered by 211.155.96.0/19 | 669 99% |
| 211.155.115.0/24 | Valid | Nonecovered by 211.155.96.0/19 | 667 99% |
| 211.155.100.0/22 | Valid | Other origin onlycovered by 211.155.96.0/19 | 666 99% |
| 211.155.104.0/22 | Valid | Other origin onlycovered by 211.155.96.0/19 | 658 98% |
| 2407:7d00:1::/48 | Valid | Other origin only | 630 99% |
| 27.0.132.0/22 | Valid | Other origin only | 628 93% |
| 103.27.4.0/22 | Valid | Other origin only | 31 5%low visibility |
| 103.27.4.0/24 | Valid | None | 31 5%low visibility |
| 103.27.5.0/24 | Valid | None | 31 5%low visibility |
| 103.27.6.0/24 | Valid | None | 31 5%low visibility |
| 103.27.7.0/24 | Valid | None | 31 5%low visibility |
| 103.236.252.0/22 | Valid | Other IRR onlyRADB | 670 100% |
AS-SET
AS58854 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.
- Route object: none11
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 211.155.96.0/22 | Route objects for it name AS138915. A route object for 211.155.96.0/19 with origin AS58854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 211.155.115.0/24 | No route object for it. A route object for 211.155.96.0/19 with origin AS58854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 211.155.100.0/22 | Route objects for it name AS138915. A route object for 211.155.96.0/19 with origin AS58854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 211.155.104.0/22 | Route objects for it name AS133774, AS138915. A route object for 211.155.96.0/19 with origin AS58854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 2407:7d00:1::/48 | Route objects for it name AS138915. Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 27.0.132.0/22 | Route objects for it name AS133774. Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 103.27.4.0/22 | Route objects for it name AS4837. Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 103.27.4.0/24 | No route object for it. Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 103.27.5.0/24 | No route object for it. Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 103.27.6.0/24 | No route object for it. Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: none | 103.27.7.0/24 | No route object for it. Add a route object with origin AS58854 in the RIR database for the space. |
| Route object: RIR | 103.236.252.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58854 whose prefix no peer sees AS58854 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 211.155.96.0/19 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.