Network · data from 2026-11-12
AS17045 NGA911-CALI-A - NGA 911
Registry name: NGA911-CALI-A - NGA 911, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17045, 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.
| 2605:84c0:48::/46 | No ROA | Other origin onlycovered by 2605:84c0::/32 | 635 100% |
| 2605:84c0:48::/47 | No ROA | Other origin onlycovered by 2605:84c0::/32 | 635 100% |
AS-SET
AS17045 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 7 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2605:84c0:48::/46 | No ROA covers it. Add a ROA for AS17045, maxLength 46. |
| Route object: none | 2605:84c0:48::/46 | Route objects for it name AS46887. A route object for 2605:84c0::/32 with origin AS17045 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17045 in the RIR database for the space. |
| ROA: none | 2605:84c0:48::/47 | No ROA covers it. Add a ROA for AS17045, maxLength 47. |
| Route object: none | 2605:84c0:48::/47 | Route objects for it name AS46887. A route object for 2605:84c0::/32 with origin AS17045 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17045 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17045 whose prefix no peer sees AS17045 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.153.240.0/24 | RADB | Valid |
| 158.51.225.0/24 | ARIN, RADB | Valid |
| 2605:84c0::/32 | 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.