Announced routes
Every prefix a peer of the route collectors sees with origin AS21030, 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.
| 2a04:8580:ffff::/48 | No ROA | Other origin onlycovered by 2a04:8580::/32 | 636 100% |
| 62.204.57.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 85.209.68.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 85.209.69.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 85.209.70.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 130.49.154.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.40.154.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.40.155.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.253.21.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.253.22.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.253.23.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.119.139.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.209.71.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 216.162.46.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS21030: AS-CDNNOW. 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 (AS21030 isn't in the set, or no route object for AS21030 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 | AS21030 in it | Not covered |
|---|---|---|---|---|---|
| AS-CDNNOW | RIPE | 5 | 1 | 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 17 are in fix.csv.
- ROA: none13
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a04:8580:ffff::/48 | No ROA covers it. Add a ROA for AS21030, maxLength 48. |
| Route object: none | 2a04:8580:ffff::/48 | Route objects for it name AS48989. A route object for 2a04:8580::/32 with origin AS21030 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21030 in the RIR database for the space. |
| ROA: none | 62.204.57.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 85.209.68.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 85.209.69.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 85.209.70.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 130.49.154.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 185.40.154.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 185.40.155.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 185.253.21.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 185.253.22.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 185.253.23.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 217.119.139.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
| ROA: none | 85.209.71.0/24 | No ROA covers it. Add a ROA for AS21030, maxLength 24. |
Route objects not announced
Route objects with origin AS21030 whose prefix no peer sees AS21030 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.40.154.0/23 | RIPE | No ROA |
| 194.67.192.0/24 | RIPE | Valid |
| 2a04:8580::/32 | 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.