Network · data from 2026-11-12
AS18546 ACN-NADC - Accenture LLP
Registry name: ACN-NADC - Accenture LLP, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18546, 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.
| 170.248.76.0/24 | No ROA | None | 673 100% |
| 170.248.172.0/24 | No ROA | None | 673 100% |
| 170.248.173.0/24 | No ROA | None | 673 100% |
| 170.251.22.0/24 | No ROA | Other origin only | 673 100% |
AS-SET
AS18546 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 21 are in fix.csv.
- ROA: none4
- Route object: none4
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.248.76.0/24 | No ROA covers it. Add a ROA for AS18546, maxLength 24. |
| Route object: none | 170.248.76.0/24 | No route object for it. Add a route object with origin AS18546 in the RIR database for the space. |
| ROA: none | 170.248.172.0/24 | No ROA covers it. Add a ROA for AS18546, maxLength 24. |
| Route object: none | 170.248.172.0/24 | No route object for it. Add a route object with origin AS18546 in the RIR database for the space. |
| ROA: none | 170.248.173.0/24 | No ROA covers it. Add a ROA for AS18546, maxLength 24. |
| Route object: none | 170.248.173.0/24 | No route object for it. Add a route object with origin AS18546 in the RIR database for the space. |
| ROA: none | 170.251.22.0/24 | No ROA covers it. Add a ROA for AS18546, maxLength 24. |
| Route object: none | 170.251.22.0/24 | Route objects for it name AS9497. Add a route object with origin AS18546 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18546 whose prefix no peer sees AS18546 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.70.110.192/26 | RADB | No ROA |
| 65.201.212.0/24 | ALTDB | No ROA |
| 144.36.3.0/24 | ALTDB | No ROA |
| 144.36.16.0/24 | ALTDB | No ROA |
| 170.248.39.0/24 | ALTDB, RADB | No ROA |
| 170.248.93.0/24 | ALTDB, RADB | No ROA |
| 170.248.94.0/24 | ALTDB | No ROA |
| 170.248.95.0/24 | ALTDB | No ROA |
| 170.248.250.0/23 | ALTDB, RADB | No ROA |
| 170.251.24.0/21 | ALTDB, RADB | No ROA |
| 204.63.152.0/22 | ALTDB | No ROA |
| 204.63.156.0/22 | NTTCOM | No ROA |
| 204.63.158.0/24 | ALTDB | 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.