Network · data from 2026-11-12
AS400385 CITIZENS-TELEPHONE-ASN-01 - Citizens Telephone Corporation
Registry name: CITIZENS-TELEPHONE-ASN-01 - Citizens Telephone Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400385, 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.
| 23.130.200.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 64.184.4.0/24 | Valid | Nonecovered by 64.184.4.0/22 | 672 100% |
| 69.160.217.0/24 | Valid | Nonecovered by 69.160.216.0/23 | 672 100% |
| 64.184.5.0/24 | Valid | Nonecovered by 64.184.4.0/22 | 670 100% |
| 64.184.6.0/24 | Valid | Nonecovered by 64.184.4.0/22 | 670 100% |
| 69.160.216.0/24 | Valid | Nonecovered by 69.160.216.0/23 | 670 100% |
| 64.184.95.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.184.111.0/24 | Valid | RIR databaseARIN | 673 100% |
| 208.103.10.0/24 | Valid | RIR databaseARIN | 673 100% |
| 208.103.44.0/24 | Valid | RIR databaseARIN | 673 100% |
| 208.103.50.0/24 | Valid | RIR databaseARIN | 673 100% |
| 208.103.56.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.184.7.0/24 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS400385 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 9 are in fix.csv.
- ROA: none1
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 23.130.200.0/24 | No ROA covers it. Add a ROA for AS400385, maxLength 24. |
| Route object: none | 64.184.4.0/24 | No route object for it. A route object for 64.184.4.0/22 with origin AS400385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400385 in the RIR database for the space. |
| Route object: none | 69.160.217.0/24 | No route object for it. A route object for 69.160.216.0/23 with origin AS400385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400385 in the RIR database for the space. |
| Route object: none | 64.184.5.0/24 | No route object for it. A route object for 64.184.4.0/22 with origin AS400385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400385 in the RIR database for the space. |
| Route object: none | 64.184.6.0/24 | No route object for it. A route object for 64.184.4.0/22 with origin AS400385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400385 in the RIR database for the space. |
| Route object: none | 69.160.216.0/24 | No route object for it. A route object for 69.160.216.0/23 with origin AS400385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400385 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400385 whose prefix no peer sees AS400385 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.184.4.0/22 | ARIN | Valid |
| 69.160.216.0/23 | ARIN | Valid |
| 2606:a640::/32 | ARIN | 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.