Network · data from 2026-11-12
AS397268 WILDWISP-01 - Cambridge Telephone
Registry name: WILDWISP-01 - Cambridge Telephone, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS397268, 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.
| 208.98.170.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 185.207.179.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 199.58.120.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.58.121.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.58.123.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.58.124.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.58.126.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.58.127.0/24 | Valid | RIR databaseARIN | 671 100% |
| 45.33.218.0/24 | Valid | RIR databaseARIN | 670 100% |
| 45.33.219.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.172.192.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 199.58.122.0/24 | Valid | RIR databaseARIN | 669 99% |
| 199.58.125.0/24 | Valid | RIR databaseARIN | 669 99% |
AS-SET
AS397268 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 17 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 208.98.170.0/24 | No ROA covers it. Add a ROA for AS397268, maxLength 24. |
| Route object: RIR | 185.207.179.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS397268 whose prefix no peer sees AS397268 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.33.208.0/20 | ARIN | No ROA |
| 45.33.208.0/22 | ARIN | Valid |
| 45.33.212.0/22 | ARIN | Valid |
| 45.33.216.0/24 | ARIN | Valid |
| 45.33.217.0/24 | ARIN | Valid |
| 45.33.220.0/24 | ARIN | Valid |
| 45.33.221.0/24 | ARIN | Valid |
| 45.33.222.0/24 | ARIN | Valid |
| 45.33.223.0/24 | ARIN | Valid |
| 66.232.72.0/21 | ARIN | No ROA |
| 66.232.80.0/22 | ARIN | No ROA |
| 199.58.120.0/21 | ARIN, RADB | No ROA |
| 208.98.176.0/22 | ARIN | No ROA |
| 209.19.132.0/23 | ARIN | Invalid: origin |
| 2604:9c40::/32 | ARIN, 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.