Network · data from 2026-11-12
AS201924 LERTAS-AS ENAHOST s.r.o.
Registry name: LERTAS-AS ENAHOST s.r.o., SK · not in PeeringDB
12IPv4 routes
50.0% RPKI valid · 16.7% with a route object
1IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
7No ROA
10 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS201924, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS201924, 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.
| 141.101.128.0/24 | No ROA | Nonecovered by 141.101.128.0/22 | 673 100% |
| 141.101.129.0/24 | No ROA | Nonecovered by 141.101.128.0/22 | 673 100% |
| 141.101.130.0/24 | No ROA | Nonecovered by 141.101.128.0/22 | 673 100% |
| 154.57.3.0/24 | No ROA | None | 673 100% |
| 141.101.131.0/24 | No ROA | Nonecovered by 141.101.128.0/22 | 671 100% |
| 149.7.226.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2a00:fd40:3::/48 | No ROA | RIR databaseRIPE | 634 100% |
| 195.146.0.0/24 | Valid | Nonecovered by 195.146.0.0/22 | 673 100% |
| 195.146.1.0/24 | Valid | Nonecovered by 195.146.0.0/22 | 673 100% |
| 195.146.2.0/24 | Valid | Nonecovered by 195.146.0.0/22 | 673 100% |
| 195.146.5.0/24 | Valid | Nonecovered by 195.146.0.0/21 | 673 100% |
| 195.146.7.0/24 | Valid | Nonecovered by 195.146.0.0/21 | 673 100% |
| 46.29.2.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS201924 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 22 are in fix.csv.
- ROA: none7
- Route object: none10
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 141.101.128.0/24 | No ROA covers it. Add a ROA for AS201924, maxLength 24. |
| Route object: none | 141.101.128.0/24 | No route object for it. A route object for 141.101.128.0/22 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| ROA: none | 141.101.129.0/24 | No ROA covers it. Add a ROA for AS201924, maxLength 24. |
| Route object: none | 141.101.129.0/24 | No route object for it. A route object for 141.101.128.0/22 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| ROA: none | 141.101.130.0/24 | No ROA covers it. Add a ROA for AS201924, maxLength 24. |
| Route object: none | 141.101.130.0/24 | No route object for it. A route object for 141.101.128.0/22 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| ROA: none | 154.57.3.0/24 | No ROA covers it. Add a ROA for AS201924, maxLength 24. |
| Route object: none | 154.57.3.0/24 | No route object for it. Add a route object with origin AS201924 in the RIR database for the space. |
| ROA: none | 141.101.131.0/24 | No ROA covers it. Add a ROA for AS201924, maxLength 24. |
| Route object: none | 141.101.131.0/24 | No route object for it. A route object for 141.101.128.0/22 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| ROA: none | 149.7.226.0/24 | No ROA covers it. Add a ROA for AS201924, maxLength 24. |
| Route object: RIR | 149.7.226.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2a00:fd40:3::/48 | No ROA covers it. Add a ROA for AS201924, maxLength 48. |
| Route object: none | 195.146.0.0/24 | No route object for it. A route object for 195.146.0.0/22 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| Route object: none | 195.146.1.0/24 | No route object for it. A route object for 195.146.0.0/22 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| Route object: none | 195.146.2.0/24 | No route object for it. A route object for 195.146.0.0/22 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| Route object: none | 195.146.5.0/24 | No route object for it. A route object for 195.146.0.0/21 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
| Route object: none | 195.146.7.0/24 | No route object for it. A route object for 195.146.0.0/21 with origin AS201924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201924 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201924 whose prefix no peer sees AS201924 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 141.101.128.0/22 | RIPE | No ROA |
| 195.146.0.0/21 | RIPE | Invalid: origin |
| 195.146.0.0/22 | RIPE | Invalid: origin |
| 195.146.4.0/24 | 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.