Announced routes
Every prefix a peer of the route collectors sees with origin AS44421, 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.
| 185.234.214.233/32 | Invalid: maxLength | Nonecovered by 185.234.214.0/24 | 2 0%low visibility |
| 2a0b:4340:cc::/48 | Valid | Nonecovered by 2a0b:4340:c0::/44 | 634 100% |
| 185.234.214.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 2a0b:4340:c0::/48 | Valid | RIR databaseRADB, RIPE | 635 100% |
| 2a0b:4340:c3::/48 | Valid | RIR databaseRADB, RIPE | 635 100% |
| 2a0b:4340:c8::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:4340:c9::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:4340:c0::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a0b:4340:c6::/48 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS44421: AS-EVE. 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 (AS44421 isn't in the set, or no route object for AS44421 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 | AS44421 in it | Not covered |
|---|---|---|---|---|---|
| AS-EVE | RIPE | 1 | 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 10 are in fix.csv.
- ROA: maxLength1
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.234.214.233/32 | ROA 185.234.214.0/24 AS44421 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.234.214.233/32. |
| Route object: none | 185.234.214.233/32 | No route object for it. A route object for 185.234.214.0/24 with origin AS44421 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS44421 in the RIR database for the space. |
| Route object: none | 2a0b:4340:cc::/48 | No route object for it. A route object for 2a0b:4340:c0::/44 with origin AS44421 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44421 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44421 whose prefix no peer sees AS44421 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0b:4340:c1::/48 | RIPE | Valid |
| 2a0b:4340:c2::/48 | RIPE | Valid |
| 2a0b:4340:c4::/48 | RIPE | Valid |
| 2a0b:4340:c5::/48 | RIPE | Valid |
| 2a0b:4340:c7::/48 | RIPE | Valid |
| 2a0d:2906::/31 | RIPE | Valid |
| 2a0d:2906::/48 | 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.