Exalate Status

The system has been under close observation and it has been stable. We will provide a post-mortem to the incident in due course.

The application has been running smoothly without any issues and we do not see any anomalies. A post-mortem will be provided in due course.

This incident has been resolved.

This incident has been resolved.

**Incident:** Exalate Application Unavailability — March 16, 2026 **Duration:** 16:13 CET – 17:09 CET \(approximately 56 minutes\) **Impact:** The Exalate UI was inaccessible during this window. Issue synchronisation was not affected — integrations continued to run normally throughout. No data was lost. **Summary:** On March 16, 2026, the Exalate application became unavailable following a production infrastructure configuration change. A resource allocation adjustment applied to a critical authentication component proved insufficient under production load, causing repeated service interruptions. **Timeline:** * 16:13 CET — Issue reported, investigation initiated * 16:56 CET — Root cause identified, remediation initiated * 17:09 CET — Fix deployed, service restored * 18:13 CET — Full stability confirmed **Root Cause:** A resource limit adjustment deployed without cross-team review under-provisioned a critical authentication component. Under production load, the platform repeatedly terminated the component, rendering the application inaccessible. **Resolution:** Resource limits were corrected, restoring service. A further optimisation was applied during a subsequent scheduled maintenance window following joint engineering review. **Preventive Measures:** * All production infrastructure configuration changes now require joint sign-off from infrastructure and engineering leads before deployment * Resource and capacity parameters validated against production load baselines prior to deployment

**Date:** March 17, 2026 **Duration:** 12:10 CET - 15:00 CET \(2 hours, 50 minutes\) **Impact:** The [exalate.com](http://exalate.com) website was completely inaccessible to all users for the duration of the incident. **Summary:** The hosting environment experienced resource exhaustion triggered by a sudden surge in web traffic. This was further exacerbated by a malfunctioning security plugin. **Timeline:** 12:10 CET: Incident start \(resource exhaustion begins\) 12:28 CET: Issue detected 14:40 CET: Root cause identified 15:00 CET: Service fully restored **Root Cause:** A spike in unique visitors has led to resource depletion on the hosting server. During the investigation, it was discovered that an installed security plugin was behaving inefficiently under high load, significantly compounding the CPU and memory usage, preventing the server from recovering. **Resolution:** Identified and blocked specific IP addresses responsible for an anomalous volume of requests. Deactivated and removed the problematic security plugin. Implemented an alternative solution to handle the plugin's core functionality without the performance overhead. **Preventive Measures:** Investigate and implement automated rate-limiting and IP blocking solutions \(e.g., WAF rules\) to handle traffic spikes.

**Incident:** Exalate Cloud Service Disruption - March 9, 2026 **Duration:** 07:30 CET – 08:10 CET \(approximately 40 minutes\) **Impact:** Some Exalate Cloud nodes experienced temporary service disruption. Database write operations were briefly affected. Issue synchronisation resumed automatically once the issue was resolved. No data was lost. **Summary:** On March 9, 2026, the primary database instance serving part of the Exalate Cloud infrastructure reached full storage capacity. This prevented the database from processing write operations, temporarily impacting node availability. **Timeline:** * 07:30 CET - Issue detected, investigation initiated * 08:05 CET - Storage expanded, database operations resumed * 08:10 CET - Fix verified, nodes confirmed operational * 10:00 CET - Full stability confirmed after extended monitoring **Root Cause:** The primary database storage volume gradually reached full capacity under normal operational growth. Proactive storage monitoring did not fire in time. **Resolution:** Database storage was expanded and the service returned to full operation automatically. Additional alerting configured.

**Incident:** Exalate Application Unavailability — January 23, 2026 **Duration:** 10:59 CET – 11:18 CET \(approximately 19 minutes\) **Impact:** The Exalate UI was inaccessible during this window. Issue synchronisation was not affected — integrations continued to run normally throughout. No data was lost. **Summary:** On January 23, 2026, our monitoring detected a service outage affecting the Exalate application. The root cause was a deployment configuration change that unintentionally removed an active compute resource from the production environment. **Timeline:** * 10:59 CET — Issue detected, investigation initiated * 11:18 CET — Fix deployed, service restored * 13:18 CET — Full stability confirmed **Root Cause:** A deployment configuration change targeted the wrong resource section, resulting in an active production compute resource being removed and the application becoming inaccessible. **Resolution:** The affected resource was recreated and all services returned to full operation with no data loss. **Preventive Measures:** * Infrastructure-as-code changes must be validated in a non-production environment before production deployment * Peer review steps introduced to verify configuration targets prior to execution

**Incident: Service Outage - December 12, 2025** **Duration:** 16:35 CET - 03:01 CET \(approximately 10 hours\) **Impact:** A significant number of Exalate Cloud nodes experienced service unavailability, resulting in temporary disruption to data synchronization services. No data was lost during this incident. **Summary:** On December 12, 2025, our infrastructure monitoring detected a service outage affecting Exalate Cloud customers on our production clusters. The root cause was identified as a storage system failure triggered by network latency on a legacy infrastructure component, which caused storage connectivity issues for customer workloads. **Timeline:** * 16:35 CET - Issue detected by monitoring systems * 17:31 CET - Root cause identified, restoration initiated * 21:20 CET - Majority of nodes restored to service * 03:01 CET - Full service restoration confirmed **Root Cause:** A storage management component became unresponsive due to elevated network latency caused by a legacy networking layer. This resulted in storage disconnection for customer workloads. **Resolution:** The storage system was restored, all affected workloads were rescheduled, and the external dependency was updated to a supported version. All nodes were returned to full operation with no data loss. **Preventive Measures:** * Deploying patches to address the storage component stability issue * Accelerating migration away from the legacy networking layer to modern infrastructure * Implementing internal mirroring of critical external dependencies to eliminate reliance on third-party availability * Enhancing operational safeguards for infrastructure management procedures We sincerely apologize for the disruption this incident caused. Our team remains committed to improving the reliability and resilience of the Exalate Cloud platform.

**Incident: Service Degradation - November 27, 2025** **Duration:** 11:26 CET - 21:37 CET \(~10 hours\) **Impact:** Approximately 700 Exalate Cloud nodes experienced intermittent connectivity issues, resulting in temporary disruption to data synchronization services. No data was lost during this incident. **Summary:** On November 27, 2025, our infrastructure monitoring detected service degradation affecting a subset of Exalate Cloud customers. The root cause was identified as storage I/O contention on the underlying database infrastructure, which caused the primary database to become unresponsive intermittently. **Timeline:** * 11:26 CET - Issue detected by monitoring systems * 11:30 CET - Engineering team began investigation * 15:30 CET - Initial mitigation applied \(infrastructure scaling\) * 18:30 CET - Root cause identified and permanent remediation initiated * 21:37 CET - Full service restoration confirmed **Root Cause:** Database storage was experiencing resource contention due to shared infrastructure components, causing elevated I/O latency. This triggered automated health checks to restart the database service repeatedly, compounding the connectivity issues. **Resolution:** The database was migrated to dedicated storage resources and allocated additional compute capacity. All affected nodes were restored to full operation with no data loss. **Preventive Measures:** * Implementing enhanced storage latency monitoring and alerting * Reviewing infrastructure health check configurations for database workloads * Auditing storage allocation across all database clusters to prevent similar contention We apologize for any inconvenience this incident may have caused. Our team remains committed to maintaining the reliability and performance of the Exalate Cloud platform.

Maintenance will begin as scheduled in 60 minutes.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.