Network · data from 2026-11-12
AS209588 FLYSERVERS-ASN Flyservers S.A.
Registry name: FLYSERVERS-ASN Flyservers S.A., PA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209588, 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.
| 2a10:9100:7::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 2a10:9100:9::/48 | No ROA | RIR databaseRIPE | 634 100% |
| 92.51.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 179.60.145.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 141.98.83.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 141.98.82.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS209588 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: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a10:9100:7::/48 | No ROA covers it. Add a ROA for AS209588, maxLength 48. |
| ROA: none | 2a10:9100:9::/48 | No ROA covers it. Add a ROA for AS209588, maxLength 48. |
Route objects not announced
Route objects with origin AS209588 whose prefix no peer sees AS209588 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 141.98.81.0/24 | RIPE | No ROA |
| 179.60.147.0/24 | LACNIC | Valid |
| 2a10:9107:f000::/36 | 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.