Network · data from 2026-11-12
AS138607 CAMBO-AS-AP - CAMBO (HK) TECHNOLOGY (I.S.P) CO., LIMITED
Registry name: CAMBO-AS-AP - CAMBO (HK) TECHNOLOGY (I.S.P) CO., LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138607, 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.232.151.0/24 | Invalid: maxLength | Nonecovered by 103.232.148.0/22 | 2 0%low visibility |
| 103.134.140.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.134.141.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.97.82.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 78.138.12.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 78.138.13.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.232.148.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.232.149.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 144.48.70.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 144.48.71.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 144.48.188.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 144.48.189.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 144.48.190.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 144.48.191.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 213.255.200.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 213.255.201.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 213.255.202.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 213.255.203.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.232.150.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 144.48.69.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
AS-SET
AS138607 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 14 are in fix.csv.
- ROA: maxLength1
- ROA: none3
- Route object: none1
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.232.151.0/24 | ROA 103.232.148.0/22 AS138607 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.232.151.0/24. |
| Route object: none | 103.232.151.0/24 | No route object for it. A route object for 103.232.148.0/22 with origin AS138607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138607 in the RIR database for the space. |
| ROA: none | 103.134.140.0/24 | No ROA covers it. Add a ROA for AS138607, maxLength 24. |
| Route object: RIR | 103.134.140.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.134.141.0/24 | No ROA covers it. Add a ROA for AS138607, maxLength 24. |
| Route object: RIR | 103.134.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.97.82.0/24 | No ROA covers it. Add a ROA for AS138607, maxLength 24. |
| Route object: RIR | 103.97.82.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138607 whose prefix no peer sees AS138607 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 78.138.12.0/22 | RADB | No ROA |
| 103.232.148.0/22 | APNIC, RADB | Valid |
| 144.48.68.0/22 | APNIC, RADB | Valid |
| 144.48.68.0/24 | APNIC, RADB | Valid |
| 144.48.188.0/22 | APNIC, RADB | Valid |
| 213.255.200.0/22 | APNIC, 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.