Network · data from 2026-11-12
AS33614 CITY-OF-SAN-DIEGO - City of San Diego
Registry name: CITY-OF-SAN-DIEGO - City of San Diego, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33614, 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.
| 156.29.3.0/24 | No ROA | Nonecovered by 156.29.0.0/16 | 672 100% |
| 156.29.4.0/24 | No ROA | Nonecovered by 156.29.0.0/16 | 672 100% |
| 156.29.5.0/24 | No ROA | Nonecovered by 156.29.0.0/16 | 672 100% |
| 156.29.6.0/24 | No ROA | Nonecovered by 156.29.0.0/16 | 672 100% |
| 156.29.7.0/24 | No ROA | Nonecovered by 156.29.0.0/16 | 672 100% |
| 156.29.64.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS33614 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 21 are in fix.csv.
- ROA: none6
- Route object: none5
- Route object: RIR1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 156.29.3.0/24 | No ROA covers it. Add a ROA for AS33614, maxLength 24. |
| Route object: none | 156.29.3.0/24 | No route object for it. A route object for 156.29.0.0/16 with origin AS33614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33614 in the RIR database for the space. |
| ROA: none | 156.29.4.0/24 | No ROA covers it. Add a ROA for AS33614, maxLength 24. |
| Route object: none | 156.29.4.0/24 | No route object for it. A route object for 156.29.0.0/16 with origin AS33614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33614 in the RIR database for the space. |
| ROA: none | 156.29.5.0/24 | No ROA covers it. Add a ROA for AS33614, maxLength 24. |
| Route object: none | 156.29.5.0/24 | No route object for it. A route object for 156.29.0.0/16 with origin AS33614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33614 in the RIR database for the space. |
| ROA: none | 156.29.6.0/24 | No ROA covers it. Add a ROA for AS33614, maxLength 24. |
| Route object: none | 156.29.6.0/24 | No route object for it. A route object for 156.29.0.0/16 with origin AS33614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33614 in the RIR database for the space. |
| ROA: none | 156.29.7.0/24 | No ROA covers it. Add a ROA for AS33614, maxLength 24. |
| Route object: none | 156.29.7.0/24 | No route object for it. A route object for 156.29.0.0/16 with origin AS33614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33614 in the RIR database for the space. |
| ROA: none | 156.29.64.0/24 | No ROA covers it. Add a ROA for AS33614, maxLength 24. |
| Route object: RIR | 156.29.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS33614 whose prefix no peer sees AS33614 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.29.0.0/16 | RADB | No ROA |
| 156.29.37.0/24 | RADB | No ROA |
| 156.29.63.0/24 | RADB | No ROA |
| 156.29.114.0/24 | RADB | No ROA |
| 156.29.126.0/23 | RADB | No ROA |
| 156.29.176.0/20 | RADB | No ROA |
| 156.29.248.0/21 | RADB | No ROA |
| 198.180.16.0/20 | RADB | No ROA |
| 198.180.31.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.