Network · data from 2026-11-12
AS201172 Sunet-IP-RUNKO Suupohjan Seutuverkko Oy
Registry name: Sunet-IP-RUNKO Suupohjan Seutuverkko Oy, FI · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201172, 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.
| 45.13.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 45.85.232.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.247.132.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 109.204.165.0/24 | Valid | Nonecovered by 109.204.160.0/21 | 672 100% |
| 45.156.92.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 109.204.160.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.83.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.104.188.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.8.226.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 2a05:8c40::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS201172 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 4 are in fix.csv.
- ROA: none3
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.13.60.0/22 | No ROA covers it. Add a ROA for AS201172, maxLength 22. |
| ROA: none | 45.85.232.0/22 | No ROA covers it. Add a ROA for AS201172, maxLength 22. |
| ROA: none | 185.247.132.0/22 | No ROA covers it. Add a ROA for AS201172, maxLength 22. |
| Route object: none | 109.204.165.0/24 | No route object for it. A route object for 109.204.160.0/21 with origin AS201172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201172 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS201172 is announced.
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.