All Systems Operational

About This Site

Welcome to exalate's status page

Uptime over the past 90 days. View historical uptime.
Zendesk Operational
90 days ago
100.0 % uptime
Today
Exalate Console Operational
90 days ago
100.0 % uptime
Today
Exalate Cloud Operational
90 days ago
99.92 % uptime
Today
connect.exalate.net (mapper) Operational
Hosting platform Operational
connect.exalate.cloud Operational
90 days ago
99.92 % uptime
Today
Jira Cloud Operational
90 days ago
100.0 % uptime
Today
Synchronisation node Operational
90 days ago
100.0 % uptime
Today
Table Grid Next Generation Operational
90 days ago
100.0 % uptime
Today
Table Grid Cloud - Server Operational
90 days ago
100.0 % uptime
Today
Documentation Operational
90 days ago
100.0 % uptime
Today
Documentation Host Operational
90 days ago
100.0 % uptime
Today
Exalate Documentation Operational
90 days ago
100.0 % uptime
Today
Table Grid Next Generation - Documentation Operational
90 days ago
100.0 % uptime
Today
Table Grid Editor Documentation Operational
90 days ago
100.0 % uptime
Today
Pivot Documentation Operational
90 days ago
100.0 % uptime
Today
Exalate Support Operational
90 days ago
100.0 % uptime
Today
Azure DevOps Operational
90 days ago
100.0 % uptime
Today
Exalate for Azure DevOps Operational
90 days ago
100.0 % uptime
Today
Service Now Operational
90 days ago
100.0 % uptime
Today
Exalate for ServiceNow in Exalate Cloud Operational
90 days ago
100.0 % uptime
Today
GitHub Operational
90 days ago
100.0 % uptime
Today
Exalate for GitHub Operational
90 days ago
100.0 % uptime
Today
Salesforce Operational
90 days ago
100.0 % uptime
Today
Exalate for SalesForce Operational
90 days ago
100.0 % uptime
Today
Exalate.com website Operational
90 days ago
100.0 % uptime
Today
Exalate for Freshdesk in Exalate Cloud Operational
90 days ago
100.0 % uptime
Today
Freshdesk Operational
90 days ago
100.0 % uptime
Today
Exalate for Freshservice in Exalate Cloud Operational
90 days ago
100.0 % uptime
Today
Freshservice Operational
90 days ago
100.0 % uptime
Today
Exalate.app Operational
90 days ago
99.99 % uptime
Today
Exalate Community Operational
90 days ago
100.0 % uptime
Today
Aida Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jul 30, 2026

Upgrade of Exalate for New Exalate to 4.2.0 version
Completed - The scheduled maintenance has been completed.
Jul 30, 14:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 30, 13:00 CEST
Scheduled - We’re introducing a new update for New Exalate with significant performance improvements, pagination across key pages, and a range of fixes improving stability and usability.

For detailed information, please refer to the release notes:

- https://community.exalate.com/t/new-exalate-version-4-1/8203;

Maintenance Window: The maintenance is scheduled to take place between 12 CET and 13 CET.
Jul 29, 16:08 CEST

Jul 29, 2026

No incidents reported.

Jul 28, 2026

Upgrade of Exalate for Jira Cloud to 5.36.0 version
Completed - The scheduled maintenance has been completed.
Jul 28, 18:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 12:00 CEST
Scheduled - This upgrade for Jira Cloud part 2 includes improvements and bug fixes.

For detailed information, please refer to the release notes:
https://community.exalate.com/t/jira-cloud-version-5-36-0/8251

- Maintenance Window: The maintenance is scheduled to take place between 12 CET and 14 CET. During this time, updates will be applied to all customer nodes using the Jira Cloud.
- Service Impact for your Instance: For your specific instance, the service will experience a brief interruption of approximately 3-5 minutes during a scheduled restart.
Jul 28, 11:52 CEST

Jul 27, 2026

Upgrade of Exalate for Jira Cloud to 5.36.0 version
Completed - The scheduled maintenance has been completed.
Jul 27, 14:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 27, 12:00 CEST
Scheduled - This upgrade for Jira Cloud part 1 includes improvements and bug fixes.

For detailed information, please refer to the release notes:
https://community.exalate.com/t/jira-cloud-version-5-36-0/8251

- Maintenance Window: The maintenance is scheduled to take place between 12 CET and 14 CET. During this time, updates will be applied to all customer nodes using the Jira Cloud.
- Service Impact for your Instance: For your specific instance, the service will experience a brief interruption of approximately 3-5 minutes during a scheduled restart.
Jul 24, 18:09 CEST

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

App name change/proxy user on Atlassian Jira Cloud
Resolved - The proxy user name was reverted back to Exalate.

We are considering the incident as resolved.
Jul 24, 18:33 CEST
Update - 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.
Jul 24, 17:47 CEST
Update - We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible.
Jul 24, 14:39 CEST
Update - We continue to investigate the best approach to solve this issue with the help of Atlassian support.
Jul 24, 11:15 CEST
Identified - 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.
Jul 24, 08:12 CEST

Jul 23, 2026

Maintenance window for Exalate Classic
Completed - The maintenance window programmed tasks were completed successfully.
Jul 23, 21:30 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 23, 17:30 CEST
Scheduled - We will be performing maintenance tasks for the nodes of all the available connectors.

We will post an update once the intervention is completed.

Thanks in advance
Jul 23, 17:04 CEST

Jul 22, 2026

Upgrade of Exalate Classic for Salesforce, ServiceNow, Asana, Freshdesk, Freshservice, Jira Cloud Headless to 5.36.0 version
Completed - The scheduled maintenance has been completed.
Jul 22, 19:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 22, 12:00 CEST
Scheduled - This upgrade for Salesforce, ServiceNow, Asana, Freshdesk, Freshservice, Jira Cloud Headless includes important bug fixes and improvements.

For detailed information, please refer to the release notes:

- https://community.exalate.com/t/salesforce-version-5-36-0/8231
- https://community.exalate.com/t/servicenow-version-5-36-0/8230
- https://community.exalate.com/c/release-history/asana/28
- https://community.exalate.com/t/freshservice-version-5-36-1/8233
- https://community.exalate.com/t/freshdesk-version-5-36-1/8234
- Jira Cloud Headless will be covered in scope of New Exalate 4.2 release.

Note: final build number for Asana, Freshdesk and Freshservice will be 5.36.1 (not 5.36.0) due to an internal pipeline rebuild — no functional or scope changes.

- Maintenance Window: The maintenance is scheduled to take place between 12PM CET and 7PM CET. During this time, updates will be applied to all customer nodes using the Salesforce, ServiceNow, Asana, Freshdesk, Freshservice, Jira Cloud Headless connectors.
- Service Impact for Your Instance: For your specific instance, the service will experience a brief interruption of approximately 3-5 minutes during a scheduled restart.
Jul 21, 17:25 CEST

Jul 21, 2026

No incidents reported.

Jul 20, 2026

Upgrade of Exalate for GitHub, Zendesk, Azure DevOps, Azure DevOps on-premise to 5.35.0 version
Completed - The scheduled maintenance has been completed.
Jul 20, 16:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 20, 13:00 CEST
Scheduled - This upgrade for includes important improvement and bug fixes.

For detailed information, please refer to the release notes:

- https://community.exalate.com/t/azure-devops-version-5-36-0/8229;
- https://community.exalate.com/t/zendesk-version-5-36-0/8228;
- https://community.exalate.com/t/github-version-5-36-0/8227

- Maintenance Window: The maintenance is scheduled to take place between 13:00 CET and 16:00 CET. During this time, updates will be applied to all customer nodes using Github, Zendesk and Azure DevOps.
- Service Impact for your Instance: For your specific instance, the service will experience a brief interruption of approximately 3-5 minutes during a scheduled restart
Jul 20, 12:00 CEST

Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

Jul 17, 2026

No incidents reported.

Jul 16, 2026

JiraCloud nodes experiencing some instablility
Resolved - After close monitoring, the issue is considered as fully resolved. We will be posting a RCA here in due course.
Jul 16, 19:18 CEST
Monitoring - All nodes are back to normal operation. We continue to monitor the situation closely.
Jul 16, 17:57 CEST
Update - The restart is still in progress and is going without any issues. We will update you as soon as it is completed.
Jul 16, 17:15 CEST
Update - 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.
Jul 16, 15:38 CEST
Identified - 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.
Jul 16, 14:03 CEST
Investigating - 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.
Jul 16, 13:28 CEST
← Incident History Powered by Atlassian Statuspage