Exalate.app is not loading the connections.
Affected: Exalate.app
Exalate Outage History
Exalate is up right nowExalate had 21 outages in the last 2 years totaling 1518h 23m of downtime — averaging 0.9 incidents per month.
There were 21 Exalate outages since August 28, 2024 totaling 1518h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some exalate cloud nodes unavailable
Affected: connect.exalate.net (mapper)Hosting platformconnect.exalate.cloud
Timeline · 7 updates
- 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.
- investigating May 04, 2026, 01:41 PM UTC
We are continuing to investigate this issue.
- investigating May 04, 2026, 01:42 PM UTC
We are continuing to investigate this issue.
- identified May 04, 2026, 02:50 PM UTC
Our cloud team has identified the root cause and is actively engaged in rectifying it.
- identified May 04, 2026, 03:53 PM UTC
affected nodes are recovering while our cloud team continues to work on the issue.
- 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.
- 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.
Exalate.app Not loading workspaces
Affected: Exalate.app
Timeline · 5 updates
Some Exalate Nodes are currently unreachable
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceFreshdeskFreshservice
Timeline · 5 updates
- 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
- 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
- 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.
- 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.
- resolved Apr 02, 2026, 09:26 PM UTC
This incident has been resolved.
Exalate App unavailable
Affected: Exalate.app
Timeline · 5 updates
Exalate Website Unavailable
Affected: Exalate.com website
Timeline · 5 updates
Exalate.app page is not loading.
Affected: Exalate.app
Timeline · 4 updates
Exalate nodes unrachable
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
Some Exalate nodes are unavailable
Affected: Hosting platform
Timeline · 9 updates
SyncRoom website and Community not loading.
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceFreshdeskFreshserviceExalate Support
Timeline · 4 updates
- 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.
- 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.
- resolved Nov 20, 2025, 11:23 AM UTC
This incident has been resolved.
- postmortem Apr 01, 2026, 04:08 AM UTC
timeout
Some Exalate nodes down (specially on Jira Cloud)
Affected: Synchronisation node
Timeline · 4 updates
Jira Cloud: Script Configuration Update Available
Affected: Synchronisation node
Timeline · 3 updates
- 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.
- resolved Nov 05, 2025, 02:17 PM UTC
This incident has been resolved.
- postmortem Apr 01, 2026, 04:09 AM UTC
timeout
Some Exalate nodes unavailable
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceFreshdeskFreshservice
Timeline · 17 updates
Jira Cloud IssueLinks being Removed
Affected: Synchronisation node
Timeline · 6 updates
Connection error on Cloud instance
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceHosting platform
Timeline · 8 updates
- investigating Apr 08, 2025, 12:58 PM UTC
We are currently tracking an issue where cloud nodes are getting errors communication with the destination side and blocking the synchronization. Resolving the errors will make the synchronization work again but another error could reappear.
- investigating Apr 08, 2025, 01:43 PM UTC
As part of our continued investigation into the recent service disruption, a number of nodes have been identified as temporarily unreachable. Our engineering teams are prioritizing node recovery and service restoration.
- identified Apr 08, 2025, 03:29 PM UTC
We have successfully identified the root cause of the recent node downtime and communication disruptions. A mitigation is now being deployed, and we will maintain continuous monitoring of the system.
- identified Apr 08, 2025, 03:36 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 08, 2025, 07:03 PM UTC
We've successfully restored 90% of the nodes, and they're now fully operational. We're actively working on the remaining systems and closely monitoring performance.
- monitoring Apr 09, 2025, 07:42 AM UTC
All Cloud nodes are working as expected. We will continue to monitor the situation.
- resolved Apr 09, 2025, 03:32 PM UTC
All affected services are now back online, and no further impacts have been observed. We apologize for any inconvenience this may have caused.
- postmortem Apr 01, 2026, 04:10 AM UTC
timeout
Some nodes are down due to cluster issue
Affected: Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForce
Timeline · 10 updates
www.exalate.com is not accessible
Affected: Exalate.com website
Timeline · 5 updates
- investigating Jan 16, 2025, 03:51 PM UTC
The website is currently not available and we are investigating with the hoster the reason why.
- monitoring Jan 16, 2025, 04:14 PM UTC
A fix has been rolled out, and we are monitoring.
- monitoring Jan 16, 2025, 04:14 PM UTC
We are continuing to monitor for any further issues.
- resolved Jan 17, 2025, 09:40 AM UTC
The incident is resolved.
- postmortem Apr 01, 2026, 04:11 AM UTC
timeout
Salesforce nodes down due to a major service interruption at Salesforce
Affected: Exalate for SalesForce
Timeline · 5 updates
- identified Nov 13, 2024, 08:44 AM UTC
Integration services to Salesforce are affected by a major service interruption on the Salesforce side Check here - https://status.salesforce.com/products/Salesforce_Services We are monitoring the situation and will be handling it as new information from Salesforce is provided.
- monitoring Nov 13, 2024, 09:40 AM UTC
All the nodes are back operationally, but currently we don't see any activity on these nodes. We are moving the incident into monitoring (and will be doing some additional testing, lowering the severity to 'degraded performance'
- monitoring Nov 14, 2024, 11:08 AM UTC
All nodes are back to normal. We continue monitoring
- resolved Nov 19, 2024, 04:09 PM UTC
We consider the case closed. The root cause was a degraded performance at the salesforce side. We are looking how this can be notified in the Exalate product.
- postmortem Apr 01, 2026, 04:11 AM UTC
timeout
Partial Outage of Exalate Nodes
Affected: Synchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate Cloud
Timeline · 5 updates
- identified Oct 09, 2024, 03:15 PM UTC
We are currently experiencing an incident affecting a limited number of nodes in our system. Current situation: We've identified the root cause and a mitigation has started, some nodes are back online.
- identified Oct 09, 2024, 05:06 PM UTC
We are continuing to work on resolving the outage. Currently, 80% of the affected nodes have been restored and are fully operational.
- monitoring Oct 09, 2024, 07:26 PM UTC
All nodes are back online, we will continue monitoring and will provide further updates.
- resolved Oct 10, 2024, 06:28 AM UTC
The incident has been resolved, we will be providing a postmortem soon.
- postmortem Apr 01, 2026, 04:11 AM UTC
timeout
Nodes down due to routing incident in core infrastructure
Affected: Hosting platform
Timeline · 9 updates
Exalate Console not loading on some Zendesk
Affected: Exalate Console
Timeline · 6 updates
- investigating Aug 28, 2024, 01:35 PM UTC
We are currently experiencing an incident affecting a limited number of ZenDesk nodes. Current Situation: Affected Nodes: Approximately 30% of ZenDesk nodes are currently experiencing downtime. Actions Taken: This is currently been investigated by our Eng department. Impact on Users: Some Zendesk nodes are not accessible. Ongoing Work: We are currently testing a solution for the customer affected by this outage, once proven effective, the solution will be roll out to all affected customer. At this time there is no action needed from the customer side. We appreciate your patience and understanding during this time.
- identified Aug 28, 2024, 04:49 PM UTC
We have Identified the issue and we are currently working on a solution. If you are being affected by this outage, please create a Support ticket.
- monitoring Aug 29, 2024, 12:15 PM UTC
The incident has been successfully mitigated. Our team has taken all necessary actions to address the issue, and the situation is now under control. However, we are committed to ensuring that the resolution is sustained, and as such, we will continue to monitor the situation closely. Should any further action be required, we will take it promptly and keep you informed. Please feel free to reach out if you have any questions or need further clarification.
- monitoring Sep 02, 2024, 02:46 PM UTC
We are continuing to monitor for any further issues.
- resolved Sep 03, 2024, 02:52 PM UTC
The incident has been resolved. All nodes are operational.
- postmortem Apr 01, 2026, 04:12 AM UTC
timeout