Exalate Outage History

Exalate is up right now

Exalate had 13 outages in the last 2 years totaling 1049h 7m of downtime — averaging 0.5 incidents per month.

There were 13 Exalate outages since August 29, 2025 totaling 1049h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.exalate.com

Minor May 4, 2026

Some exalate cloud nodes unavailable

Detected by Pingoru
May 04, 2026, 01:24 PM UTC
Resolved
May 04, 2026, 09:28 PM UTC
Duration
8h 3m
Affected: connect.exalate.net (mapper)Hosting platformconnect.exalate.cloud
Timeline · 7 updates
  1. investigating May 04, 2026, 01:24 PM UTC

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

  2. investigating May 04, 2026, 01:41 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 04, 2026, 01:42 PM UTC

    We are continuing to investigate this issue.

  4. identified May 04, 2026, 02:50 PM UTC

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

  5. identified May 04, 2026, 03:53 PM UTC

    affected nodes are recovering while our cloud team continues to work on the issue.

  6. monitoring May 04, 2026, 06:50 PM UTC

    All nodes are operational, our cloud team continues to review the affected cluster and work on its maintenance.

  7. resolved May 04, 2026, 09:28 PM UTC

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

Read the full incident report →

Major April 15, 2026

Exalate.app Not loading workspaces

Detected by Pingoru
Apr 15, 2026, 09:03 AM UTC
Resolved
Apr 15, 2026, 12:16 PM UTC
Duration
3h 13m
Affected: Exalate.app
Timeline · 4 updates
  1. investigating Apr 15, 2026, 09:03 AM UTC

    We are currently investigating an issue where the workspaces page is not loading. The sync is not affected, only the UI of New Exalate is not loading.

  2. identified Apr 15, 2026, 09:04 AM UTC

    We have identified the root cause of the issue and are currently working on a fix.

  3. monitoring Apr 15, 2026, 10:16 AM UTC

    The technical issues have been fully resolved and the app is up and running now. We are closely monitoring the situation.

  4. resolved Apr 15, 2026, 12:16 PM UTC

    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.

Read the full incident report →

Major April 2, 2026

Some Exalate Nodes are currently unreachable

Detected by Pingoru
Apr 02, 2026, 03:41 PM UTC
Resolved
Apr 02, 2026, 09:26 PM UTC
Duration
5h 44m
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceFreshdeskFreshservice
Timeline · 5 updates
  1. investigating Apr 02, 2026, 03:41 PM UTC

    We are investigating some Exalate nodes being unavailable. We will be providing an update shortly on the investigation. Next update within 2 hours - or as soon as we have any relevant updates

  2. identified Apr 02, 2026, 04:37 PM UTC

    The issue was identified and we are currently working on restoring the nodes as soon as possible. Next update within 2 hours or as soon as we have any relevant updates

  3. identified Apr 02, 2026, 06:25 PM UTC

    We continue with the restoration efforts. Some nodes are already available. Next update will be within 2 hours or as soon as we have any relevant update.

  4. monitoring Apr 02, 2026, 07:18 PM UTC

    All nodes have been successfully restored. Our team is closely monitoring the system to ensure continued stability.

  5. resolved Apr 02, 2026, 09:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 12, 2025

Exalate nodes unrachable

Detected by Pingoru
Dec 12, 2025, 04:15 PM UTC
Resolved
Dec 13, 2025, 04:26 AM UTC
Duration
12h 10m
Affected: connect.exalate.net (mapper)Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceFreshdeskFreshserviceconnect.exalate.cloudExalate.app
Timeline · 11 updates

Read the full incident report →

Minor November 20, 2025

SyncRoom website and Community not loading.

Detected by Pingoru
Nov 20, 2025, 09:43 AM UTC
Resolved
Nov 20, 2025, 11:23 AM UTC
Duration
1h 39m
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceFreshdeskFreshserviceExalate Support
Timeline · 4 updates
  1. identified Nov 20, 2025, 09:43 AM UTC

    We have identified an issue when trying to access the SyncRoom page, caused by a significant increase in DNS traffic originating from an external problem between Hostinger and Cloudflare. This external issue is currently impacting our service and is preventing the SyncRoom page and the community from loading Important Note: This issue does not affect the core Exalate functionality. Synchronization is continuing to work as expected. We are actively working to resolve this and will provide an update within the next two hours. Thank you for your patience.

  2. monitoring Nov 20, 2025, 10:29 AM UTC

    A fix has been implemented by Hostinger and the services have been restored (Exalate community and SyncRoom) We will continue to monitor the results.

  3. resolved Nov 20, 2025, 11:23 AM UTC

    This incident has been resolved.

  4. postmortem Apr 01, 2026, 04:08 AM UTC

    timeout

Read the full incident report →

Minor October 3, 2025

Jira Cloud: Script Configuration Update Available

Detected by Pingoru
Oct 03, 2025, 09:43 AM UTC
Resolved
Nov 05, 2025, 02:17 PM UTC
Duration
33d 4h
Affected: Synchronisation node
Timeline · 3 updates
  1. monitoring Oct 03, 2025, 09:43 AM UTC

    We've released a configuration update for Jira Cloud connections running version 5.28.5. Who is affected: Customers using external script repositories in their Jira Cloud connections may experience script-related errors after upgrading to 5.28.5. Resolution: If you're experiencing issues with your scripts, please contact our support team at [email protected] - we'll assist you with a quick configuration update. Status: We're actively monitoring and reaching out to affected customers.

  2. resolved Nov 05, 2025, 02:17 PM UTC

    This incident has been resolved.

  3. postmortem Apr 01, 2026, 04:09 AM UTC

    timeout

Read the full incident report →

Major September 24, 2025

Some Exalate nodes unavailable

Detected by Pingoru
Sep 24, 2025, 10:56 AM UTC
Resolved
Sep 25, 2025, 02:21 PM UTC
Duration
1d 3h
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceFreshdeskFreshservice
Timeline · 17 updates

Read the full incident report →