Network · data from 2026-11-12
AS25367 AS-ADTS-LU Proximus Luxembourg S.A.
Registry name: AS-ADTS-LU Proximus Luxembourg S.A., LU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25367, 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.
| 156.133.108.0/24 | No ROA | Nonecovered by 156.133.108.0/22 | 673 100% |
| 141.96.6.0/24 | No ROA | Nonecovered by 141.96.0.0/16 | 672 100% |
| 141.96.7.0/24 | No ROA | Nonecovered by 141.96.0.0/16 | 672 100% |
| 141.96.0.0/16 | No ROA | RIR databaseRIPE | 671 100% |
| 156.133.48.0/20 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 212.63.224.0/19 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS25367 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 10 are in fix.csv.
- ROA: none5
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 156.133.108.0/24 | No ROA covers it. Add a ROA for AS25367, maxLength 24. |
| Route object: none | 156.133.108.0/24 | No route object for it. A route object for 156.133.108.0/22 with origin AS25367 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25367 in the RIR database for the space. |
| ROA: none | 141.96.6.0/24 | No ROA covers it. Add a ROA for AS25367, maxLength 24. |
| Route object: none | 141.96.6.0/24 | No route object for it. A route object for 141.96.0.0/16 with origin AS25367 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25367 in the RIR database for the space. |
| ROA: none | 141.96.7.0/24 | No ROA covers it. Add a ROA for AS25367, maxLength 24. |
| Route object: none | 141.96.7.0/24 | No route object for it. A route object for 141.96.0.0/16 with origin AS25367 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25367 in the RIR database for the space. |
| ROA: none | 141.96.0.0/16 | No ROA covers it. Add a ROA for AS25367, maxLength 16. |
| ROA: none | 156.133.48.0/20 | No ROA covers it. Add a ROA for AS25367, maxLength 20. |
Route objects not announced
Route objects with origin AS25367 whose prefix no peer sees AS25367 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.133.0.0/16 | RIPE | No ROA |
| 156.133.108.0/22 | 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.