Announced routes
Every prefix a peer of the route collectors sees with origin AS51790, 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.
| 91.230.238.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.128.141.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.185.88.0/23 | Valid | None | 671 100% |
| 185.185.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.61.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.136.188.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 45.136.190.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.19.8.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.19.10.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.19.12.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.19.14.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.57.144.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.57.146.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.92.228.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.97.52.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.97.54.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 193.3.59.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 198.60.216.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 209.16.152.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 209.16.154.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.57.145.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 46.19.13.0/24 | Valid | RIR databaseRIPE | 666 99% |
| 2a02:28b2::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:28b0::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a02:28b1::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a02:28b7::/32 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS51790: AS-SIEL. 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 (AS51790 isn't in the set, or no route object for AS51790 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 | AS51790 in it | Not covered |
|---|---|---|---|---|---|
| AS-SIEL | RIPE | 9 | 2 | Yes | 1 |
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 15 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.230.238.0/24 | No ROA covers it. Add a ROA for AS51790, maxLength 24. |
| ROA: none | 195.128.141.0/24 | No ROA covers it. Add a ROA for AS51790, maxLength 24. |
| Route object: none | 185.185.88.0/23 | No route object for it. Add a route object with origin AS51790 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51790 whose prefix no peer sees AS51790 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.19.8.0/21 | RIPE | No ROA |
| 46.19.8.0/24 | RIPE | Valid |
| 46.19.9.0/24 | RIPE | Valid |
| 46.19.10.0/24 | RIPE | Valid |
| 46.19.11.0/24 | RIPE | Valid |
| 46.19.12.0/24 | RIPE | Valid |
| 46.19.14.0/24 | RIPE | Valid |
| 185.57.144.0/24 | RIPE | Invalid: maxLength |
| 185.57.147.0/24 | RIPE | No ROA |
| 185.97.55.0/24 | RIPE | Valid |
| 185.185.90.0/23 | RIPE | Valid |
| 2001:470:435::/48 | ARIN | 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.