Root Cause Analysis – KaseyaOne Frontend Availability Incident

Summary

Between 2026-07-16 01:00 UTC and 2026-07-16 01:25 UTC, KaseyaOne customers were unable to access the KaseyaOne web application. During this period, the KaseyaOne frontend became unavailable, preventing users from accessing the login page, the associated web experience, and accessing the Support Helpdesk from KaseyaOne.

The issue primarily affected customers in the APAC region due to the timing of the incident, although the service disruption had global scope.

Root Cause

A planned infrastructure update caused a previously undetected configuration discrepancy within a customer-facing web delivery component to be applied in production. This resulted in requests being directed to an incorrect backend endpoint, causing the KaseyaOne frontend to become unavailable until the configuration was corrected and fully propagated across the platform.

Incident Timeline

Identified: 2026-07-16 01:00 UTC

Root Cause Identified: 2026-07-16 01:10 UTC

Corrective Configuration Deployment: 2026-07-16 01:30 UTC

Confirmation of Resolution: 2026-07-16 01:50 UTC

Preventative Measures

To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps:

Enhancements to Infrastructure Governance

• Reinforce the use of Infrastructure as Code (IaC) as the authoritative source for production infrastructure changes.
• Eliminate manual production configuration updates outside approved deployment processes.
• Establish automated controls to ensure production configurations remain aligned with approved infrastructure definitions.

Enhancements to Release Management Practices

• Require enhanced review procedures for infrastructure platform and provider upgrades that may trigger configuration reconciliation.
• Implement pre-deployment validation of critical production endpoints before infrastructure changes are applied.
• Strengthen change review requirements for production edge-routing and traffic-management components.

Enhancements to Infrastructure Resiliency

• Implement automated configuration drift detection and reporting to identify discrepancies between deployed infrastructure and source-controlled configurations.
• Add regular validation of externally facing routing and origin configurations.
• Improve recovery validation procedures to account for platform propagation delays and ensure service restoration is fully confirmed before incident closure.

Enhancements to Incident Management and Response

• Introduce additional deployment validation procedures for infrastructure changes affecting customer-facing services.
• Expand post-deployment verification activities to include end-to-end application availability testing.
• Continue refining incident response processes to further accelerate restoration activities.