Network · data from 2026-11-12
AS31705 EUMETSAT-OPS Europaischen Organisation fuer die Nutzung Meteorologischen Satelliten (Eumetsat)
Registry name: EUMETSAT-OPS Europaischen Organisation fuer die Nutzung Meteorologischen Satelliten (Eumetsat), DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31705, 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.
| 163.165.192.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 193.17.8.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.17.9.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.76.223.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS31705 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 10 are in fix.csv.
- ROA: none4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 163.165.192.0/18 | No ROA covers it. Add a ROA for AS31705, maxLength 18. |
| ROA: none | 193.17.8.0/22 | No ROA covers it. Add a ROA for AS31705, maxLength 22. |
| ROA: none | 193.17.9.0/24 | No ROA covers it. Add a ROA for AS31705, maxLength 24. |
| ROA: none | 194.76.223.0/24 | No ROA covers it. Add a ROA for AS31705, maxLength 24. |
Route objects not announced
Route objects with origin AS31705 whose prefix no peer sees AS31705 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 163.165.193.0/24 | RIPE | No ROA |
| 163.165.210.0/24 | RIPE | No ROA |
| 163.165.212.0/24 | RIPE | No ROA |
| 193.17.8.0/24 | RIPE | No ROA |
| 193.17.10.0/24 | RIPE | No ROA |
| 193.17.11.0/24 | 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.