Exalate Status Page

Jul 13, 2026

We've received multiple reports of syncs looping after update to the new Jira Cloud forge app. Our initial investigation leads us to believe this is happening due to the change in the Proxy User account. We are actively working on determining the root cause and applying a fix.

Jun 23, 2026 · resolved Jun 23

**Duration:** 11:10 CEST - 11:26 CEST \(approximately 16 minutes\). Full stability confirmed at 14:47 CEST. **Impact:** The Exalate.app connection and dashboard pages were inaccessible during this window. Issue synchronisation was not affected - integrations continued to run normally throughout. No data was lost. **Summary:** On June 23, 2026, the Exalate.app interface became inaccessible after an internal authentication component failed to connect to its database. The failure was caused by a credential mismatch introduced during a production deployment. **Timeline:** * 11:10 CEST - Issue detected, investigation initiated * 11:26 CEST - Fix deployed, service restored * 14:47 CEST - Full stability confirmed **Root Cause:** During a production deployment on June 19, a database credential was configured independently in two systems. A subtle mismatch was introduced during a subsequent configuration update. The mismatch remained latent because the application maintained existing database connections. A routine GKE maintenance event on June 23 recycled the application, forcing new connections that exposed the mismatch. **Resolution:** The database credential was aligned and the application was restarted. Service returned to full operation with no data loss. **Preventive Measures:** * Post-deployment authentication verification checks have been added to the deployment runbook * Alerting for application database connectivity failures has been implemented * The credential configuration process is being consolidated to eliminate the dual-system mismatch risk We apologize for the disruption. We remain committed to the reliability of the Exalate platform.

May 4, 2026 · resolved May 4

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

Apr 15, 2026 · resolved Apr 15

**Incident:** Exalate.app Not Loading Workspaces - April 15, 2026 **Duration:** 11:03 CEST – 12:16 CEST \(approximately 73 minutes\). **Impact:** The Exalate.app UI was inaccessible during this window. Issue synchronisation was not affected. No data was lost. **Summary:** On April 15, 2026, the Exalate.app interface became inaccessible following a planned infrastructure credential update. A secondary configuration dependency was not updated as part of the change, preventing the application from connecting to its database. **Timeline:** * 11:03 CEST - Issue detected, investigation initiated * 11:04 CEST - Root cause identified * 12:16 CEST - Fix deployed, service restored **Root Cause:** A configuration dependency missed during a credential update left the application unable to authenticate to its database. This was related to the April 6 incident; the additional dependency has now been identified and incorporated into the rotation procedure. **Resolution:** The affected configuration was regenerated and the application was restarted. Service returned to full operation with no data loss. **Preventive Measures:** * All credential dependencies have been fully mapped and the rotation procedure updated to cover them as a single atomic operation We apologize for the disruption. We remain committed to the reliability of the Exalate platform.

Apr 6, 2026 · resolved Apr 6

**Incident:** Exalate.app Not Loading Workspaces - April 6, 2026 **Duration:** 13:07 CEST - 13:28 CEST \(approximately 21 minutes\). **Impact:** The Exalate.app UI was inaccessible during this window. Issue synchronisation was not affected - integrations continued to run normally throughout. No data was lost. **Summary:** On April 6, 2026, the Exalate.app interface became inaccessible after an infrastructure credential was rotated as part of a planned security improvement programme. The component responsible for database connectivity caches credentials at startup and does not reload them automatically. The previous credential was removed before the component had been restarted to pick up the new one, causing authentication failures. **Timeline:** * 13:07 CEST - Issue detected, investigation initiated * 13:28 CEST - Fix deployed, service restored **Root Cause:** A credential rotation completed out of sequence - the old credential was removed before the consuming component had been restarted with the new one. **Resolution:** The affected components were restarted with the correct credentials. Service returned to full operation with no data loss. **Preventive Measures:** * A credential rotation procedure has been established enforcing a mandatory sequence: update, restart consumers, verify, then remove old credentials * Direct monitoring for database connectivity authentication failures is being implemented * Migration to automated credential management that eliminates manual rotation for this workload is underway We apologize for the disruption. We remain committed to the reliability of the Exalate platform.

Is Exalate down right now?

Yes — Exalate is reporting a minor incident as of Jul 13, 11:42 PM UTC.

What is Exalate's current status?

Exalate: Partially Degraded Service. Alert24 checks Exalate's status page continuously and can notify you the moment it changes.

How do I get alerted when Exalate goes down?

Alert24 monitors Exalate and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.