Network · data from 2026-11-12
AS54110 CLEARLYIP1 - Modulis
Registry name: CLEARLYIP1 - Modulis, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54110, 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.
| 199.21.208.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 199.182.132.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 199.182.135.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 206.168.36.0/23 | Valid | RIR databaseARIN | 673 100% |
| 199.182.134.0/24 | Valid | RIR databaseARIN, RADB | 2 0%low visibility |
AS-SET
AS54110 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 12 are in fix.csv.
- ROA: none1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.21.208.0/24 | No ROA covers it. Add a ROA for AS54110, maxLength 24. |
Route objects not announced
Route objects with origin AS54110 whose prefix no peer sees AS54110 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.21.208.0/21 | ARIN | No ROA |
| 199.182.132.0/22 | ARIN, RADB | Valid |
| 199.182.133.0/24 | ARIN, RADB | Valid |
| 203.14.132.0/22 | RADB | No ROA |
| 203.14.132.0/24 | RADB | No ROA |
| 203.14.133.0/24 | RADB | No ROA |
| 203.14.134.0/24 | RADB | No ROA |
| 203.14.135.0/24 | RADB | No ROA |
| 208.90.24.0/21 | ARIN, RADB | No ROA |
| 2605:3880::/32 | RADB | No ROA |
| 2605:3880:16::/48 | ARIN | 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.