bgpreport

Network · data from 2026-11-12

AS206996 zap-hosting ZAP-Hosting GmbH

Registry name: zap-hosting ZAP-Hosting GmbH, DE · not in PeeringDB

90IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS206996, seen from no peer

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% 67
2a0c:3580:3000::/36 Valid Nonecovered by 2a0c:3580::/29 635 100% 67
2a0c:3580:4000::/36 Valid Nonecovered by 2a0c:3580::/29 634 100% 67
2a0c:3580:1000::/36 Valid Nonecovered by 2a0c:3580::/29 633 100% 67
5.175.184.0/24 Valid RIR databaseRIPE 673 100% 67
5.231.107.0/24 Valid RIR databaseRIPE 673 100% 67
5.249.166.0/24 Valid RIR databaseRIPE 673 100% 67
147.189.169.0/24 Valid RIR databaseRIPE 673 100% 67
147.189.172.0/24 Valid RIR databaseRIPE 673 100% 67
194.156.90.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.223.0/24 Valid RIR databaseRIPE 672 100% 66
5.231.252.0/24 Valid RIR databaseRIPE 672 100% 66
5.249.160.0/24 Valid RIR databaseRIPE 672 100% 66
5.249.161.0/24 Valid RIR databaseRIPE 672 100% 66
5.249.162.0/24 Valid RIR databaseRIPE 672 100% 66
5.249.164.0/24 Valid RIR databaseRIPE 672 100% 66
31.214.141.0/24 Valid RIR databaseRIPE 672 100% 66
31.214.245.0/24 Valid RIR databaseRIPE 672 100% 66
87.237.52.0/24 Valid RIR databaseRIPE 672 100% 66
87.237.53.0/24 Valid RIR databaseRIPE 672 100% 66
87.237.54.0/24 Valid RIR databaseRIPE 672 100% 66
87.237.55.0/24 Valid RIR databaseRIPE 672 100% 66
88.214.56.0/24 Valid RIR databaseRIPE 672 100% 66
88.214.57.0/24 Valid RIR databaseRIPE 672 100% 66
88.214.58.0/24 Valid RIR databaseRIPE 672 100% 66
88.214.59.0/24 Valid RIR databaseRIPE 672 100% 67
89.144.46.0/24 Valid RIR databaseRIPE 672 100% 66
92.42.44.0/24 Valid RIR databaseRIPE 672 100% 66
92.42.45.0/24 Valid RIR databaseRIPE 672 100% 66
92.42.46.0/24 Valid RIR databaseRIPE 672 100% 66
92.42.47.0/24 Valid RIR databaseRIPE 672 100% 66
94.249.233.0/24 Valid RIR databaseRIPE 672 100% 66
95.156.227.0/24 Valid RIR databaseRIPE 672 100% 66
109.230.238.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.216.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.217.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.218.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.219.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.220.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.225.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.227.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.231.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.232.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.233.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.234.0/24 Valid RIR databaseRIPE 672 100% 66
134.255.252.0/24 Valid RIR databaseRIPE 672 100% 66
147.189.171.0/24 Valid RIR databaseRIPE 672 100% 66
147.189.175.0/24 Valid RIR databaseRIPE 672 100% 66
185.150.25.0/24 Valid RIR databaseRIPE 672 100% 66
185.223.28.0/24 Valid RIR databaseRIPE 672 100% 66
185.223.29.0/24 Valid RIR databaseRIPE 672 100% 66
185.223.30.0/24 Valid RIR databaseRIPE 672 100% 66
185.223.31.0/24 Valid RIR databaseRIPE 672 100% 66
185.239.236.0/24 Valid RIR databaseRIPE 672 100% 66
185.239.237.0/24 Valid RIR databaseRIPE 672 100% 66
185.239.238.0/24 Valid RIR databaseRIPE 672 100% 66
185.239.239.0/24 Valid RIR databaseRIPE 672 100% 66
185.249.196.0/24 Valid RIR databaseRIPE 672 100% 67
185.249.197.0/24 Valid RIR databaseRIPE 672 100% 66
185.249.199.0/24 Valid RIR databaseRIPE 672 100% 66
193.23.126.0/24 Valid RIR databaseRIPE 672 100% 66
193.23.127.0/24 Valid RIR databaseRIPE 672 100% 66
193.23.160.0/24 Valid RIR databaseRIPE 672 100% 66
193.23.161.0/24 Valid RIR databaseRIPE 672 100% 66
193.34.69.0/24 Valid RIR databaseRIPE 672 100% 66
193.203.238.0/24 Valid RIR databaseRIPE 672 100% 66
194.62.1.0/24 Valid RIR databaseRIPE 672 100% 66
194.62.29.0/24 Valid RIR databaseRIPE 672 100% 66
194.62.157.0/24 Valid RIR databaseRIPE 672 100% 66
194.156.88.0/24 Valid RIR databaseRIPE 672 100% 66
194.156.89.0/24 Valid RIR databaseRIPE 672 100% 67
195.62.33.0/24 Valid RIR databaseRIPE 672 100% 66
195.62.47.0/24 Valid RIR databaseRIPE 672 100% 67
5.83.138.0/24 Valid RIR databaseRIPE 671 100% 67
45.141.36.0/24 Valid RIR databaseRIPE 671 100% 66
45.141.37.0/24 Valid RIR databaseRIPE 671 100% 66
45.146.252.0/24 Valid RIR databaseRIPE 671 100% 66
45.146.253.0/24 Valid RIR databaseRIPE 671 100% 66
45.146.254.0/24 Valid RIR databaseRIPE 671 100% 66
45.146.255.0/24 Valid RIR databaseRIPE 671 100% 66
45.156.84.0/24 Valid RIR databaseRIPE 671 100% 66
45.156.85.0/24 Valid RIR databaseRIPE 671 100% 66
185.249.198.0/24 Valid RIR databaseRIPE 671 100% 66
5.175.181.0/24 Valid RIR databaseRIPE 668 99% 67
5.175.213.0/24 Valid RIR databaseRIPE 668 99% 67
5.249.163.0/24 Valid RIR databaseRIPE 668 99% 67
5.249.165.0/24 Valid RIR databaseRIPE 668 99% 67
94.249.185.0/24 Valid RIR databaseRIPE 668 99% 67
147.189.168.0/24 Valid RIR databaseRIPE 668 99% 67
147.189.170.0/24 Valid RIR databaseRIPE 668 99% 67
147.189.173.0/24 Valid RIR databaseRIPE 668 99% 67
147.189.174.0/24 Valid RIR databaseRIPE 668 99% 67
194.156.91.0/24 Valid RIR databaseRIPE 668 99% 67
89.106.74.0/24 Valid RIR databaseRIPE 660 98% 67

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
ChangePrefix or setDetailFull-table peers
Route object: none2a0c:3580:2000::/36No 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.635 of 636
Route object: none2a0c:3580:3000::/36No 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.635 of 636
Route object: none2a0c:3580:4000::/36No 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.634 of 636
Route object: none2a0c:3580:1000::/36No 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.633 of 636

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/24ARINValid
45.43.18.0/24ARINValid
170.39.212.0/24ARINValid
2a0c:3580::/29RIPEValid

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.