Network · data from 2026-11-12
AS22238 DARPA - Defense Advanced Research Projects Agency(DARPA)
Registry name: DARPA - Defense Advanced Research Projects Agency(DARPA), US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22238, 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.
| 158.63.2.0/24 | No ROA | Nonecovered by 158.63.0.0/16 | 673 100% |
| 158.63.4.0/24 | No ROA | Nonecovered by 158.63.0.0/16 | 673 100% |
| 158.63.250.0/24 | No ROA | Nonecovered by 158.63.0.0/16 | 673 100% |
| 158.63.254.0/24 | No ROA | Nonecovered by 158.63.0.0/16 | 673 100% |
| 192.5.18.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.187.8.0/24 | No ROA | Other IRR onlyRADB | 556 83% |
AS-SET
AS22238 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.
- ROA: none6
- Route object: none4
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 158.63.2.0/24 | No ROA covers it. Add a ROA for AS22238, maxLength 24. |
| Route object: none | 158.63.2.0/24 | No route object for it. A route object for 158.63.0.0/16 with origin AS22238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22238 in the RIR database for the space. |
| ROA: none | 158.63.4.0/24 | No ROA covers it. Add a ROA for AS22238, maxLength 24. |
| Route object: none | 158.63.4.0/24 | No route object for it. A route object for 158.63.0.0/16 with origin AS22238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22238 in the RIR database for the space. |
| ROA: none | 158.63.250.0/24 | No ROA covers it. Add a ROA for AS22238, maxLength 24. |
| Route object: none | 158.63.250.0/24 | No route object for it. A route object for 158.63.0.0/16 with origin AS22238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22238 in the RIR database for the space. |
| ROA: none | 158.63.254.0/24 | No ROA covers it. Add a ROA for AS22238, maxLength 24. |
| Route object: none | 158.63.254.0/24 | No route object for it. A route object for 158.63.0.0/16 with origin AS22238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22238 in the RIR database for the space. |
| ROA: none | 192.5.18.0/24 | No ROA covers it. Add a ROA for AS22238, maxLength 24. |
| Route object: RIR | 192.5.18.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.187.8.0/24 | No ROA covers it. Add a ROA for AS22238, maxLength 24. |
| Route object: RIR | 192.187.8.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22238 whose prefix no peer sees AS22238 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.94.39.0/24 | AFRINIC | Invalid: origin |
| 158.63.0.0/16 | 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.