Network · data from 2026-11-12
AS11308 APTIV-NET - APTIV SERVICES US, LLC
Registry name: APTIV-NET - APTIV SERVICES US, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11308, 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.
| 144.250.33.0/24 | No ROA | Other IRR onlyNTTCOM | 49 7%low visibility |
| 144.250.40.0/24 | No ROA | Other IRR onlyNTTCOM | 32 5%low visibility |
| 144.250.128.0/24 | Valid | RIR databaseARIN, NTTCOM | 49 7%low visibility |
AS-SET
AS11308 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 7 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 144.250.33.0/24 | No ROA covers it. Add a ROA for AS11308, maxLength 24. |
| Route object: RIR | 144.250.33.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 144.250.40.0/24 | No ROA covers it. Add a ROA for AS11308, maxLength 24. |
| Route object: RIR | 144.250.40.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11308 whose prefix no peer sees AS11308 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.205.157.64/27 | NTTCOM | No ROA |
| 69.42.101.192/28 | NTTCOM | No ROA |
| 202.94.114.192/26 | 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.