Network · data from 2026-11-12
AS21668 ENET - ElbertonNet
Registry name: ENET - ElbertonNet, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21668, 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.
| 173.245.224.0/24 | No ROA | Other origin only | 671 100% |
| 198.251.42.0/23 | No ROA | Nonecovered by 198.251.40.0/21 | 671 100% |
| 198.251.44.0/24 | No ROA | Nonecovered by 198.251.40.0/21 | 671 100% |
| 198.251.46.0/23 | No ROA | Nonecovered by 198.251.40.0/21 | 671 100% |
| 198.251.46.0/24 | No ROA | Nonecovered by 198.251.40.0/21 | 671 100% |
| 198.251.47.0/24 | No ROA | Nonecovered by 198.251.40.0/21 | 670 100% |
| 198.251.40.0/21 | No ROA | Other IRR onlyBBOI | 671 100% |
| 208.101.192.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS21668 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 17 are in fix.csv.
- ROA: none7
- Route object: none6
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 173.245.224.0/24 | No ROA covers it. Add a ROA for AS21668, maxLength 24. |
| Route object: none | 173.245.224.0/24 | Route objects for it name AS31877. Add a route object with origin AS21668 in the RIR database for the space. |
| ROA: none | 198.251.42.0/23 | No ROA covers it. Add a ROA for AS21668, maxLength 23. |
| Route object: none | 198.251.42.0/23 | No route object for it. A route object for 198.251.40.0/21 with origin AS21668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21668 in the RIR database for the space. |
| ROA: none | 198.251.44.0/24 | No ROA covers it. Add a ROA for AS21668, maxLength 24. |
| Route object: none | 198.251.44.0/24 | No route object for it. A route object for 198.251.40.0/21 with origin AS21668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21668 in the RIR database for the space. |
| ROA: none | 198.251.46.0/23 | No ROA covers it. Add a ROA for AS21668, maxLength 23. |
| Route object: none | 198.251.46.0/23 | No route object for it. A route object for 198.251.40.0/21 with origin AS21668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21668 in the RIR database for the space. |
| ROA: none | 198.251.46.0/24 | No ROA covers it. Add a ROA for AS21668, maxLength 24. |
| Route object: none | 198.251.46.0/24 | No route object for it. A route object for 198.251.40.0/21 with origin AS21668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21668 in the RIR database for the space. |
| ROA: none | 198.251.47.0/24 | No ROA covers it. Add a ROA for AS21668, maxLength 24. |
| Route object: none | 198.251.47.0/24 | No route object for it. A route object for 198.251.40.0/21 with origin AS21668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21668 in the RIR database for the space. |
| ROA: none | 198.251.40.0/21 | No ROA covers it. Add a ROA for AS21668, maxLength 21. |
| Route object: RIR | 198.251.40.0/21 | Route object only in BBOI. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21668 whose prefix no peer sees AS21668 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.251.45.0/24 | RADB | No ROA |
| 208.101.198.0/24 | BBOI, RADB | No ROA |
| 2604:7280::/32 | BBOI | 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.