Network · data from 2026-11-12
AS14538 HEC-NETWORK - Harrisonburg Electric Commission
Registry name: HEC-NETWORK - Harrisonburg Electric Commission, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14538, 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.
| 50.205.160.0/24 | Valid | Other IRR onlyNTTCOM | 670 100% |
AS-SET
AS14538 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.
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 50.205.160.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14538 whose prefix no peer sees AS14538 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.237.81.0/24 | NTTCOM | No ROA |
| 65.199.119.0/24 | NTTCOM | No ROA |
| 207.97.188.0/24 | RADB | No ROA |
| 208.9.161.0/24 | RADB | No ROA |
| 209.49.205.0/24 | RADB | No ROA |
| 209.118.222.0/23 | RADB | No ROA |
| 209.137.50.0/23 | 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.