Some exalate cloud nodes unavailable

Update timeline

1. investigating Mar 09, 2026, 06:59 AM UTC

   We have reports of some Exlate cloud nodes being unavailable. Our team is currently investigating the issue.

2. identified Mar 09, 2026, 07:11 AM UTC

   Our cloud team has identified the root cause and is actively engaged in rectifying it.

3. monitoring Mar 09, 2026, 07:20 AM UTC

   The issue has been fully rectified and all nodes are fully restored. We are closely monitoring the situation.

4. resolved Mar 09, 2026, 09:00 AM UTC

   After close monitoring, we consider the issue fully resolved. An RCA would be published here in due course.

5. postmortem Apr 01, 2026, 03:39 AM UTC

   **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.