Network · data from 2026-11-12
AS206996 zap-hosting ZAP-Hosting GmbH
Registry name: zap-hosting ZAP-Hosting GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206996, 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.
| 2a0c:3580:2000::/36 | Valid | Nonecovered by 2a0c:3580::/29 | 635 100% |
| 2a0c:3580:3000::/36 | Valid | Nonecovered by 2a0c:3580::/29 | 635 100% |
| 2a0c:3580:4000::/36 | Valid | Nonecovered by 2a0c:3580::/29 | 634 100% |
| 2a0c:3580:1000::/36 | Valid | Nonecovered by 2a0c:3580::/29 | 633 100% |
| 5.175.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.231.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.249.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 147.189.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 147.189.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.156.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.175.223.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.231.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.249.160.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.249.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.249.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.249.164.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 31.214.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 31.214.245.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.237.52.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.237.53.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.237.54.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.237.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 88.214.56.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 88.214.57.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 88.214.58.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 88.214.59.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.144.46.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.42.44.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.42.45.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.42.46.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.42.47.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.249.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.156.227.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.230.238.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.216.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.217.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.218.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.219.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.220.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.225.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.227.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.232.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.234.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.255.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 147.189.171.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 147.189.175.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.150.25.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.223.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.223.29.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.223.30.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.223.31.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.239.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.239.237.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.239.238.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.239.239.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.249.196.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.249.197.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.249.199.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.23.126.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.23.127.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.23.160.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.23.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.34.69.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.203.238.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.62.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.62.29.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.62.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.156.88.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.156.89.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.62.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.62.47.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.83.138.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.141.36.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.141.37.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.146.252.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.146.253.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.146.254.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.146.255.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.156.84.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.156.85.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.249.198.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.175.181.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 5.175.213.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 5.249.163.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 5.249.165.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 94.249.185.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 147.189.168.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 147.189.170.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 147.189.173.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 147.189.174.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 194.156.91.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 89.106.74.0/24 | Valid | RIR databaseRIPE | 660 98% |
AS-SET
AS206996 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 8 are in fix.csv.
- Route object: none4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a0c:3580:2000::/36 | No route object for it. A route object for 2a0c:3580::/29 with origin AS206996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206996 in the RIR database for the space. |
| Route object: none | 2a0c:3580:3000::/36 | No route object for it. A route object for 2a0c:3580::/29 with origin AS206996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206996 in the RIR database for the space. |
| Route object: none | 2a0c:3580:4000::/36 | No route object for it. A route object for 2a0c:3580::/29 with origin AS206996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206996 in the RIR database for the space. |
| Route object: none | 2a0c:3580:1000::/36 | No route object for it. A route object for 2a0c:3580::/29 with origin AS206996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206996 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206996 whose prefix no peer sees AS206996 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.43.2.0/24 | ARIN | Valid |
| 45.43.18.0/24 | ARIN | Valid |
| 170.39.212.0/24 | ARIN | Valid |
| 2a0c:3580::/29 | 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.