Network · data from 2026-11-12
AS196670 ADP (Automatic Data Processing)
Registry name: ADP-EUROPE ADP GSI FRANCE SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS196670, 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.
| 150.175.44.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 150.175.45.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 195.200.254.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 195.200.255.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 91.213.26.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 194.36.92.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 195.200.254.0/23 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS196670's PeeringDB record names no 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.
- Route object: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 150.175.44.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 150.175.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 195.200.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 195.200.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS196670 whose prefix no peer sees AS196670 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:67c:239c::/48 | RIPE | No ROA |
| 2a04:9140:3001::/48 | RIPE | Valid |
| 2a04:9140:3041::/48 | RIPE | 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.