Network · data from 2026-11-12
AS201750 contrasec Contrasec Oy
Registry name: contrasec Contrasec Oy, FI · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201750, 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.
| 185.252.116.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.252.119.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.252.117.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.252.118.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a0c:2640::/32 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS201750 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 14 are in fix.csv.
- ROA: none5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.252.116.0/24 | No ROA covers it. Add a ROA for AS201750, maxLength 24. |
| ROA: none | 185.252.119.0/24 | No ROA covers it. Add a ROA for AS201750, maxLength 24. |
| ROA: none | 185.252.117.0/24 | No ROA covers it. Add a ROA for AS201750, maxLength 24. |
| ROA: none | 185.252.118.0/24 | No ROA covers it. Add a ROA for AS201750, maxLength 24. |
| ROA: none | 2a0c:2640::/32 | No ROA covers it. Add a ROA for AS201750, maxLength 32. |
Route objects not announced
Route objects with origin AS201750 whose prefix no peer sees AS201750 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.252.116.0/22 | RIPE | No ROA |
| 2a0c:2640::/29 | RIPE | No ROA |
| 2a0c:2641::/32 | RIPE | No ROA |
| 2a0c:2642::/32 | RIPE | No ROA |
| 2a0c:2643::/32 | RIPE | No ROA |
| 2a0c:2644::/32 | RIPE | No ROA |
| 2a0c:2645::/32 | RIPE | No ROA |
| 2a0c:2646::/32 | RIPE | No ROA |
| 2a0c:2647::/32 | RIPE | 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.