Network · data from 2026-11-12
AS25717 SCAAM0001 - Essity Hygiene and Health
Registry name: SCAAM0001 - Essity Hygiene and Health, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25717, 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.
| 193.221.54.0/23 | Valid | None | 673 100% |
| 171.25.128.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 171.25.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 171.25.138.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 171.25.139.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.16.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.17.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.18.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.22.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.23.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.47.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.56.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.57.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.72.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.221.74.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.75.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.221.76.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.221.77.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.221.78.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.221.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 171.25.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 171.25.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 171.25.142.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 171.25.140.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.221.66.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.221.68.0/24 | Valid | RIR databaseNTTCOM, RIPE | 671 100% |
| 193.221.69.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.221.70.0/23 | Valid | RIR databaseNTTCOM, RIPE | 671 100% |
| 171.25.143.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS25717 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: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 193.221.54.0/23 | No route object for it. Add a route object with origin AS25717 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25717 whose prefix no peer sees AS25717 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.222.52.0/24 | RADB | No ROA |
| 171.25.134.0/24 | RIPE | Valid |
| 171.25.135.0/24 | RIPE | Valid |
| 193.221.54.0/24 | RIPE | Invalid: maxLength |
| 193.221.55.0/24 | RIPE | Invalid: maxLength |
| 193.221.58.0/24 | RIPE | No ROA |
| 193.221.60.0/24 | RIPE | Valid |
| 193.221.73.0/24 | RIPE | No ROA |
| 193.221.76.0/23 | RADB | 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.