Announced routes
Every prefix a peer of the route collectors sees with origin AS205638, 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.211.158.0/23 | Valid | Nonecovered by 185.211.156.0/22 | 2 0%low visibility |
| 45.137.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.137.112.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.137.113.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.137.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.225.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.211.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.211.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.211.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.211.159.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.233.84.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.233.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.233.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.233.86.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.233.86.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.233.87.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.226.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.143.64.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.143.65.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.143.66.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.143.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.137.112.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS205638'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 7 are in fix.csv.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.211.158.0/23 | No route object for it. A route object for 185.211.156.0/22 with origin AS205638 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205638 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205638 whose prefix no peer sees AS205638 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.137.114.0/23 | RIPE | Invalid: maxLength |
| 45.137.114.0/24 | RIPE | Invalid: maxLength |
| 185.211.157.0/24 | RIPE | Valid |
| 193.143.64.0/23 | RIPE | No ROA |
| 212.233.84.0/22 | RIPE | No ROA |
| 2a0b:66c0::/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.