Announced routes
Every prefix a peer of the route collectors sees with origin AS42000, 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.103.160.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 94.124.104.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 192.162.96.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.99.68.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.11.245.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a00:1790::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS42000: RIPE::AS-KAORA. 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 (AS42000 isn't in the set, or no route object for AS42000 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 | AS42000 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-KAORA | RIPElists itself further down5 member sets in no database: AS-GLOBALIPEXCHNAGE7, AS-NIX-RIS, AS-SET-CBS, AS-SPEEDNET, AS18229:AS-PEL | 653 | 127 | 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 24 are in fix.csv.
- ROA: none3
- AS-SET: missing member5
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.103.160.0/21 | No ROA covers it. Add a ROA for AS42000, maxLength 21. |
| ROA: none | 94.124.104.0/21 | No ROA covers it. Add a ROA for AS42000, maxLength 21. |
| ROA: none | 192.162.96.0/22 | No ROA covers it. Add a ROA for AS42000, maxLength 22. |
| AS-SET: missing member | RIPE::AS-KAORA | AS-KAORA (RIPE) lists AS-GLOBALIPEXCHNAGE7; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-KAORA | AS-KAORA (RIPE) lists AS-NIX-RIS; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-KAORA | AS-KAORA (RIPE) lists AS-SET-CBS; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-KAORA | AS-KAORA (RIPE) lists AS-SPEEDNET; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-KAORA | AS-KAORA (RIPE) lists AS18229:AS-PEL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS42000 whose prefix no peer sees AS42000 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.103.160.0/22 | RIPE | No ROA |
| 91.103.164.0/22 | RIPE | No ROA |
| 91.103.164.0/24 | RIPE | No ROA |
| 91.103.165.0/24 | RIPE | No ROA |
| 91.103.166.0/24 | RIPE | No ROA |
| 91.103.167.0/24 | RIPE | No ROA |
| 94.124.104.0/22 | RIPE | No ROA |
| 94.124.108.0/22 | RIPE | No ROA |
| 185.216.220.0/22 | RIPE | Valid |
| 203.31.160.0/24 | ARIN | Valid |
| 212.18.101.0/24 | RIPE | Valid |
| 2602:f666:10::/44 | ARIN | Valid |
| 2a00:1790::/32 | RIPE | Invalid: maxLength |
| 2a0b:bdc0::/29 | RIPE | Valid |
| 2a0b:bdc0::/32 | RIPE | Valid |
| 2a12:5c00::/32 | 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.