bgpreport

Network · data from 2026-11-12

AS205233 AS_KBCGROUP_CSOBCZ KBC GLOBAL SERVICES NV

Registry name: AS_KBCGROUP_CSOBCZ KBC GLOBAL SERVICES NV, BE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205233, 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.

193.245.32.0/21 No ROA Other origin only 673 100% 67
193.245.32.0/22 No ROA None 671 100% 67
193.245.32.0/23 No ROA None 671 100% 67
193.245.34.0/23 No ROA None 671 100% 67
193.245.36.0/22 No ROA None 671 100% 67
193.245.36.0/23 No ROA None 671 100% 67
193.245.38.0/23 No ROA None 671 100% 67

AS-SET

AS205233 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 22 are in fix.csv.

  • ROA: none7
  • Route object: none7
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none193.245.32.0/21No ROA covers it. Add a ROA for AS205233, maxLength 21.673 of 673
Route object: none193.245.32.0/21Route objects for it name AS5588, AS5610. Add a route object with origin AS205233 in the RIR database for the space.673 of 673
ROA: none193.245.32.0/22No ROA covers it. Add a ROA for AS205233, maxLength 22.671 of 673
Route object: none193.245.32.0/22No route object for it. Add a route object with origin AS205233 in the RIR database for the space.671 of 673
ROA: none193.245.32.0/23No ROA covers it. Add a ROA for AS205233, maxLength 23.671 of 673
Route object: none193.245.32.0/23No route object for it. Add a route object with origin AS205233 in the RIR database for the space.671 of 673
ROA: none193.245.34.0/23No ROA covers it. Add a ROA for AS205233, maxLength 23.671 of 673
Route object: none193.245.34.0/23No route object for it. Add a route object with origin AS205233 in the RIR database for the space.671 of 673
ROA: none193.245.36.0/22No ROA covers it. Add a ROA for AS205233, maxLength 22.671 of 673
Route object: none193.245.36.0/22No route object for it. Add a route object with origin AS205233 in the RIR database for the space.671 of 673
ROA: none193.245.36.0/23No ROA covers it. Add a ROA for AS205233, maxLength 23.671 of 673
Route object: none193.245.36.0/23No route object for it. Add a route object with origin AS205233 in the RIR database for the space.671 of 673
ROA: none193.245.38.0/23No ROA covers it. Add a ROA for AS205233, maxLength 23.671 of 673
Route object: none193.245.38.0/23No route object for it. Add a route object with origin AS205233 in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS205233 whose prefix no peer sees AS205233 announce. Many are kept on purpose (backup routes, space announced only in some places).

193.245.32.0/24RIPENo ROA
193.245.33.0/24RIPENo ROA
193.245.34.0/24RIPENo ROA
193.245.35.0/24RIPENo ROA
193.245.36.0/24RIPENo ROA
193.245.37.0/24RIPENo ROA
193.245.38.0/24RIPENo ROA
193.245.39.0/24RIPENo 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.