No impact incident

Kaseya: BMS - EMEA - Pages fail to load with Error - "Something went wrong! Please contact the system admin."

Nov 2, 2026, 22:15 UTC
started
14:30 UTC
resolved
—
duration

Current status of Kaseya: Under maintenance — live Kaseya status

Timeline

  1. Nov 2, 2026, 14:30 UTC
    resolved
    The Kaseya Engineering Team resolved a problem where pages were failing to load with an error message: "Something went wrong! Please contact the system admin." If you are still experiencing this issue or need any assistance, please contact our support team for assistance through our helpdesk at: https://helpdesk.kaseya.com/hc/en-gb#/contact To receive notifications about future maintenance events and service updates, subscribe to https://status.kaseya.com/
  2. Nov 3, 2026, 17:45 UTC
    postmortem
    # Summary Between 2026-11-02 14:13 UTC and 2026-11-02 14:51 UTC, some BMS EMEA customers experienced intermittent application errors when attempting to log in and perform certain actions, including ticket-related workflows. Affected users received an error message indicating that the requested action could not be completed. # Root Cause An application-level issue resulted in intermittent processing failures that affected login and ticketrelated workflows for some BMS EMEA customers. The application recovered successfully after a restart restored normal operation. ## Incident Timeline * Identified: 2026-11-02 14:13 UTC * Resolved: 2026-11-02 14:51 UTC # Preventative Measures To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. ## Enhancements to Monitoring and Alerting * Review existing monitoring coverage for application availability and application error conditions, with particular focus on login and ticket-related workflows. ## Enhancements to Incident Response and Recovery * Review and update operational recovery procedures for intermittent application failures. * Ensure recovery validation includes verification of critical workflows, including login functionality and ticket-related operations, following remediation activities.

Updates as published by Kaseya (original).

Other services with incidents at the same time

This was part of a wider event: 13 services reported incidents within the hour.

More Kaseya incidents