Network · data from 2026-11-12
AS22301 APC-CC-CUSTOMERS - RingSquared CC
Registry name: APC-CC-CUSTOMERS - RingSquared CC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22301, 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.
| 38.125.240.0/21 | No ROA | Other IRR onlyALTDB, RADB | 670 100% |
| 66.59.48.0/20 | No ROA | Other IRR onlyALTDB, RADB | 670 100% |
AS-SET
AS22301 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 5 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.125.240.0/21 | No ROA covers it. Add a ROA for AS22301, maxLength 21. |
| Route object: RIR | 38.125.240.0/21 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 66.59.48.0/20 | No ROA covers it. Add a ROA for AS22301, maxLength 20. |
| Route object: RIR | 66.59.48.0/20 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22301 whose prefix no peer sees AS22301 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.183.244.0/24 | 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.