Network · data from 2026-11-12
AS397710 HARMONYTELCO - MiBroadband
Registry name: HARMONYTELCO - MiBroadband, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS397710, 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.
| 69.173.160.0/22 | No ROA | RIR databaseARIN | 671 100% |
| 69.173.164.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 162.33.196.0/22 | No ROA | RIR databaseARIN | 671 100% |
| 205.178.138.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 205.237.96.0/21 | No ROA | RIR databaseARIN | 671 100% |
AS-SET
AS397710 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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.173.160.0/22 | No ROA covers it. Add a ROA for AS397710, maxLength 22. |
| ROA: none | 69.173.164.0/23 | No ROA covers it. Add a ROA for AS397710, maxLength 23. |
| ROA: none | 162.33.196.0/22 | No ROA covers it. Add a ROA for AS397710, maxLength 22. |
| ROA: none | 205.178.138.0/23 | No ROA covers it. Add a ROA for AS397710, maxLength 23. |
| ROA: none | 205.237.96.0/21 | No ROA covers it. Add a ROA for AS397710, maxLength 21. |
Route objects not announced
Every route object with origin AS397710 is announced.
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.