Network · data from 2026-11-12
AS35042 Layer7-Networks-DE Layer7 Networks GmbH
Registry name: Layer7-Networks-DE Layer7 Networks GmbH, DE · not in PeeringDB
13IPv4 routes
84.6% RPKI valid · 76.9% with a route object
17IPv6 routes
100.0% RPKI valid · 0.0% with a route object
2RPKI invalid
2 origin · 0 maxLength
0No ROA
20 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS35042, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS35042, 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.55.240.0/22 | Invalid: origin | Other origin only | 2 0%low visibility |
| 193.24.208.0/23 | Invalid: origin | None | 2 0%low visibility |
| 88.214.25.0/24 | Valid | Other origin only | 671 100% |
| 2a00:1911::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:1::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:3::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:4::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:5::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:6::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:7::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:8::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:9::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1911:10::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1912::/32 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1912:1::/48 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a00:1913::/32 | Valid | Nonecovered by 2a00:1910::/29 | 634 100% |
| 2a09:8700::/32 | Valid | Other origin only | 634 100% |
| 2a09:8700:2::/48 | Valid | None | 634 100% |
| 2a00:1910::/32 | Valid | Nonecovered by 2a00:1910::/29 | 627 99% |
| 2a00:1911::/32 | Valid | Nonecovered by 2a00:1910::/29 | 627 99% |
| 88.214.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.228.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.133.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 179.60.150.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 185.55.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.55.243.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.24.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.24.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.24.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.93.196.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS35042 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 24 are in fix.csv.
- ROA: origin2
- Route object: none20
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.55.240.0/22 | ROAs covering it name AS211179, not AS35042. If AS35042 should announce it, add a ROA for AS35042. |
| Route object: none | 185.55.240.0/22 | Route objects for it name AS29551. Add a route object with origin AS35042 in the RIR database for the space. |
| ROA: origin | 193.24.208.0/23 | ROAs covering it name AS29551, not AS35042. If AS35042 should announce it, add a ROA for AS35042. |
| Route object: none | 193.24.208.0/23 | No route object for it. Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 88.214.25.0/24 | Route objects for it name AS29551. Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:1::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:3::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:4::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:5::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:6::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:7::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:8::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:9::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911:10::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1912::/32 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1912:1::/48 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1913::/32 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a09:8700::/32 | Route objects for it name AS12586. Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a09:8700:2::/48 | No route object for it. Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1910::/32 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
| Route object: none | 2a00:1911::/32 | No route object for it. A route object for 2a00:1910::/29 with origin AS35042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35042 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35042 whose prefix no peer sees AS35042 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.241.44.0/24 | RIPE | Invalid: origin |
| 2a00:1910::/29 | RIPE | No ROA |
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.