Network · data from 2026-11-12
AS399220 UPSTATE-FIBER-NETWORK
Registry name: UPSTATE-FIBER-NETWORK - Finger Lakes Communications Group, Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399220, 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.
| 192.230.151.0/24 | Valid | Nonecovered by 192.230.144.0/21 | 673 100% |
| 199.167.197.0/24 | Valid | Nonecovered by 199.167.192.0/21 | 671 100% |
| 2605:d340:7000::/44 | Valid | Nonecovered by 2605:d340:7000::/36 | 634 100% |
| 192.230.144.0/21 | Valid | RIR databaseARIN | 673 100% |
| 207.66.73.0/24 | Valid | RIR databaseARIN | 673 100% |
| 207.66.75.0/24 | Valid | RIR databaseARIN | 673 100% |
| 207.66.76.0/24 | Valid | RIR databaseARIN | 673 100% |
| 207.66.77.0/24 | Valid | RIR databaseARIN | 673 100% |
| 207.66.78.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 207.66.79.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 64.246.224.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 192.190.160.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 199.167.192.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.66.64.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.66.64.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.66.64.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.66.68.0/24 | Valid | RIR databaseARIN | 671 100% |
| 207.66.69.0/24 | Valid | RIR databaseARIN | 671 100% |
| 207.66.71.0/24 | Valid | RIR databaseARIN | 671 100% |
| 192.230.152.0/21 | Valid | RIR databaseARIN, RADB | 670 100% |
| 2605:d340:3000::/36 | Valid | RIR databaseARIN, RADB | 631 99% |
AS-SET
AS399220's PeeringDB record names no 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 26 are in fix.csv.
- Route object: none3
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 192.230.151.0/24 | No route object for it. A route object for 192.230.144.0/21 with origin AS399220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399220 in the RIR database for the space. |
| Route object: none | 199.167.197.0/24 | No route object for it. A route object for 199.167.192.0/21 with origin AS399220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399220 in the RIR database for the space. |
| Route object: none | 2605:d340:7000::/44 | No route object for it. A route object for 2605:d340:7000::/36 with origin AS399220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399220 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399220 whose prefix no peer sees AS399220 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.230.144.0/20 | ARIN | No ROA |
| 207.66.65.0/24 | ARIN | Valid |
| 207.66.66.0/24 | ARIN | Valid |
| 207.66.67.0/24 | ARIN | Valid |
| 207.66.70.0/24 | ARIN | Valid |
| 207.66.72.0/21 | ARIN, RADB | Valid |
| 207.66.72.0/24 | ARIN | Valid |
| 207.66.74.0/24 | ARIN | Valid |
| 2605:d340::/32 | RADB | No ROA |
| 2605:d340:1000::/36 | ARIN | Valid |
| 2605:d340:2000::/36 | ARIN | Valid |
| 2605:d340:4000::/36 | ARIN | Valid |
| 2605:d340:5000::/36 | ARIN | Valid |
| 2605:d340:6000::/36 | ARIN | Valid |
| 2605:d340:7000::/36 | ARIN | Valid |
| 2605:d340:8000::/36 | ARIN | Valid |
| 2605:d340:9000::/36 | ARIN | Valid |
| 2605:d340:a000::/36 | ARIN | Valid |
| 2605:d340:b000::/36 | ARIN | Valid |
| 2605:d340:c000::/36 | ARIN | Valid |
| 2605:d340:d000::/36 | ARIN | Valid |
| 2605:d340:e000::/36 | ARIN | Valid |
| 2605:d340:f000::/36 | ARIN | 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.