Announced routes
Every prefix a peer of the route collectors sees with origin AS11805, 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.
| 165.140.252.0/24 | No ROA | Nonecovered by 165.140.252.0/23 | 672 100% |
| 192.163.28.0/24 | Valid | Nonecovered by 192.163.28.0/22 | 672 100% |
| 192.163.31.0/24 | Valid | Nonecovered by 192.163.28.0/22 | 672 100% |
| 192.163.30.0/24 | Valid | Nonecovered by 192.163.28.0/22 | 671 100% |
| 2602:fd63:31::/48 | Valid | Nonecovered by 2602:fd63::/36 | 605 95% |
| 23.136.44.0/24 | Valid | RIR databaseARIN | 672 100% |
| 192.163.28.0/22 | Valid | RIR databaseARIN | 672 100% |
| 208.91.103.0/24 | Valid | RIR databaseARIN | 671 100% |
| 2602:fd63:12::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS11805: AS-ENNWISE-ALL. 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 (AS11805 isn't in the set, or no route object for AS11805 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 | AS11805 in it | Not covered |
|---|---|---|---|---|---|
| AS-ENNWISE-ALL | ARIN | 7 | 2 | 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 11 are in fix.csv.
- ROA: none1
- Route object: none5
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 165.140.252.0/24 | No ROA covers it. Add a ROA for AS11805, maxLength 24. |
| Route object: none | 165.140.252.0/24 | No route object for it. A route object for 165.140.252.0/23 with origin AS11805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11805 in the RIR database for the space. |
| Route object: none | 192.163.28.0/24 | No route object for it. A route object for 192.163.28.0/22 with origin AS11805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11805 in the RIR database for the space. |
| Route object: none | 192.163.31.0/24 | No route object for it. A route object for 192.163.28.0/22 with origin AS11805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11805 in the RIR database for the space. |
| Route object: none | 192.163.30.0/24 | No route object for it. A route object for 192.163.28.0/22 with origin AS11805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11805 in the RIR database for the space. |
| Route object: none | 2602:fd63:31::/48 | No route object for it. A route object for 2602:fd63::/36 with origin AS11805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11805 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11805 whose prefix no peer sees AS11805 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 155.103.77.0/24 | ARIN | Valid |
| 165.140.252.0/23 | ARIN | No ROA |
| 208.91.102.0/23 | ARIN | Valid |
| 208.91.102.0/24 | ARIN | Valid |
| 2602:fd63::/36 | 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.