Network · data from 2026-11-12
AS44295 Lab Group
Registry name: LAB-AS Lab Luxembourg S.A., LU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44295, 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.202.248.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 2a0a:cf40::/29 | No ROA | RIR databaseRIPE | 634 100% |
| 92.42.176.0/21 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS44295's PeeringDB record names no 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 2 are in fix.csv.
- ROA: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.202.248.0/22 | No ROA covers it. Add a ROA for AS44295, maxLength 22. |
| ROA: none | 2a0a:cf40::/29 | No ROA covers it. Add a ROA for AS44295, maxLength 29. |
Route objects not announced
Every route object with origin AS44295 is announced.
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.