bgpreport

Network · data from 2026-11-12

AS56619 KSB Safety Integrated Systems Ltd

Registry name: KSB Safety Integrated Systems Ltd, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56619, 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.232.201.0/24 No ROA RIR databaseRIPE 673 100% 66
193.232.199.0/24 No ROA RIR databaseRIPE 5 1%low visibility 6
193.232.198.0/24 No ROA RIR databaseRIPE 4 1%low visibility 3
62.89.215.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS56619 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 8 are in fix.csv.

  • ROA: none3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none193.232.201.0/24No ROA covers it. Add a ROA for AS56619, maxLength 24.673 of 673
ROA: none193.232.199.0/24No ROA covers it. Add a ROA for AS56619, maxLength 24.5 of 673
ROA: none193.232.198.0/24No ROA covers it. Add a ROA for AS56619, maxLength 24.4 of 673

Route objects not announced

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

62.89.203.0/24RIPEValid
79.98.252.0/24RIPEValid
79.98.253.0/24RIPEValid
90.188.199.0/24RIPEValid
178.34.101.0/24RIPEInvalid: origin

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.