Network · data from 2026-11-12
AS22030 ZIPCON-AS-1 - Zipcon LLC
Registry name: ZIPCON-AS-1 - Zipcon LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22030, 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.246.122.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS22030 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 10 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.246.122.0/23 | No ROA covers it. Add a ROA for AS22030, maxLength 23. |
| Route object: RIR | 38.246.122.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22030 whose prefix no peer sees AS22030 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.48.21.0/24 | RADB | No ROA |
| 204.238.32.0/24 | RADB | No ROA |
| 209.221.136.0/22 | ALTDB, RADB | No ROA |
| 209.221.140.0/24 | ALTDB, RADB | No ROA |
| 209.221.144.0/24 | ALTDB, RADB | No ROA |
| 209.221.148.0/24 | ALTDB, RADB | No ROA |
| 209.221.166.0/23 | ALTDB, RADB | No ROA |
| 209.221.184.0/23 | ALTDB, 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.