Network · data from 2026-11-12
AS43980 LEKKERLAND-AS Lekkerland SE
Registry name: LEKKERLAND-AS Lekkerland SE, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43980, 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.
| 91.198.242.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.29.118.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.29.119.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a04:44c0:1000::/48 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS43980 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 5 are in fix.csv.
- ROA: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.198.242.0/24 | No ROA covers it. Add a ROA for AS43980, maxLength 24. |
| ROA: none | 185.29.118.0/24 | No ROA covers it. Add a ROA for AS43980, maxLength 24. |
| ROA: none | 185.29.119.0/24 | No ROA covers it. Add a ROA for AS43980, maxLength 24. |
| ROA: none | 2a04:44c0:1000::/48 | No ROA covers it. Add a ROA for AS43980, maxLength 48. |
Route objects not announced
Route objects with origin AS43980 whose prefix no peer sees AS43980 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a04:44c0::/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.