Announced routes
Every prefix a peer of the route collectors sees with origin AS58182, 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.230.60.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.230.62.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.230.63.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 199.15.160.0/24 | Valid | RIR databaseARIN | 673 100% |
| 199.15.163.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS58182'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 19 are in fix.csv.
- ROA: none3
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.230.60.0/24 | No ROA covers it. Add a ROA for AS58182, maxLength 24. |
| ROA: none | 185.230.62.0/24 | No ROA covers it. Add a ROA for AS58182, maxLength 24. |
| ROA: none | 185.230.63.0/24 | No ROA covers it. Add a ROA for AS58182, maxLength 24. |
Route objects not announced
Route objects with origin AS58182 whose prefix no peer sees AS58182 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.7.220.0/24 | ARIN | Valid |
| 64.95.157.0/24 | ARIN | Valid |
| 65.38.108.0/24 | ARIN | Invalid: origin |
| 70.42.116.0/24 | ARIN | Valid |
| 70.42.119.0/24 | ARIN | Valid |
| 185.230.60.0/22 | RIPE | No ROA |
| 185.230.60.0/23 | RIPE | No ROA |
| 185.230.61.0/24 | RIPE | No ROA |
| 185.230.62.0/23 | RIPE | No ROA |
| 199.15.160.0/22 | ARIN | Valid |
| 199.15.161.0/24 | ARIN | Valid |
| 199.15.162.0/24 | ARIN | Valid |
| 216.52.12.0/24 | ARIN | Valid |
| 216.52.15.0/24 | ARIN | Valid |
| 216.52.17.0/24 | ARIN | Valid |
| 216.52.21.0/24 | ARIN | 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.