Announced routes
Every prefix a peer of the route collectors sees with origin AS62043, 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.
| 195.53.125.0/24 | Invalid: origin | None | 1 0%low visibility |
| 185.145.229.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.145.230.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.145.231.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.145.228.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 205.173.71.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS62043'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 6 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 195.53.125.0/24 | ROAs covering it name AS3352, not AS62043. If AS62043 should announce it, add a ROA for AS62043. |
| Route object: none | 195.53.125.0/24 | No route object for it. Add a route object with origin AS62043 in the RIR database for the space. |
| ROA: none | 185.145.229.0/24 | No ROA covers it. Add a ROA for AS62043, maxLength 24. |
| ROA: none | 185.145.230.0/24 | No ROA covers it. Add a ROA for AS62043, maxLength 24. |
| ROA: none | 185.145.231.0/24 | No ROA covers it. Add a ROA for AS62043, maxLength 24. |
| ROA: none | 185.145.228.0/24 | No ROA covers it. Add a ROA for AS62043, maxLength 24. |
Route objects not announced
Every route object with origin AS62043 is announced.
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.