Announced routes
Every prefix a peer of the route collectors sees with origin AS205152, 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.
| 44.30.7.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2a0e:b107:e0::/44 | Valid | None | 634 100% |
| 2a0b:4340:1304::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0b:4340:1340::/48 | Valid | RIR databaseRADB, RIPE | 634 100% |
AS-SET
AS205152'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 12 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.30.7.0/24 | No ROA covers it. Add a ROA for AS205152, maxLength 24. |
| Route object: RIR | 44.30.7.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2a0e:b107:e0::/44 | No route object for it. Add a route object with origin AS205152 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205152 whose prefix no peer sees AS205152 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a06:a005:1a80::/44 | RADB | No ROA |
| 2a06:a005:1a90::/44 | RADB | No ROA |
| 2a06:a005:1aa0::/44 | RADB | No ROA |
| 2a06:a005:1ab0::/44 | RADB | No ROA |
| 2a06:a005:1ac0::/44 | RADB | No ROA |
| 2a0b:4340:1300::/40 | RIPE | Valid |
| 2a0b:4340:1303::/48 | RIPE | Valid |
| 2a0b:4340:1303::/64 | RIPE | Invalid: maxLength |
| 2a0b:4340:1310::/48 | RIPE | 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.