Network · data from 2026-11-12
AS395800 JCPN-AS - JEFFERSON COUNTY PUD NO. 1
Registry name: JCPN-AS - JEFFERSON COUNTY PUD NO. 1, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS395800, 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.
| 128.254.210.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 66.133.58.0/23 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS395800 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 7 are in fix.csv.
- ROA: none1
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 128.254.210.0/24 | No ROA covers it. Add a ROA for AS395800, maxLength 24. |
| Route object: RIR | 128.254.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 66.133.58.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS395800 whose prefix no peer sees AS395800 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.87.213.0/24 | RIPE | Invalid: origin |
| 212.87.214.0/24 | RIPE | Invalid: origin |
| 212.87.215.0/24 | RIPE | Invalid: origin |
| 2602:facf::/40 | 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.