Network · data from 2026-11-12
AS208968 Avacon Connect
Registry name: Avacon-Connect-de Avacon Connect GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208968, 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.
| 45.13.20.0/23 | No ROA | Nonecovered by 45.13.20.0/22 | 671 100% |
| 45.13.22.0/23 | No ROA | Nonecovered by 45.13.20.0/22 | 671 100% |
| 185.160.100.0/23 | No ROA | Nonecovered by 185.160.100.0/22 | 671 100% |
| 2a0e:ab05::/32 | No ROA | Nonecovered by 2a0e:ab00::/29 | 635 100% |
| 2a0e:ab06::/32 | No ROA | Nonecovered by 2a0e:ab00::/29 | 635 100% |
| 2a0e:ab07::/32 | No ROA | Nonecovered by 2a0e:ab00::/29 | 635 100% |
| 45.13.20.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 85.190.224.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.35.132.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.160.100.0/22 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS208968'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 17 are in fix.csv.
- ROA: none10
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.13.20.0/23 | No ROA covers it. Add a ROA for AS208968, maxLength 23. |
| Route object: none | 45.13.20.0/23 | No route object for it. A route object for 45.13.20.0/22 with origin AS208968 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208968 in the RIR database for the space. |
| ROA: none | 45.13.22.0/23 | No ROA covers it. Add a ROA for AS208968, maxLength 23. |
| Route object: none | 45.13.22.0/23 | No route object for it. A route object for 45.13.20.0/22 with origin AS208968 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208968 in the RIR database for the space. |
| ROA: none | 185.160.100.0/23 | No ROA covers it. Add a ROA for AS208968, maxLength 23. |
| Route object: none | 185.160.100.0/23 | No route object for it. A route object for 185.160.100.0/22 with origin AS208968 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208968 in the RIR database for the space. |
| ROA: none | 2a0e:ab05::/32 | No ROA covers it. Add a ROA for AS208968, maxLength 32. |
| Route object: none | 2a0e:ab05::/32 | No route object for it. A route object for 2a0e:ab00::/29 with origin AS208968 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208968 in the RIR database for the space. |
| ROA: none | 2a0e:ab06::/32 | No ROA covers it. Add a ROA for AS208968, maxLength 32. |
| Route object: none | 2a0e:ab06::/32 | No route object for it. A route object for 2a0e:ab00::/29 with origin AS208968 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208968 in the RIR database for the space. |
| ROA: none | 2a0e:ab07::/32 | No ROA covers it. Add a ROA for AS208968, maxLength 32. |
| Route object: none | 2a0e:ab07::/32 | No route object for it. A route object for 2a0e:ab00::/29 with origin AS208968 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208968 in the RIR database for the space. |
| ROA: none | 45.13.20.0/22 | No ROA covers it. Add a ROA for AS208968, maxLength 22. |
| ROA: none | 85.190.224.0/22 | No ROA covers it. Add a ROA for AS208968, maxLength 22. |
| ROA: none | 185.35.132.0/22 | No ROA covers it. Add a ROA for AS208968, maxLength 22. |
| ROA: none | 185.160.100.0/22 | No ROA covers it. Add a ROA for AS208968, maxLength 22. |
Route objects not announced
Route objects with origin AS208968 whose prefix no peer sees AS208968 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0e:ab00::/29 | RIPE | 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.