Network · data from 2026-11-12
AS683 ARGONNE-AS - Argonne National Laboratory
Registry name: ARGONNE-AS - Argonne National Laboratory, US · not in PeeringDB
26IPv4 routes
69.2% RPKI valid · 84.6% with a route object
10IPv6 routes
100.0% RPKI valid · 10.0% with a route object
2RPKI invalid
0 origin · 2 maxLength
6No ROA
13 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS683, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS683, 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.
| 146.137.93.0/24 | Invalid: maxLength | Nonecovered by 146.137.0.0/16 | 1 0%low visibility |
| 146.139.248.0/24 | Invalid: maxLength | Nonecovered by 146.139.0.0/16 | 1 0%low visibility |
| 192.5.84.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 192.5.86.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 192.5.87.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 192.148.94.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 192.148.95.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 198.252.143.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 192.5.174.0/24 | Valid | Nonecovered by 192.5.172.0/22 | 670 100% |
| 192.5.175.0/24 | Valid | Nonecovered by 192.5.172.0/22 | 670 100% |
| 2602:278:2000::/36 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:4000::/36 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:5000::/36 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:8100::/48 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:9000::/36 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:aaaa::/48 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:e100::/40 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:e200::/48 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2602:278:e220::/48 | Valid | Nonecovered by 2602:278::/32 | 636 100% |
| 2620:0:dc0::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 140.221.68.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 140.221.69.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 140.221.70.0/23 | Valid | RIR databaseARIN, RADB | 670 100% |
| 140.221.96.0/23 | Valid | RIR databaseARIN, RADB | 670 100% |
| 140.221.112.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
| 146.137.252.0/22 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.5.170.0/23 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.5.176.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.5.200.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 130.202.0.0/16 | Valid | RIR databaseARIN, RADB | 669 99% |
| 140.221.0.0/18 | Valid | RIR databaseARIN, RADB | 669 99% |
| 140.221.72.0/21 | Valid | RIR databaseARIN, RADB | 669 99% |
| 140.221.80.0/20 | Valid | RIR databaseARIN, RADB | 669 99% |
| 146.137.0.0/16 | Valid | RIR databaseARIN, RADB | 669 99% |
| 146.139.0.0/16 | Valid | RIR databaseARIN, RADB | 669 99% |
| 164.54.0.0/16 | Valid | RIR databaseARIN, RADB | 669 99% |
AS-SET
AS683 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 35 are in fix.csv.
- ROA: maxLength2
- ROA: none6
- Route object: none13
- Route object: RIR7
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 146.137.93.0/24 | ROA 146.137.0.0/16 AS683 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 146.137.93.0/24. |
| Route object: none | 146.137.93.0/24 | No route object for it. A route object for 146.137.0.0/16 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| ROA: maxLength | 146.139.248.0/24 | ROA 146.139.0.0/16 AS683 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 146.139.248.0/24. |
| Route object: none | 146.139.248.0/24 | No route object for it. A route object for 146.139.0.0/16 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| ROA: none | 192.5.84.0/24 | No ROA covers it. Add a ROA for AS683, maxLength 24. |
| Route object: RIR | 192.5.84.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.5.86.0/24 | No ROA covers it. Add a ROA for AS683, maxLength 24. |
| Route object: RIR | 192.5.86.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.5.87.0/24 | No ROA covers it. Add a ROA for AS683, maxLength 24. |
| Route object: RIR | 192.5.87.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.148.94.0/24 | No ROA covers it. Add a ROA for AS683, maxLength 24. |
| Route object: RIR | 192.148.94.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.148.95.0/24 | No ROA covers it. Add a ROA for AS683, maxLength 24. |
| Route object: RIR | 192.148.95.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.252.143.0/24 | No ROA covers it. Add a ROA for AS683, maxLength 24. |
| Route object: RIR | 198.252.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 192.5.174.0/24 | No route object for it. A route object for 192.5.172.0/22 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 192.5.175.0/24 | No route object for it. A route object for 192.5.172.0/22 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:2000::/36 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:4000::/36 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:5000::/36 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:8100::/48 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:9000::/36 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:aaaa::/48 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:e100::/40 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:e200::/48 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: none | 2602:278:e220::/48 | No route object for it. A route object for 2602:278::/32 with origin AS683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS683 in the RIR database for the space. |
| Route object: RIR | 2620:0:dc0::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS683 whose prefix no peer sees AS683 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 140.221.64.0/22 | RADB | No ROA |
| 140.221.100.0/22 | RADB | No ROA |
| 192.5.172.0/22 | ARIN, RADB | Valid |
| 192.5.192.0/21 | ARIN, RADB | Valid |
| 192.5.201.0/24 | ARIN | Valid |
| 192.131.121.0/24 | RADB | No ROA |
| 2602:278::/32 | RADB | 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.