Network · data from 2026-11-12
AS16527 Guadalupe Valley Telephone Cooperative
Registry name: GVTCINTERNET - Guadalupe Valley Telephone Cooperative, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16527, 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.
| 96.8.128.0/23 | Valid | Nonecovered by 96.8.128.0/17 | 673 100% |
| 96.8.192.0/19 | Valid | Nonecovered by 96.8.128.0/17 | 673 100% |
| 96.8.193.0/24 | Valid | Nonecovered by 96.8.128.0/17 | 673 100% |
| 96.8.224.0/19 | Valid | Nonecovered by 96.8.128.0/17 | 673 100% |
| 96.8.128.0/19 | Valid | Nonecovered by 96.8.128.0/17 | 671 100% |
| 96.8.160.0/19 | Valid | Nonecovered by 96.8.128.0/17 | 670 100% |
| 69.166.64.0/19 | Valid | RIR databaseARIN, RADB | 670 100% |
| 96.8.128.0/17 | Valid | RIR databaseARIN, RADB | 670 100% |
| 162.211.68.0/22 | Valid | RIR databaseARIN, RADB | 670 100% |
| 162.245.200.0/22 | Valid | RIR databaseARIN, RADB | 670 100% |
| 216.177.160.0/19 | Valid | RIR databaseARIN, RADB | 670 100% |
| 2604:2900::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
AS16527'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 7 are in fix.csv.
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 96.8.128.0/23 | No route object for it. A route object for 96.8.128.0/17 with origin AS16527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16527 in the RIR database for the space. |
| Route object: none | 96.8.192.0/19 | No route object for it. A route object for 96.8.128.0/17 with origin AS16527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16527 in the RIR database for the space. |
| Route object: none | 96.8.193.0/24 | No route object for it. A route object for 96.8.128.0/17 with origin AS16527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16527 in the RIR database for the space. |
| Route object: none | 96.8.224.0/19 | No route object for it. A route object for 96.8.128.0/17 with origin AS16527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16527 in the RIR database for the space. |
| Route object: none | 96.8.128.0/19 | No route object for it. A route object for 96.8.128.0/17 with origin AS16527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16527 in the RIR database for the space. |
| Route object: none | 96.8.160.0/19 | No route object for it. A route object for 96.8.128.0/17 with origin AS16527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16527 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16527 whose prefix no peer sees AS16527 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.128.128.0/20 | RADB | 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.