Announced routes
Every prefix a peer of the route collectors sees with origin AS205781, 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.
| 82.24.83.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 82.153.246.0/24 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS205781'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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 82.24.83.0/24 | ROAs covering it name AS834, not AS205781. If AS205781 should announce it, add a ROA for AS205781. |
| Route object: none | 82.24.83.0/24 | Route objects for it name AS834. Add a route object with origin AS205781 in the RIR database for the space. |
| Route object: RIR | 82.153.246.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205781 whose prefix no peer sees AS205781 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a06:9801:1517::/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.