Announced routes
Every prefix a peer of the route collectors sees with origin AS58073, 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.38.12.0/24 | Valid | Nonecovered by 185.38.12.0/22 | 673 100% |
| 45.145.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2a02:2a38::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS58073'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 27 are in fix.csv.
- Route object: none1
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.38.12.0/24 | No route object for it. A route object for 185.38.12.0/22 with origin AS58073 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58073 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58073 whose prefix no peer sees AS58073 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.253.18.0/24 | RIPE | Invalid: origin |
| 5.253.19.0/24 | RIPE | Invalid: origin |
| 45.92.156.0/24 | RIPE | Invalid: origin |
| 46.182.104.0/21 | RIPE | No ROA |
| 46.182.104.0/23 | RIPE | No ROA |
| 46.182.104.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 46.182.105.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 46.182.106.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 46.182.107.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 46.182.108.0/24 | RIPE | Invalid: origin |
| 46.182.109.0/24 | NTTCOM, RADB | No ROA |
| 46.182.110.0/24 | NTTCOM, RADB | No ROA |
| 62.197.128.0/19 | NTTCOM, RADB | No ROA |
| 84.239.45.0/24 | NTTCOM | No ROA |
| 185.38.12.0/22 | NTTCOM, RADB | No ROA |
| 185.40.154.0/24 | NTTCOM, RADB | No ROA |
| 185.40.155.0/24 | NTTCOM, RADB | No ROA |
| 185.162.184.0/22 | NTTCOM, RADB | No ROA |
| 185.162.185.0/24 | NTTCOM, RADB | No ROA |
| 185.214.10.0/24 | NTTCOM, RADB, RIPE | Valid |
| 188.215.229.0/24 | NTTCOM, RADB, RIPE | Valid |
| 193.104.186.0/24 | NTTCOM, RADB | No ROA |
| 193.238.45.0/24 | RIPE | Invalid: origin |
| 213.170.133.0/24 | RIPE | Invalid: origin |
| 2a0a:7000::/29 | RIPE | No ROA |
| 2a0c:b847:ffff::/48 | 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.