Network · data from 2026-11-12
AS9059 AWS-EU-AS Amazon Data Services Ireland Ltd
Registry name: AWS-EU-AS Amazon Data Services Ireland Ltd, IE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9059, 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.
| 90.139.121.0/24 | Invalid: origin | None | 1 0%low visibility |
| 90.139.122.0/24 | Invalid: origin | None | 1 0%low visibility |
| 90.139.124.0/23 | Invalid: origin | None | 1 0%low visibility |
AS-SET
AS9059 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 7 are in fix.csv.
- ROA: origin3
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 90.139.121.0/24 | ROAs covering it name AS1257, not AS9059. If AS9059 should announce it, add a ROA for AS9059. |
| Route object: none | 90.139.121.0/24 | No route object for it. Add a route object with origin AS9059 in the RIR database for the space. |
| ROA: origin | 90.139.122.0/24 | ROAs covering it name AS1257, not AS9059. If AS9059 should announce it, add a ROA for AS9059. |
| Route object: none | 90.139.122.0/24 | No route object for it. Add a route object with origin AS9059 in the RIR database for the space. |
| ROA: origin | 90.139.124.0/23 | ROAs covering it name AS1257, not AS9059. If AS9059 should announce it, add a ROA for AS9059. |
| Route object: none | 90.139.124.0/23 | No route object for it. Add a route object with origin AS9059 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9059 whose prefix no peer sees AS9059 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.8.10.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.