Network · data from 2026-11-12
AS15269 PAI-AS - ConocoPhillips Company
Registry name: PAI-AS - ConocoPhillips Company, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15269, 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.
| 138.32.8.0/24 | Valid | Nonecovered by 138.32.8.0/22 | 671 100% |
| 138.32.9.0/24 | Valid | Nonecovered by 138.32.8.0/22 | 671 100% |
| 138.32.10.0/24 | Valid | Nonecovered by 138.32.8.0/22 | 671 100% |
| 138.32.11.0/24 | Valid | Nonecovered by 138.32.8.0/22 | 671 100% |
| 138.32.13.0/24 | Valid | Nonecovered by 138.32.12.0/22 | 671 100% |
| 138.32.14.0/23 | Valid | Nonecovered by 138.32.12.0/22 | 671 100% |
| 138.32.12.0/24 | Valid | Nonecovered by 138.32.12.0/22 | 670 100% |
| 138.32.8.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 138.32.12.0/22 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS15269 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 10 are in fix.csv.
- Route object: none7
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 138.32.8.0/24 | No route object for it. A route object for 138.32.8.0/22 with origin AS15269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15269 in the RIR database for the space. |
| Route object: none | 138.32.9.0/24 | No route object for it. A route object for 138.32.8.0/22 with origin AS15269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15269 in the RIR database for the space. |
| Route object: none | 138.32.10.0/24 | No route object for it. A route object for 138.32.8.0/22 with origin AS15269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15269 in the RIR database for the space. |
| Route object: none | 138.32.11.0/24 | No route object for it. A route object for 138.32.8.0/22 with origin AS15269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15269 in the RIR database for the space. |
| Route object: none | 138.32.13.0/24 | No route object for it. A route object for 138.32.12.0/22 with origin AS15269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15269 in the RIR database for the space. |
| Route object: none | 138.32.14.0/23 | No route object for it. A route object for 138.32.12.0/22 with origin AS15269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15269 in the RIR database for the space. |
| Route object: none | 138.32.12.0/24 | No route object for it. A route object for 138.32.12.0/22 with origin AS15269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15269 in the RIR database for the space. |
| Route object: RIR | 138.32.8.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.32.12.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15269 whose prefix no peer sees AS15269 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.32.8.0/21 | 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.