Network · data from 2026-11-12
AS60150 area-7 IT-Services GmbH
Registry name: area-7 area-7 IT-Services GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60150, 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.
| 185.96.56.0/24 | Valid | Nonecovered by 185.96.56.0/22 | 673 100% |
| 185.96.57.0/24 | Valid | Nonecovered by 185.96.56.0/22 | 673 100% |
| 185.136.18.0/24 | Valid | Nonecovered by 185.136.16.0/22 | 673 100% |
| 185.136.19.0/24 | Valid | Nonecovered by 185.136.16.0/22 | 673 100% |
| 2a05:ff00:1::/48 | Valid | Nonecovered by 2a05:ff00::/29 | 636 100% |
| 2a05:ff00:2::/48 | Valid | Nonecovered by 2a05:ff00::/29 | 636 100% |
| 2a05:ff00:1000::/36 | Valid | Nonecovered by 2a05:ff00::/29 | 636 100% |
| 2a05:ff00:2000::/36 | Valid | Nonecovered by 2a05:ff00::/29 | 636 100% |
| 45.12.100.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.96.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.136.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2001:678:6bc::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:678:ef0::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:678:ef4::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:678:ef8::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:270::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:28a0::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a05:ff00::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS60150: AS-LEBHERZ. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS60150 isn't in the set, or no route object for AS60150 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS60150 in it | Not covered |
|---|---|---|---|---|---|
| AS-LEBHERZ | RIPE | 3 | 1 | Yes | 0 |
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 9 are in fix.csv.
- Route object: none8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.96.56.0/24 | No route object for it. A route object for 185.96.56.0/22 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
| Route object: none | 185.96.57.0/24 | No route object for it. A route object for 185.96.56.0/22 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
| Route object: none | 185.136.18.0/24 | No route object for it. A route object for 185.136.16.0/22 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
| Route object: none | 185.136.19.0/24 | No route object for it. A route object for 185.136.16.0/22 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
| Route object: none | 2a05:ff00:1::/48 | No route object for it. A route object for 2a05:ff00::/29 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
| Route object: none | 2a05:ff00:2::/48 | No route object for it. A route object for 2a05:ff00::/29 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
| Route object: none | 2a05:ff00:1000::/36 | No route object for it. A route object for 2a05:ff00::/29 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
| Route object: none | 2a05:ff00:2000::/36 | No route object for it. A route object for 2a05:ff00::/29 with origin AS60150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60150 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60150 whose prefix no peer sees AS60150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a07:5b40::/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.