Network · data from 2026-11-12
AS377 SNLA-NET-AS - Sandia National Laboratories
Registry name: SNLA-NET-AS - Sandia National Laboratories, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS377, 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.
| 198.178.168.0/24 | No ROA | None | 660 98% |
| 198.178.169.0/24 | No ROA | None | 660 98% |
| 198.178.170.0/24 | No ROA | None | 660 98% |
| 132.175.0.0/16 | No ROA | Other IRR onlyRADB | 669 99% |
| 134.253.0.0/16 | No ROA | Other IRR onlyRADB | 669 99% |
| 192.160.227.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 198.102.151.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 198.102.152.0/22 | No ROA | Other IRR onlyRADB | 669 99% |
| 198.206.223.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 205.137.80.0/20 | No ROA | Other IRR onlyRADB | 669 99% |
| 2620:106:6008::/48 | Valid | Nonecovered by 2620:106:6000::/36 | 636 100% |
AS-SET
AS377 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 24 are in fix.csv.
- ROA: none10
- Route object: none4
- Route object: RIR7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 198.178.168.0/24 | No ROA covers it. Add a ROA for AS377, maxLength 24. |
| Route object: none | 198.178.168.0/24 | No route object for it. Add a route object with origin AS377 in the RIR database for the space. |
| ROA: none | 198.178.169.0/24 | No ROA covers it. Add a ROA for AS377, maxLength 24. |
| Route object: none | 198.178.169.0/24 | No route object for it. Add a route object with origin AS377 in the RIR database for the space. |
| ROA: none | 198.178.170.0/24 | No ROA covers it. Add a ROA for AS377, maxLength 24. |
| Route object: none | 198.178.170.0/24 | No route object for it. Add a route object with origin AS377 in the RIR database for the space. |
| ROA: none | 132.175.0.0/16 | No ROA covers it. Add a ROA for AS377, maxLength 16. |
| Route object: RIR | 132.175.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 134.253.0.0/16 | No ROA covers it. Add a ROA for AS377, maxLength 16. |
| Route object: RIR | 134.253.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.160.227.0/24 | No ROA covers it. Add a ROA for AS377, maxLength 24. |
| Route object: RIR | 192.160.227.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.102.151.0/24 | No ROA covers it. Add a ROA for AS377, maxLength 24. |
| Route object: RIR | 198.102.151.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.102.152.0/22 | No ROA covers it. Add a ROA for AS377, maxLength 22. |
| Route object: RIR | 198.102.152.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.206.223.0/24 | No ROA covers it. Add a ROA for AS377, maxLength 24. |
| Route object: RIR | 198.206.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 205.137.80.0/20 | No ROA covers it. Add a ROA for AS377, maxLength 20. |
| Route object: RIR | 205.137.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2620:106:6008::/48 | No route object for it. A route object for 2620:106:6000::/36 with origin AS377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS377 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS377 whose prefix no peer sees AS377 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.206.220.0/22 | RADB | No ROA |
| 198.206.222.0/23 | RADB | No ROA |
| 2620:106:6000::/36 | ARIN | Valid |
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.