Announced routes
Every prefix a peer of the route collectors sees with origin AS64419, 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.
| 79.137.158.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 79.137.168.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 79.137.181.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 79.137.182.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 79.137.185.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 85.192.2.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 85.192.14.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 89.208.70.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.208.112.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.124.194.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 213.232.194.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 77.91.121.0/24 | Valid | Nonecovered by 77.91.120.0/23 | 673 100% |
| 77.91.120.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 77.91.120.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.217.198.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 95.181.148.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.181.149.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS64419'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 13 are in fix.csv.
- ROA: none11
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 79.137.158.0/23 | No ROA covers it. Add a ROA for AS64419, maxLength 23. |
| ROA: none | 79.137.168.0/23 | No ROA covers it. Add a ROA for AS64419, maxLength 23. |
| ROA: none | 79.137.181.0/24 | No ROA covers it. Add a ROA for AS64419, maxLength 24. |
| ROA: none | 79.137.182.0/24 | No ROA covers it. Add a ROA for AS64419, maxLength 24. |
| ROA: none | 79.137.185.0/24 | No ROA covers it. Add a ROA for AS64419, maxLength 24. |
| ROA: none | 85.192.2.0/23 | No ROA covers it. Add a ROA for AS64419, maxLength 23. |
| ROA: none | 85.192.14.0/23 | No ROA covers it. Add a ROA for AS64419, maxLength 23. |
| ROA: none | 89.208.70.0/24 | No ROA covers it. Add a ROA for AS64419, maxLength 24. |
| ROA: none | 89.208.112.0/24 | No ROA covers it. Add a ROA for AS64419, maxLength 24. |
| ROA: none | 176.124.194.0/23 | No ROA covers it. Add a ROA for AS64419, maxLength 23. |
| ROA: none | 213.232.194.0/23 | No ROA covers it. Add a ROA for AS64419, maxLength 23. |
| Route object: none | 77.91.121.0/24 | No route object for it. A route object for 77.91.120.0/23 with origin AS64419 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64419 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS64419 whose prefix no peer sees AS64419 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 95.181.148.0/23 | RIPE | Invalid: origin |
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.