Network · data from 2026-11-12
AS17976 CamGSM
Registry name: CamGSM-CELLCARD-AS-AP - CAMGSM Company Ltd, KH · PeeringDB
59IPv4 routes
100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
34Route objects not announced
registered with origin AS17976, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS17976, 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.
| 45.201.180.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.201.144.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.145.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.146.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.147.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.152.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.153.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.154.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.158.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.159.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.161.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.201.163.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 203.144.92.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.144.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.193.204.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.64.0/19 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.64.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.66.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.68.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.72.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.76.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.80.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.84.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.88.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.92.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.93.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.94.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.144.95.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 45.201.138.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 103.193.207.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.73.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.76.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.79.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.80.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.81.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.87.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 203.144.88.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 103.193.206.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.69.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.72.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.75.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.82.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.83.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.86.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 203.144.91.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 45.201.139.0/24 | Valid | RIR databaseAFRINIC, RADB | 667 99% |
| 203.144.77.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 667 99% |
| 103.193.204.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 665 99% |
| 203.144.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
AS-SET
AS17976's PeeringDB record names no 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 46 are in fix.csv.
- Route object: RIR12
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.201.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.144.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.145.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.147.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.152.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.153.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.154.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.158.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.159.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17976 whose prefix no peer sees AS17976 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.201.138.0/23 | RADB | Valid |
| 45.201.172.0/24 | RADB | Valid |
| 45.201.173.0/24 | RADB | Valid |
| 45.201.176.0/24 | RADB | Valid |
| 45.201.177.0/24 | RADB | Valid |
| 45.201.178.0/24 | RADB | Valid |
| 45.201.179.0/24 | RADB | Valid |
| 103.19.204.0/24 | RADB | No ROA |
| 103.193.204.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.193.205.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.193.206.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.64.0/20 | APNIC, NTTCOM, RADB | Valid |
| 203.144.64.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.144.64.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.66.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.68.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.70.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.72.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.144.72.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.74.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.76.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.78.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.80.0/20 | APNIC, NTTCOM, RADB | Valid |
| 203.144.80.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.144.80.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.82.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.84.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.86.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.88.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.144.88.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.90.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.92.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.144.94.0/23 | APNIC, NTTCOM, RADB | Valid |
| 2401:4d80::/32 | 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.