Network · data from 2026-11-12
AS54363 BHI - Baker Hughes Holdings LLC
Registry name: BHI - Baker Hughes Holdings LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54363, 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.
| 199.193.16.0/23 | No ROA | None | 673 100% |
| 199.79.17.0/24 | Valid | None | 673 100% |
| 199.193.16.0/24 | Valid | None | 673 100% |
| 199.193.17.0/24 | Valid | None | 673 100% |
| 199.193.18.0/24 | Valid | None | 673 100% |
| 199.193.19.0/24 | Valid | None | 673 100% |
| 199.193.22.0/24 | Valid | None | 673 100% |
| 199.193.23.0/24 | Valid | None | 673 100% |
| 199.193.24.0/24 | Valid | None | 673 100% |
| 199.193.25.0/24 | Valid | None | 673 100% |
| 199.79.16.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 199.193.20.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 199.193.21.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 199.193.26.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.193.27.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.193.28.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.193.29.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS54363 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 15 are in fix.csv.
- ROA: none1
- Route object: none10
- Route object: RIR3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.193.16.0/23 | No ROA covers it. Add a ROA for AS54363, maxLength 23. |
| Route object: none | 199.193.16.0/23 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.79.17.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.16.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.17.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.18.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.19.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.22.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.23.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.24.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: none | 199.193.25.0/24 | No route object for it. Add a route object with origin AS54363 in the RIR database for the space. |
| Route object: RIR | 199.79.16.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.193.20.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.193.21.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54363 whose prefix no peer sees AS54363 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 207.193.159.0/24 | NTTCOM | 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.