Network · data from 2026-11-12
AS1640 Thacker-Grigsby Communications
Registry name: TGTEL - Thacker-Grigsby Communications, US · PeeringDB
18IPv4 routes
100.0% RPKI valid · 38.9% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
11 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS1640, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS1640, 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.
| 68.64.120.0/22 | Valid | Nonecovered by 68.64.112.0/20 | 671 100% |
| 68.64.124.0/24 | Valid | Nonecovered by 68.64.112.0/20 | 671 100% |
| 69.57.96.0/21 | Valid | Nonecovered by 69.57.96.0/20 | 671 100% |
| 69.57.104.0/21 | Valid | Nonecovered by 69.57.96.0/20 | 671 100% |
| 76.72.194.0/24 | Valid | Nonecovered by 76.72.192.0/20 | 671 100% |
| 76.72.195.0/24 | Valid | Nonecovered by 76.72.192.0/20 | 671 100% |
| 76.72.196.0/24 | Valid | Nonecovered by 76.72.192.0/20 | 671 100% |
| 76.72.197.0/24 | Valid | Nonecovered by 76.72.192.0/20 | 671 100% |
| 76.72.198.0/23 | Valid | Nonecovered by 76.72.192.0/20 | 671 100% |
| 76.72.200.0/22 | Valid | Nonecovered by 76.72.192.0/20 | 671 100% |
| 76.72.204.0/22 | Valid | Nonecovered by 76.72.192.0/20 | 671 100% |
| 68.64.112.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 69.57.96.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 76.72.192.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 199.59.84.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 199.116.152.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 199.192.120.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 208.56.128.0/19 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS1640'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 14 are in fix.csv.
- Route object: none11
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 68.64.120.0/22 | No route object for it. A route object for 68.64.112.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 68.64.124.0/24 | No route object for it. A route object for 68.64.112.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 69.57.96.0/21 | No route object for it. A route object for 69.57.96.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 69.57.104.0/21 | No route object for it. A route object for 69.57.96.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 76.72.194.0/24 | No route object for it. A route object for 76.72.192.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 76.72.195.0/24 | No route object for it. A route object for 76.72.192.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 76.72.196.0/24 | No route object for it. A route object for 76.72.192.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 76.72.197.0/24 | No route object for it. A route object for 76.72.192.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 76.72.198.0/23 | No route object for it. A route object for 76.72.192.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 76.72.200.0/22 | No route object for it. A route object for 76.72.192.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
| Route object: none | 76.72.204.0/22 | No route object for it. A route object for 76.72.192.0/20 with origin AS1640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1640 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS1640 whose prefix no peer sees AS1640 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.36.204.0/22 | ARIN, RADB | Valid |
| 104.245.140.0/22 | ARIN, RADB | Valid |
| 162.221.140.0/22 | 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.