Network · data from 2026-11-12
AS199508 S1 Networks
Registry name: S1NETWORKS-AS S1 Networks Oy, FI · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199508, 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.
| 194.110.224.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 194.110.232.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 195.20.149.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:67c:2ce8::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 45.8.128.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 62.220.224.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 62.220.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.194.236.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.41.48.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.42.43.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.11.208.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.195.149.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.195.150.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.192.250.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:b5a0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a03:6f40::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS199508: AS-S1NET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS199508 isn't in the set, or no route object for AS199508 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS199508 in it | Not covered |
|---|---|---|---|---|---|
| AS-S1NET | RIPE | 19 | 4 | Yes | 0 |
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 7 are in fix.csv.
- ROA: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.110.224.0/21 | No ROA covers it. Add a ROA for AS199508, maxLength 21. |
| ROA: none | 194.110.232.0/22 | No ROA covers it. Add a ROA for AS199508, maxLength 22. |
| ROA: none | 195.20.149.0/24 | No ROA covers it. Add a ROA for AS199508, maxLength 24. |
| ROA: none | 2001:67c:2ce8::/48 | No ROA covers it. Add a ROA for AS199508, maxLength 48. |
Route objects not announced
Route objects with origin AS199508 whose prefix no peer sees AS199508 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.220.224.0/23 | RIPE | Invalid: maxLength |
| 62.220.226.0/23 | RIPE | Invalid: maxLength |
| 93.90.48.0/20 | 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.