Network · data from 2026-11-12
AS60253 GODADDY-CGN Host Europe GmbH
Registry name: GODADDY-CGN Host Europe GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60253, 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.
| 2607:f208:d320::/48 | Invalid: origin | None | 68 11% |
| 2607:f208:d328::/48 | Invalid: origin | None | 68 11% |
| 2607:f208:df07::/48 | Invalid: origin | None | 68 11% |
| 2607:f208:df0d::/48 | Invalid: origin | None | 68 11% |
| 92.205.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 92.205.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.205.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 92.205.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 188.121.60.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.121.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a00:116a:100::/40 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS60253 isn't in PeeringDB, where networks name their 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: origin4
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2607:f208:d320::/48 | ROAs covering it name AS20773, AS26496, not AS60253. If AS60253 should announce it, add a ROA for AS60253. |
| Route object: none | 2607:f208:d320::/48 | No route object for it. Add a route object with origin AS60253 in the RIR database for the space. |
| ROA: origin | 2607:f208:d328::/48 | ROAs covering it name AS20773, AS26496, not AS60253. If AS60253 should announce it, add a ROA for AS60253. |
| Route object: none | 2607:f208:d328::/48 | No route object for it. Add a route object with origin AS60253 in the RIR database for the space. |
| ROA: origin | 2607:f208:df07::/48 | ROAs covering it name AS20773, AS26496, not AS60253. If AS60253 should announce it, add a ROA for AS60253. |
| Route object: none | 2607:f208:df07::/48 | No route object for it. Add a route object with origin AS60253 in the RIR database for the space. |
| ROA: origin | 2607:f208:df0d::/48 | ROAs covering it name AS20773, AS26496, not AS60253. If AS60253 should announce it, add a ROA for AS60253. |
| Route object: none | 2607:f208:df0d::/48 | No route object for it. Add a route object with origin AS60253 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60253 whose prefix no peer sees AS60253 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.205.192.0/20 | RIPE | Valid |
| 188.121.56.0/24 | RIPE | Valid |
| 188.121.62.0/24 | RIPE | Valid |
| 2603:c::/32 | ARIN | Valid |
| 2607:f208:fa::/48 | ARIN | Invalid: origin |
| 2607:f208:7003::/48 | ARIN | Invalid: origin |
| 2a00:116a::/40 | 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.