Network · data from 2026-11-12
AS18938 PRESSGANEY - PRESS GANEY ASSOCIATES INC
Registry name: PRESSGANEY - PRESS GANEY ASSOCIATES INC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18938, 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.
| 204.13.92.0/24 | Valid | Nonecovered by 204.13.92.0/22 | 673 100% |
| 204.13.94.0/24 | Valid | Nonecovered by 204.13.92.0/22 | 673 100% |
| 204.13.95.0/24 | Valid | Nonecovered by 204.13.92.0/22 | 673 100% |
| 74.119.200.0/23 | Valid | Nonecovered by 74.119.200.0/22 | 672 100% |
| 74.119.200.0/24 | Valid | Nonecovered by 74.119.200.0/22 | 672 100% |
| 74.119.201.0/24 | Valid | Nonecovered by 74.119.200.0/22 | 672 100% |
| 74.119.202.0/24 | Valid | Nonecovered by 74.119.200.0/22 | 672 100% |
| 204.13.92.0/22 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS18938 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 8 are in fix.csv.
- Route object: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 204.13.92.0/24 | No route object for it. A route object for 204.13.92.0/22 with origin AS18938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18938 in the RIR database for the space. |
| Route object: none | 204.13.94.0/24 | No route object for it. A route object for 204.13.92.0/22 with origin AS18938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18938 in the RIR database for the space. |
| Route object: none | 204.13.95.0/24 | No route object for it. A route object for 204.13.92.0/22 with origin AS18938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18938 in the RIR database for the space. |
| Route object: none | 74.119.200.0/23 | No route object for it. A route object for 74.119.200.0/22 with origin AS18938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18938 in the RIR database for the space. |
| Route object: none | 74.119.200.0/24 | No route object for it. A route object for 74.119.200.0/22 with origin AS18938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18938 in the RIR database for the space. |
| Route object: none | 74.119.201.0/24 | No route object for it. A route object for 74.119.200.0/22 with origin AS18938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18938 in the RIR database for the space. |
| Route object: none | 74.119.202.0/24 | No route object for it. A route object for 74.119.200.0/22 with origin AS18938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18938 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18938 whose prefix no peer sees AS18938 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.119.200.0/22 | 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.