Exalate incident

Exalate App unavailable

Minor Resolved View vendor source →
Started
Mar 16, 2026, 03:13 PM UTC
Resolved
Mar 16, 2026, 05:13 PM UTC
Duration
2h
Detected by Pingoru
Mar 16, 2026, 03:13 PM UTC

Affected components

Exalate.app

Update timeline

  1. investigating Mar 16, 2026, 03:13 PM UTC

    We are investigating reports by some users that the Exalate app is not available right now.

  2. identified Mar 16, 2026, 03:56 PM UTC

    We have identified the problem and the team is working to rectify this. We will provide an update of progress shortly.

  3. monitoring Mar 16, 2026, 04:09 PM UTC

    The services are fully functional again. We are very closely monitoring the situation.

  4. resolved Mar 16, 2026, 05:13 PM UTC

    All systems are functional. We will be providing a post-mortem of the incident here in due course.

  5. postmortem Mar 31, 2026, 09:44 AM UTC

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

Looking to track Exalate downtime and outages?

Pingoru polls Exalate's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Exalate reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Exalate alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Exalate for free

5 free monitors · No credit card required