Network · data from 2026-11-12
AS36337 CRITICALCONTROL - Critical Control Technologies Inc.
Registry name: CRITICALCONTROL - Critical Control Technologies Inc., CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36337, 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.
| 192.208.10.0/24 | Valid | Other IRR onlyBELL, RADB | 670 100% |
AS-SET
AS36337 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.
- Route object: RIR1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 192.208.10.0/24 | Route object only in BELL, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36337 whose prefix no peer sees AS36337 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.208.2.0/24 | BELL | Invalid: origin |
| 192.208.3.0/24 | BELL | Invalid: origin |
| 192.208.4.0/24 | BELL | Invalid: origin |
| 192.208.5.0/24 | BELL | Invalid: origin |
| 192.208.6.0/24 | BELL | Invalid: origin |
| 192.208.7.0/24 | BELL | Invalid: origin |
| 192.208.8.0/24 | BELL | Invalid: origin |
| 192.208.9.0/24 | BELL | Invalid: origin |
| 192.208.11.0/24 | BELL | No ROA |
| 192.208.12.0/24 | BELL | Invalid: origin |
| 192.208.13.0/24 | BELL | No ROA |
| 192.208.14.0/24 | BELL | Invalid: origin |
| 192.208.15.0/24 | BELL | Invalid: origin |
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.