Network · data from 2026-11-12
AS138643 CXICL-AS-AP - XINYUAN INTERCONNECT COMPANY LTD
Registry name: CXICL-AS-AP - XINYUAN INTERCONNECT COMPANY LTD, KH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138643, 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.
| 103.49.41.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.49.42.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 45.134.98.0/24 | Valid | Other origin only | 2 0%low visibility |
| 23.226.57.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 103.49.43.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 82.23.246.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 103.158.160.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 103.158.161.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS138643 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 11 are in fix.csv.
- ROA: origin2
- Route object: none3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.49.41.0/24 | ROAs covering it name AS834, not AS138643. If AS138643 should announce it, add a ROA for AS138643. |
| Route object: none | 103.49.41.0/24 | Route objects for it name AS834. Add a route object with origin AS138643 in the RIR database for the space. |
| ROA: origin | 103.49.42.0/24 | ROAs covering it name AS834, not AS138643. If AS138643 should announce it, add a ROA for AS138643. |
| Route object: none | 103.49.42.0/24 | Route objects for it name AS834. Add a route object with origin AS138643 in the RIR database for the space. |
| Route object: none | 45.134.98.0/24 | Route objects for it name AS140723. Add a route object with origin AS138643 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138643 whose prefix no peer sees AS138643 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.248.217.0/24 | ARIN, RADB | Valid |
| 102.220.88.0/24 | RADB | No ROA |
| 102.220.90.0/24 | RADB | No ROA |
| 102.220.91.0/24 | RADB | No ROA |
| 103.135.114.0/23 | RADB | No ROA |
| 156.234.0.0/24 | RADB | Valid |
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.