bgpreport

Network · data from 2026-11-12

AS9166 CEGEKA-HASSELT Cegeka Groep NV

Registry name: CEGEKA-HASSELT Cegeka Groep NV, BE · not in PeeringDB

14IPv4 routes 42.9% RPKI valid · 100.0% with a route object
9IPv6 routes 100.0% RPKI valid · 44.4% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 5 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS9166, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9166, 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.
194.0.205.0/24 No ROA RIR databaseRADB, RIPE 671 100% 67
194.53.130.0/23 No ROA RIR databaseRADB, RIPE 671 100% 67
194.53.132.0/23 No ROA RIR databaseRADB, RIPE 671 100% 67
194.53.134.0/24 No ROA RIR databaseRADB, RIPE 671 100% 67
194.53.130.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
194.53.131.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
194.53.132.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
194.53.133.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
2a02:2399:103::/48 Valid None 605 95% 67
2a02:2398:1::/48 Valid None 604 95% 67
2a02:2398:2::/48 Valid None 604 95% 67
2a02:2399:101::/48 Valid None 604 95% 67
2a02:2399:102::/48 Valid None 604 95% 67
62.233.0.0/20 Valid RIR databaseRADB, RIPE 671 100% 67
212.113.64.0/19 Valid RIR databaseRADB, RIPE 671 100% 67
2a02:2398::/48 Valid RIR databaseRIPE 634 100% 67
2a02:2398:100::/40 Valid RIR databaseRIPE 634 100% 67
2a02:2398:200::/40 Valid RIR databaseRIPE 634 100% 67
2a02:239c::/48 Valid RIR databaseRIPE 634 100% 67
62.233.0.0/21 Valid RIR databaseRIPE 2 0%low visibility 2
62.233.8.0/21 Valid RIR databaseRIPE 2 0%low visibility 2
212.113.64.0/20 Valid RIR databaseRIPE 2 0%low visibility 2
212.113.80.0/20 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS9166 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 13 are in fix.csv.

  • ROA: none8
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none194.0.205.0/24No ROA covers it. Add a ROA for AS9166, maxLength 24.671 of 673
ROA: none194.53.130.0/23No ROA covers it. Add a ROA for AS9166, maxLength 23.671 of 673
ROA: none194.53.132.0/23No ROA covers it. Add a ROA for AS9166, maxLength 23.671 of 673
ROA: none194.53.134.0/24No ROA covers it. Add a ROA for AS9166, maxLength 24.671 of 673
ROA: none194.53.130.0/24No ROA covers it. Add a ROA for AS9166, maxLength 24.2 of 673
ROA: none194.53.131.0/24No ROA covers it. Add a ROA for AS9166, maxLength 24.2 of 673
ROA: none194.53.132.0/24No ROA covers it. Add a ROA for AS9166, maxLength 24.2 of 673
ROA: none194.53.133.0/24No ROA covers it. Add a ROA for AS9166, maxLength 24.2 of 673
Route object: none2a02:2399:103::/48No route object for it. Add a route object with origin AS9166 in the RIR database for the space.605 of 636
Route object: none2a02:2398:1::/48No route object for it. Add a route object with origin AS9166 in the RIR database for the space.604 of 636
Route object: none2a02:2398:2::/48No route object for it. Add a route object with origin AS9166 in the RIR database for the space.604 of 636
Route object: none2a02:2399:101::/48No route object for it. Add a route object with origin AS9166 in the RIR database for the space.604 of 636
Route object: none2a02:2399:102::/48No route object for it. Add a route object with origin AS9166 in the RIR database for the space.604 of 636

Route objects not announced

Every route object with origin AS9166 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.