Network · data from 2026-11-12
AS62688 ICTC - Inter-Community Telephone Co.
Registry name: ICTC - Inter-Community Telephone Co., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62688, 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.178.198.0/24 | No ROA | Other origin only | 671 100% |
| 69.178.199.0/24 | No ROA | Other origin only | 671 100% |
| 66.163.153.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 66.163.154.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 162.220.168.0/21 | No ROA | RIR databaseARIN | 671 100% |
| 2604:fd80::/32 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
AS62688 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: none6
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.178.198.0/24 | No ROA covers it. Add a ROA for AS62688, maxLength 24. |
| Route object: none | 69.178.198.0/24 | Route objects for it name AS26794. Add a route object with origin AS62688 in the RIR database for the space. |
| ROA: none | 69.178.199.0/24 | No ROA covers it. Add a ROA for AS62688, maxLength 24. |
| Route object: none | 69.178.199.0/24 | Route objects for it name AS26794. Add a route object with origin AS62688 in the RIR database for the space. |
| ROA: none | 66.163.153.0/24 | No ROA covers it. Add a ROA for AS62688, maxLength 24. |
| ROA: none | 66.163.154.0/24 | No ROA covers it. Add a ROA for AS62688, maxLength 24. |
| ROA: none | 162.220.168.0/21 | No ROA covers it. Add a ROA for AS62688, maxLength 21. |
| ROA: none | 2604:fd80::/32 | No ROA covers it. Add a ROA for AS62688, maxLength 32. |
Route objects not announced
Every route object with origin AS62688 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.