Datto incident
Rocketcyber - eu.rocketcyber.com temporarily inaccessible
Datto experienced a minor incident on September 10, 2026 affecting EU, lasting 13d 5h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Sep 10, 2026, 09:38 AM UTC
The Kaseya R&D Team responded to alerts related to the eu.rocketcyber.com site. The incident lasted for about 30 minutes during which Rocketcyber customers hosted in the EU region were not able to access the product. The issue is now resolved, and we are currently monitoring the health of the service.
- resolved Sep 23, 2026, 03:08 PM UTC
This incident has been resolved.
- postmortem Sep 23, 2026, 03:19 PM UTC
` `**Public RCA: RocketCyber EU Production Service Interruption** **Incident Summary** On September 10, 2026, RocketCyber customers hosted in the EU region experienced service disruptions that prevented access to the RocketCyber console and caused intermittent failures in related platform services. The incident resulted in users receiving error messages when attempting to access the platform. Service was fully restored shortly after the event. We recognize the impact this disruption had on our partners and customers and apologize for the inconvenience. **Impact** **Affected Service:** RocketCyber EU Production Environment` ` **Impact Type:** Service Interruption` ` **Affected Users:** Customers utilizing the EU-hosted RocketCyber platform` ` **Duration:** Approximately 33 minutes for the primary console service disruption, with some dependent services recovering shortly thereafter. During the incident: * Users were unable to reliably access the RocketCyber console. * Some backend services experienced failures when processing requests. * Customers encountered server error messages while attempting to use the platform. **Timeline \(UTC\)** Timeline derived from the incident review. **Root Cause** The incident was caused by abnormal growth of certain database logging tables. Over time, these tables expanded significantly and exceeded operational thresholds. As the database attempted to protect itself and maintain data integrity, write operations became restricted and intensive maintenance processes consumed available database resources. This resource contention affected several dependent services, resulting in widespread application errors. As those services became unavailable, request traffic shifted to other platform components, creating additional load that ultimately impacted console availability. No customer data was lost or compromised during this event. The issue was related to system capacity and database maintenance processes rather than a security incident. **Resolution** The platform recovered as database maintenance activities completed and resource utilization returned to normal operating levels. Following service restoration, engineering teams continued monitoring platform health and performed additional analysis to validate system stability. **Preventive Actions** To reduce the likelihood of similar incidents, RocketCyber has implemented and is pursuing the following improvements: 1. Reduced unnecessary logging activity that contributed to excessive database table growth. 1. Reviewing and enhancing database growth monitoring and alerting to provide earlier visibility into capacity-related risks. 1. Evaluating additional traffic management and rate-limiting mechanisms to help prevent cascading impacts during service degradation events. 1. Developing operational guidance and runbooks to improve response efficiency for similar database-related incidents. **Current Status** All RocketCyber services are operating normally. Engineering teams have implemented immediate corrective measures and continue to strengthen monitoring and resilience controls to prevent recurrence. We appreciate your patience and understanding while this issue was being addressed.