Network · data from 2026-11-12
AS34011 GD-EMEA-DC-CGN1 Host Europe GmbH
Registry name: GD-EMEA-DC-CGN1 Host Europe GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34011, 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.
| 62.138.34.0/24 | Valid | Nonecovered by 62.138.32.0/20 | 672 100% |
| 62.138.163.0/24 | Valid | None | 672 100% |
| 80.237.133.0/24 | Valid | Nonecovered by 80.237.132.0/23 | 671 100% |
| 2001:1520:100::/40 | Valid | None | 635 100% |
| 2001:1520:101::/48 | Valid | None | 635 100% |
| 37.200.96.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 46.163.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 46.252.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 62.138.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 62.138.128.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 80.67.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 80.237.132.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 83.169.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.169.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 87.230.40.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 87.230.44.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 87.230.60.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 87.230.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.204.32.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 93.180.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 93.187.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 109.239.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 141.0.16.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 176.28.32.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.28.36.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.221.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.77.80.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 178.77.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 188.93.8.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 62.138.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.204.32.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.204.37.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.204.38.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.204.39.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 93.180.152.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.0.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 134.119.18.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.86.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.225.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.226.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.228.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.229.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.232.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.240.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.241.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.244.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.245.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.246.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.247.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.119.254.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.67.16.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.237.132.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.237.137.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.237.138.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2001:1520:3::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:1168:101::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:1158::/32 | Valid | RIR databaseRIPE | 369 58% |
AS-SET
AS34011 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 72 are in fix.csv.
- Route object: none5
- Route object: not announced67
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 62.138.34.0/24 | No route object for it. A route object for 62.138.32.0/20 with origin AS34011 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34011 in the RIR database for the space. |
| Route object: none | 62.138.163.0/24 | No route object for it. Add a route object with origin AS34011 in the RIR database for the space. |
| Route object: none | 80.237.133.0/24 | No route object for it. A route object for 80.237.132.0/23 with origin AS34011 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34011 in the RIR database for the space. |
| Route object: none | 2001:1520:100::/40 | No route object for it. Add a route object with origin AS34011 in the RIR database for the space. |
| Route object: none | 2001:1520:101::/48 | No route object for it. Add a route object with origin AS34011 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34011 whose prefix no peer sees AS34011 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.200.98.0/24 | RIPE | Valid |
| 37.200.99.0/24 | RIPE | Valid |
| 46.252.16.0/24 | RIPE | Valid |
| 46.252.19.0/24 | RIPE | Valid |
| 46.252.20.0/24 | RIPE | Valid |
| 46.252.21.0/24 | RIPE | Valid |
| 46.252.24.0/24 | RIPE | Valid |
| 46.252.25.0/24 | RIPE | Valid |
| 46.252.26.0/24 | RIPE | Valid |
| 46.252.27.0/24 | RIPE | Valid |
| 46.252.28.0/24 | RIPE | Valid |
| 46.252.29.0/24 | RIPE | Valid |
| 46.252.30.0/24 | RIPE | Valid |
| 62.138.162.0/24 | RIPE | Valid |
| 80.237.128.0/24 | RIPE | Valid |
| 80.237.128.56/31 | RIPE | Invalid: maxLength |
| 80.237.128.144/31 | RIPE | Invalid: maxLength |
| 80.237.136.0/24 | RIPE | Valid |
| 92.204.33.0/24 | RIPE | Valid |
| 92.204.34.0/24 | RIPE | Invalid: maxLength |
| 92.204.35.0/24 | RIPE | Invalid: maxLength |
| 92.205.80.0/21 | RIPE | Invalid: origin |
| 93.180.154.0/24 | RIPE | Valid |
| 93.180.155.0/24 | RIPE | Valid |
| 93.180.156.0/24 | RIPE | Valid |
| 93.180.157.0/24 | RIPE | Valid |
| 109.239.48.0/24 | RIPE | Valid |
| 109.239.49.0/24 | RIPE | Valid |
| 109.239.50.0/24 | RIPE | Valid |
| 109.239.57.0/24 | RIPE | Valid |
| 109.239.58.0/24 | RIPE | Valid |
| 109.239.60.0/24 | RIPE | Valid |
| 134.119.1.0/24 | RIPE | Valid |
| 134.119.3.0/24 | RIPE | Valid |
| 134.119.4.0/24 | RIPE | Valid |
| 134.119.5.0/24 | RIPE | Valid |
| 134.119.8.0/24 | RIPE | Valid |
| 134.119.9.0/24 | RIPE | Valid |
| 134.119.10.0/24 | RIPE | Valid |
| 134.119.11.0/24 | RIPE | Valid |
| 134.119.13.0/24 | RIPE | Valid |
| 134.119.17.0/24 | RIPE | Valid |
| 134.119.20.0/24 | RIPE | Valid |
| 134.119.21.0/24 | RIPE | Valid |
| 134.119.24.0/24 | RIPE | Valid |
| 134.119.26.0/24 | RIPE | Valid |
| 134.119.28.0/24 | RIPE | No ROA |
| 134.119.30.0/24 | RIPE | Valid |
| 134.119.32.0/24 | RIPE | Valid |
| 134.119.36.0/24 | RIPE | Valid |
| 134.119.39.0/24 | RIPE | Valid |
| 134.119.42.0/24 | RIPE | Valid |
| 134.119.46.0/24 | RIPE | Valid |
| 134.119.49.0/24 | RIPE | Valid |
| 134.119.227.0/24 | RIPE | Valid |
| 134.119.230.0/24 | RIPE | Valid |
| 134.119.252.0/24 | RIPE | Valid |
| 134.119.253.0/24 | RIPE | Valid |
| 141.0.20.0/24 | RIPE | Valid |
| 141.0.21.0/24 | RIPE | Valid |
| 176.28.5.0/24 | RIPE | Valid |
| 176.221.42.0/24 | RIPE | Valid |
| 176.221.43.0/24 | RIPE | Valid |
| 176.221.46.0/24 | RIPE | Valid |
| 217.115.143.0/24 | RIPE | Valid |
| 217.115.143.224/31 | RIPE | Invalid: maxLength |
| 2a01:488::/126 | RIPE | Invalid: maxLength |
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.