Network · data from 2026-11-12
AS216134 ZF-Friedrichshafen-AG ZF Friedrichshafen AG
Registry name: ZF-Friedrichshafen-AG ZF Friedrichshafen AG, DE · not in PeeringDB
48IPv4 routes
97.9% RPKI valid · 56.2% with a route object
3IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
21 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
12Route objects not announced
registered with origin AS216134, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS216134, 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.
| 192.43.234.0/24 | No ROA | None | 672 100% |
| 149.238.80.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 673 100% |
| 149.238.126.0/23 | Valid | Nonecovered by 149.238.0.0/16 | 673 100% |
| 140.171.0.0/16 | Valid | None | 672 100% |
| 149.238.64.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 672 100% |
| 149.238.65.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 672 100% |
| 149.238.66.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 672 100% |
| 149.238.68.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 672 100% |
| 149.238.70.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 672 100% |
| 149.238.71.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 672 100% |
| 149.238.81.0/24 | Valid | Nonecovered by 149.238.64.0/19 | 672 100% |
| 149.238.96.0/20 | Valid | Nonecovered by 149.238.0.0/16 | 672 100% |
| 149.238.96.0/24 | Valid | Nonecovered by 149.238.0.0/16 | 672 100% |
| 149.238.97.0/24 | Valid | Nonecovered by 149.238.0.0/16 | 672 100% |
| 149.238.100.0/24 | Valid | Nonecovered by 149.238.0.0/16 | 672 100% |
| 149.238.114.0/24 | Valid | Nonecovered by 149.238.0.0/16 | 672 100% |
| 149.238.118.0/23 | Valid | Nonecovered by 149.238.0.0/16 | 672 100% |
| 149.238.122.0/23 | Valid | Other origin onlycovered by 149.238.0.0/16 | 672 100% |
| 149.238.124.0/23 | Valid | Other origin onlycovered by 149.238.0.0/16 | 672 100% |
| 192.101.48.0/20 | Valid | None | 672 100% |
| 149.238.96.0/19 | Valid | Other origin onlycovered by 149.238.0.0/16 | 2 0%low visibility |
| 149.238.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 149.238.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 149.238.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 149.238.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 149.238.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 192.112.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 204.235.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 204.235.186.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 149.223.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 149.223.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 149.238.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 149.238.128.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 149.238.128.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 149.238.129.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 149.238.135.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 170.205.192.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 192.77.114.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.33.52.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.33.52.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.202.20.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 204.235.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 204.235.180.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 204.235.184.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 204.235.184.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 204.235.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 204.235.188.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 204.235.190.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 2a13:cb41::/33 | Valid | RIR databaseRIPE | 633 100% |
| 2a13:cb41:8000::/33 | Valid | RIR databaseRIPE | 633 100% |
| 2a13:cb42:8000::/33 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS216134 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 34 are in fix.csv.
- ROA: none1
- Route object: none21
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.43.234.0/24 | No ROA covers it. Add a ROA for AS216134, maxLength 24. |
| Route object: none | 192.43.234.0/24 | No route object for it. Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.80.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.126.0/23 | No route object for it. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 140.171.0.0/16 | No route object for it. Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.64.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.65.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.66.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.68.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.70.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.71.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.81.0/24 | No route object for it. A route object for 149.238.64.0/19 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.96.0/20 | No route object for it. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.96.0/24 | No route object for it. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.97.0/24 | No route object for it. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.100.0/24 | No route object for it. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.114.0/24 | No route object for it. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.118.0/23 | No route object for it. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.122.0/23 | Route objects for it name AS51964. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.124.0/23 | Route objects for it name AS51964. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 192.101.48.0/20 | No route object for it. Add a route object with origin AS216134 in the RIR database for the space. |
| Route object: none | 149.238.96.0/19 | Route objects for it name AS51964. A route object for 149.238.0.0/16 with origin AS216134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216134 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS216134 whose prefix no peer sees AS216134 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 149.223.0.0/16 | RIPE | Valid |
| 149.223.128.0/19 | RIPE | Valid |
| 149.238.0.0/16 | RIPE | Valid |
| 149.238.94.0/24 | RIPE | Valid |
| 149.238.95.0/24 | RIPE | Valid |
| 149.238.158.0/24 | RIPE | Valid |
| 149.238.159.0/24 | RIPE | Valid |
| 193.33.53.0/24 | RIPE | Valid |
| 193.39.210.0/24 | RIPE | Valid |
| 193.39.211.0/24 | RIPE | Valid |
| 193.39.214.0/24 | RIPE | Valid |
| 2a13:cb42:8013::/48 | 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.