Announced routes
Every prefix a peer of the route collectors sees with origin AS47820, 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.205.116.0/24 | Valid | Nonecovered by 91.205.116.0/23 | 670 100% |
| 91.205.117.0/24 | Valid | Nonecovered by 91.205.116.0/23 | 670 100% |
| 91.205.118.0/24 | Valid | Nonecovered by 91.205.118.0/23 | 670 100% |
| 91.205.119.0/24 | Valid | Nonecovered by 91.205.118.0/23 | 670 100% |
| 185.148.226.0/24 | Valid | Nonecovered by 185.148.226.0/23 | 670 100% |
| 185.148.227.0/24 | Valid | Nonecovered by 185.148.226.0/23 | 670 100% |
| 193.242.174.0/24 | Valid | Nonecovered by 193.242.174.0/23 | 670 100% |
| 193.242.175.0/24 | Valid | Nonecovered by 193.242.174.0/23 | 670 100% |
| 185.232.192.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 91.205.116.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 91.205.118.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 109.234.0.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 185.148.226.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 193.242.174.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 2a07:6200::/29 | Valid | RIR databaseRIPE | 369 58% |
AS-SET
AS47820's PeeringDB record names no AS-SET.
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 14 are in fix.csv.
- Route object: none8
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.205.116.0/24 | No route object for it. A route object for 91.205.116.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
| Route object: none | 91.205.117.0/24 | No route object for it. A route object for 91.205.116.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
| Route object: none | 91.205.118.0/24 | No route object for it. A route object for 91.205.118.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
| Route object: none | 91.205.119.0/24 | No route object for it. A route object for 91.205.118.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
| Route object: none | 185.148.226.0/24 | No route object for it. A route object for 185.148.226.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
| Route object: none | 185.148.227.0/24 | No route object for it. A route object for 185.148.226.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
| Route object: none | 193.242.174.0/24 | No route object for it. A route object for 193.242.174.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
| Route object: none | 193.242.175.0/24 | No route object for it. A route object for 193.242.174.0/23 with origin AS47820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47820 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS47820 whose prefix no peer sees AS47820 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.205.116.0/22 | RIPE | Valid |
| 91.209.107.0/24 | RIPE | Invalid: origin |
| 109.234.0.0/24 | RIPE | Valid |
| 109.234.1.0/24 | RIPE | Valid |
| 109.234.2.0/24 | RIPE | Valid |
| 185.148.224.0/22 | 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.