Announced routes
Every prefix a peer of the route collectors sees with origin AS51945, 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.
| 37.122.251.0/24 | No ROA | Nonecovered by 37.122.248.0/21 | 671 100% |
| 37.122.248.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 91.221.152.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.244.181.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a00:7a40::/32 | No ROA | RIR databaseRIPE | 635 100% |
| 185.190.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS51945: AS-CONNETU. 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 (AS51945 isn't in the set, or no route object for AS51945 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 | AS51945 in it | Not covered |
|---|---|---|---|---|---|
| AS-CONNETU | RIPE | 17 | 5 | 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 9 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 37.122.251.0/24 | No ROA covers it. Add a ROA for AS51945, maxLength 24. |
| Route object: none | 37.122.251.0/24 | No route object for it. A route object for 37.122.248.0/21 with origin AS51945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51945 in the RIR database for the space. |
| ROA: none | 37.122.248.0/21 | No ROA covers it. Add a ROA for AS51945, maxLength 21. |
| ROA: none | 91.221.152.0/23 | No ROA covers it. Add a ROA for AS51945, maxLength 23. |
| ROA: none | 91.244.181.0/24 | No ROA covers it. Add a ROA for AS51945, maxLength 24. |
| ROA: none | 2a00:7a40::/32 | No ROA covers it. Add a ROA for AS51945, maxLength 32. |
Route objects not announced
Route objects with origin AS51945 whose prefix no peer sees AS51945 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0c:4380:14e::/48 | RIPE | No ROA |
| 2a0c:4380:38f6::/48 | RIPE | No ROA |
| 2a0c:4380:9ff2::/48 | 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.