Announced routes
Every prefix a peer of the route collectors sees with origin AS18245, 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.
| 59.108.45.0/24 | Invalid: origin | None | 125 19% |
| 59.108.133.0/24 | Invalid: origin | None | 125 19% |
| 59.108.139.0/24 | Invalid: origin | None | 125 19% |
| 59.108.140.0/24 | Invalid: origin | None | 125 19% |
| 59.108.155.0/24 | Invalid: origin | None | 125 19% |
| 59.108.91.0/24 | Valid | None | 2 0%low visibility |
AS-SET
AS18245'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 15 are in fix.csv.
- ROA: origin5
- Route object: none6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 59.108.45.0/24 | ROAs covering it name AS4847, not AS18245. If AS18245 should announce it, add a ROA for AS18245. |
| Route object: none | 59.108.45.0/24 | No route object for it. Add a route object with origin AS18245 in the RIR database for the space. |
| ROA: origin | 59.108.133.0/24 | ROAs covering it name AS4847, not AS18245. If AS18245 should announce it, add a ROA for AS18245. |
| Route object: none | 59.108.133.0/24 | No route object for it. Add a route object with origin AS18245 in the RIR database for the space. |
| ROA: origin | 59.108.139.0/24 | ROAs covering it name AS4847, not AS18245. If AS18245 should announce it, add a ROA for AS18245. |
| Route object: none | 59.108.139.0/24 | No route object for it. Add a route object with origin AS18245 in the RIR database for the space. |
| ROA: origin | 59.108.140.0/24 | ROAs covering it name AS4847, not AS18245. If AS18245 should announce it, add a ROA for AS18245. |
| Route object: none | 59.108.140.0/24 | No route object for it. Add a route object with origin AS18245 in the RIR database for the space. |
| ROA: origin | 59.108.155.0/24 | ROAs covering it name AS4847, not AS18245. If AS18245 should announce it, add a ROA for AS18245. |
| Route object: none | 59.108.155.0/24 | No route object for it. Add a route object with origin AS18245 in the RIR database for the space. |
| Route object: none | 59.108.91.0/24 | No route object for it. Add a route object with origin AS18245 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18245 whose prefix no peer sees AS18245 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 59.108.1.0/24 | APNIC | Invalid: origin |
| 59.108.16.0/20 | APNIC | Invalid: origin |
| 59.108.40.0/24 | APNIC | Invalid: origin |
| 218.240.224.0/22 | APNIC, RADB | 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.