Network · data from 2026-11-12
AS6966 USDOS - U.S. Department of State
Registry name: USDOS - U.S. Department of State, US · not in PeeringDB
17IPv4 routes
0.0% RPKI valid · 11.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
17No ROA
15 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS6966, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS6966, 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.
| 169.252.0.0/17 | No ROA | Nonecovered by 169.252.0.0/16 | 673 100% |
| 169.252.80.0/20 | No ROA | Nonecovered by 169.252.0.0/16 | 673 100% |
| 169.252.80.0/24 | No ROA | Nonecovered by 169.252.0.0/16 | 673 100% |
| 169.252.81.0/24 | No ROA | Nonecovered by 169.252.0.0/16 | 673 100% |
| 169.252.128.0/17 | No ROA | Nonecovered by 169.252.0.0/16 | 673 100% |
| 169.253.0.0/17 | No ROA | Nonecovered by 169.253.0.0/16 | 673 100% |
| 169.253.4.0/24 | No ROA | Nonecovered by 169.253.0.0/16 | 673 100% |
| 169.253.6.0/24 | No ROA | Nonecovered by 169.253.0.0/16 | 673 100% |
| 169.253.40.0/24 | No ROA | Nonecovered by 169.253.0.0/16 | 673 100% |
| 169.253.128.0/17 | No ROA | Nonecovered by 169.253.0.0/16 | 673 100% |
| 169.253.160.0/19 | No ROA | Nonecovered by 169.253.0.0/16 | 673 100% |
| 169.253.188.0/24 | No ROA | Nonecovered by 169.253.0.0/16 | 673 100% |
| 169.252.24.0/22 | No ROA | Nonecovered by 169.252.0.0/16 | 2 0%low visibility |
| 169.253.162.0/24 | No ROA | Nonecovered by 169.253.0.0/16 | 1 0%low visibility |
| 169.253.172.0/22 | No ROA | Nonecovered by 169.253.0.0/16 | 1 0%low visibility |
| 169.252.0.0/16 | No ROA | Other IRR onlyRADB | 673 100% |
| 169.253.0.0/16 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS6966 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 36 are in fix.csv.
- ROA: none17
- Route object: none15
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 169.252.0.0/17 | No ROA covers it. Add a ROA for AS6966, maxLength 17. |
| Route object: none | 169.252.0.0/17 | No route object for it. A route object for 169.252.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.252.80.0/20 | No ROA covers it. Add a ROA for AS6966, maxLength 20. |
| Route object: none | 169.252.80.0/20 | No route object for it. A route object for 169.252.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.252.80.0/24 | No ROA covers it. Add a ROA for AS6966, maxLength 24. |
| Route object: none | 169.252.80.0/24 | No route object for it. A route object for 169.252.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.252.81.0/24 | No ROA covers it. Add a ROA for AS6966, maxLength 24. |
| Route object: none | 169.252.81.0/24 | No route object for it. A route object for 169.252.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.252.128.0/17 | No ROA covers it. Add a ROA for AS6966, maxLength 17. |
| Route object: none | 169.252.128.0/17 | No route object for it. A route object for 169.252.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.0.0/17 | No ROA covers it. Add a ROA for AS6966, maxLength 17. |
| Route object: none | 169.253.0.0/17 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.4.0/24 | No ROA covers it. Add a ROA for AS6966, maxLength 24. |
| Route object: none | 169.253.4.0/24 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.6.0/24 | No ROA covers it. Add a ROA for AS6966, maxLength 24. |
| Route object: none | 169.253.6.0/24 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.40.0/24 | No ROA covers it. Add a ROA for AS6966, maxLength 24. |
| Route object: none | 169.253.40.0/24 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.128.0/17 | No ROA covers it. Add a ROA for AS6966, maxLength 17. |
| Route object: none | 169.253.128.0/17 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.160.0/19 | No ROA covers it. Add a ROA for AS6966, maxLength 19. |
| Route object: none | 169.253.160.0/19 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.188.0/24 | No ROA covers it. Add a ROA for AS6966, maxLength 24. |
| Route object: none | 169.253.188.0/24 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.252.24.0/22 | No ROA covers it. Add a ROA for AS6966, maxLength 22. |
| Route object: none | 169.252.24.0/22 | No route object for it. A route object for 169.252.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.162.0/24 | No ROA covers it. Add a ROA for AS6966, maxLength 24. |
| Route object: none | 169.253.162.0/24 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.253.172.0/22 | No ROA covers it. Add a ROA for AS6966, maxLength 22. |
| Route object: none | 169.253.172.0/22 | No route object for it. A route object for 169.253.0.0/16 with origin AS6966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6966 in the RIR database for the space. |
| ROA: none | 169.252.0.0/16 | No ROA covers it. Add a ROA for AS6966, maxLength 16. |
| Route object: RIR | 169.252.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 169.253.0.0/16 | No ROA covers it. Add a ROA for AS6966, maxLength 16. |
| Route object: RIR | 169.253.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS6966 whose prefix no peer sees AS6966 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 169.253.32.0/24 | RADB | No ROA |
| 169.253.192.0/19 | 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.