Announced routes
Every prefix a peer of the route collectors sees with origin AS205368, 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.215.53.0/24 | Invalid: maxLength | RIR databaseRIPE | 0 0%low visibility |
| 46.182.172.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 46.182.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.182.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.215.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.182.174.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.95.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.215.52.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.215.54.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.215.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.86.229.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.237.150.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a02:29f8::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:a3c0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS205368'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 3 are in fix.csv.
- ROA: maxLength1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.215.53.0/24 | ROA 185.215.52.0/22 AS205368 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.215.53.0/24. |
Route objects not announced
Route objects with origin AS205368 whose prefix no peer sees AS205368 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.215.52.0/23 | RIPE | Invalid: maxLength |
| 185.215.54.0/23 | RIPE | Invalid: maxLength |
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.