Network · data from 2026-11-12
AS10668 LEE-ASN - Lee Enterprises, Incorporated
Registry name: LEE-ASN - Lee Enterprises, Incorporated, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10668, 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.
| 209.96.3.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 192.104.182.0/24 | No ROA | RIR databaseALTDB, ARIN | 672 100% |
| 192.104.183.0/24 | No ROA | RIR databaseALTDB, ARIN | 672 100% |
| 192.104.185.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 192.104.192.0/19 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.104.224.0/21 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS10668 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 8 are in fix.csv.
- ROA: none4
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.96.3.0/24 | No ROA covers it. Add a ROA for AS10668, maxLength 24. |
| Route object: RIR | 209.96.3.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.104.182.0/24 | No ROA covers it. Add a ROA for AS10668, maxLength 24. |
| ROA: none | 192.104.183.0/24 | No ROA covers it. Add a ROA for AS10668, maxLength 24. |
| ROA: none | 192.104.185.0/24 | No ROA covers it. Add a ROA for AS10668, maxLength 24. |
Route objects not announced
Route objects with origin AS10668 whose prefix no peer sees AS10668 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.104.184.0/24 | ARIN | No ROA |
| 198.175.232.0/24 | RADB | No ROA |
| 198.175.233.0/24 | 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.