Network · data from 2026-11-12
AS35542 SSC-AS SSC Space AB
Registry name: SSC-AS SSC Space AB, SE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35542, 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.
| 5.250.224.0/21 | No ROA | None | 672 100% |
| 185.128.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.92.128.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 185.128.0.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.222.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.128.2.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS35542 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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.250.224.0/21 | No ROA covers it. Add a ROA for AS35542, maxLength 21. |
| Route object: none | 5.250.224.0/21 | No route object for it. Add a route object with origin AS35542 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35542 whose prefix no peer sees AS35542 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.43.14.0/24 | RIPE | No ROA |
| 92.43.15.0/24 | RIPE | No ROA |
| 185.128.0.0/22 | 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.