Exalate Outage History

Exalate is up right now

Exalate had 16 outages in the last 2 years totaling 902h 44m of downtime — averaging 0.7 incidents per month.

There were 16 Exalate outages since October 3, 2025 totaling 902h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.exalate.com

Notice August 27, 2026

Atlassian has an active incident that might be affecting your connections

Detected by Pingoru
Aug 27, 2026, 04:36 AM UTC
Resolved
Aug 27, 2026, 05:27 AM UTC
Duration
51m
Affected: Synchronisation node
Timeline · 5 updates
  1. investigating Aug 27, 2026, 04:36 AM UTC

    Atlassian is experiencing an issue with Jira and other systems currently - details here: https://status.atlassian.com/ This may affect your Exalate connections if you are connecting to a Jira instance.

  2. identified Aug 27, 2026, 04:44 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 27, 2026, 05:09 AM UTC

    Atlassian have put a fix in place to resolve the issue. Your synchronization should already be back to normal, but please reach out to support in case of any issues.

  4. resolved Aug 27, 2026, 05:27 AM UTC

    All Atlassian systems are back to normal, and the synchronization is working as expected. In case of any issues with your sync, please create a support ticket and we will be happy to assist.

  5. postmortem Sep 08, 2026, 05:41 AM UTC

    N/A

Read the full incident report →

Minor July 24, 2026

App name change/proxy user on Atlassian Jira Cloud

Detected by Pingoru
Jul 24, 2026, 06:12 AM UTC
Resolved
Jul 24, 2026, 04:33 PM UTC
Duration
10h 20m
Affected: Synchronisation node
Timeline · 5 updates
  1. identified Jul 24, 2026, 06:12 AM UTC

    Following up on an unadverted change in the application name which causes the proxy user to be shown with the full name of the application instead of just "Exalate". This is already notified to Atlassian and we are awaiting the required action on their end to revert the change. Impact: Updates made by Exalate will display "Exalate Classic Connector for Jira (Two-way Sync)" as the user making the change.

  2. identified Jul 24, 2026, 09:15 AM UTC

    We continue to investigate the best approach to solve this issue with the help of Atlassian support.

  3. identified Jul 24, 2026, 12:39 PM UTC

    We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible.

  4. identified Jul 24, 2026, 03:47 PM UTC

    We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible. We will be providing the next update within 6 hours or as soon as we have any relevant information.

  5. resolved Jul 24, 2026, 04:33 PM UTC

    The proxy user name was reverted back to Exalate. We are considering the incident as resolved.

Read the full incident report →

Minor July 16, 2026

JiraCloud nodes experiencing some instablility

Detected by Pingoru
Jul 16, 2026, 11:28 AM UTC
Resolved
Jul 16, 2026, 05:18 PM UTC
Duration
5h 50m
Affected: Synchronisation node
Timeline · 6 updates
  1. investigating Jul 16, 2026, 11:28 AM UTC

    Some Jira Cloud nodes are experiencing instability over the past 30mins. The problem is limited and only affects some customers. We will be providing an update shortly.

  2. identified Jul 16, 2026, 12:03 PM UTC

    We will be actioning a change on Exalate Cloud to improve stability. The impact on your node will be that limited to a restart with the node being unavailable for a couple of min. The inconvenience is regretted.

  3. identified Jul 16, 2026, 01:38 PM UTC

    The rolling restart of the nodes is in progress. You will experience a brief restart on JCloud nodes. We will keep you posted with our progress.

  4. identified Jul 16, 2026, 03:15 PM UTC

    The restart is still in progress and is going without any issues. We will update you as soon as it is completed.

  5. monitoring Jul 16, 2026, 03:57 PM UTC

    All nodes are back to normal operation. We continue to monitor the situation closely.

  6. resolved Jul 16, 2026, 05:18 PM UTC

    After close monitoring, the issue is considered as fully resolved. We will be posting a RCA here in due course.

Read the full incident report →

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