Network · data from 2026-11-12
AS25428 Colruyt Group Services
Registry name: INFOCO-COLRUYT-AS Colruyt Group NV, BE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25428, 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.231.108.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 91.231.109.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.16.240.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 195.26.2.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 195.26.3.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.138.171.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a01:89c0::/32 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
AS25428'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 9 are in fix.csv.
- ROA: none7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.231.108.0/24 | No ROA covers it. Add a ROA for AS25428, maxLength 24. |
| ROA: none | 91.231.109.0/24 | No ROA covers it. Add a ROA for AS25428, maxLength 24. |
| ROA: none | 185.16.240.0/22 | No ROA covers it. Add a ROA for AS25428, maxLength 22. |
| ROA: none | 195.26.2.0/24 | No ROA covers it. Add a ROA for AS25428, maxLength 24. |
| ROA: none | 195.26.3.0/24 | No ROA covers it. Add a ROA for AS25428, maxLength 24. |
| ROA: none | 45.138.171.0/24 | No ROA covers it. Add a ROA for AS25428, maxLength 24. |
| ROA: none | 2a01:89c0::/32 | No ROA covers it. Add a ROA for AS25428, maxLength 32. |
Route objects not announced
Route objects with origin AS25428 whose prefix no peer sees AS25428 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.138.168.0/23 | RIPE | No ROA |
| 45.138.170.0/24 | 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.