Network · data from 2026-11-12
AS400238 PIEG-01 - PIE&G
Registry name: PIEG-01 - PIE&G, US · not in PeeringDB
43IPv4 routes
100.0% RPKI valid · 51.2% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
21 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS400238, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS400238, 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.
| 109.73.224.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.225.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.226.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.227.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.228.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.229.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.230.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.231.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 109.73.232.0/24 | Valid | Nonecovered by 109.73.224.0/20 | 671 100% |
| 204.8.76.0/24 | Valid | Nonecovered by 204.8.76.0/22 | 671 100% |
| 204.8.77.0/24 | Valid | Nonecovered by 204.8.76.0/22 | 671 100% |
| 204.8.78.0/24 | Valid | Nonecovered by 204.8.76.0/22 | 671 100% |
| 204.8.79.0/24 | Valid | Nonecovered by 204.8.76.0/22 | 671 100% |
| 204.8.116.0/24 | Valid | Nonecovered by 204.8.116.0/22 | 671 100% |
| 204.8.117.0/24 | Valid | Nonecovered by 204.8.116.0/22 | 671 100% |
| 204.8.118.0/24 | Valid | Nonecovered by 204.8.116.0/22 | 671 100% |
| 204.8.119.0/24 | Valid | Nonecovered by 204.8.116.0/22 | 671 100% |
| 209.127.100.0/24 | Valid | Nonecovered by 209.127.100.0/22 | 671 100% |
| 209.127.101.0/24 | Valid | Nonecovered by 209.127.100.0/22 | 671 100% |
| 209.127.102.0/24 | Valid | Nonecovered by 209.127.100.0/22 | 671 100% |
| 209.127.103.0/24 | Valid | Nonecovered by 209.127.100.0/22 | 671 100% |
| 2602:fc02::/36 | Valid | Other IRR onlyRADB | 635 100% |
| 109.73.224.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 147.185.189.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 147.185.208.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 147.185.210.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 147.185.216.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 147.185.219.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 147.185.225.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 204.8.76.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 204.8.116.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 206.225.29.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.244.221.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.244.222.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 209.127.100.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 209.145.41.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.87.35.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.87.36.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.87.51.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.87.52.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.87.57.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.87.59.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.87.61.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.114.68.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS400238 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 22 are in fix.csv.
- Route object: none21
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 109.73.224.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.225.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.226.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.227.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.228.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.229.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.230.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.231.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 109.73.232.0/24 | No route object for it. A route object for 109.73.224.0/20 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.76.0/24 | No route object for it. A route object for 204.8.76.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.77.0/24 | No route object for it. A route object for 204.8.76.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.78.0/24 | No route object for it. A route object for 204.8.76.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.79.0/24 | No route object for it. A route object for 204.8.76.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.116.0/24 | No route object for it. A route object for 204.8.116.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.117.0/24 | No route object for it. A route object for 204.8.116.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.118.0/24 | No route object for it. A route object for 204.8.116.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 204.8.119.0/24 | No route object for it. A route object for 204.8.116.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 209.127.100.0/24 | No route object for it. A route object for 209.127.100.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 209.127.101.0/24 | No route object for it. A route object for 209.127.100.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 209.127.102.0/24 | No route object for it. A route object for 209.127.100.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: none | 209.127.103.0/24 | No route object for it. A route object for 209.127.100.0/22 with origin AS400238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400238 in the RIR database for the space. |
| Route object: RIR | 2602:fc02::/36 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS400238 is announced.
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.