30 recorded Tempo incidents since April 2017, with official updates, affected components, duration and resolution information.
Atlassian has reported an incident which occured between 01:00 UTC and 07:25 UTC: This resulted in Tempo failing to load for many customers. The incident has resolved and Tempo services are confirmed to be working normally.
Disruption to Atlassian services first reported. Tempo services in both regions (US and EU) failed to load for many customers at this time.
We're experiencing an elevated level of request errors and slow response times. We are currently looking into the issue.
We've applied some fixes that have stabilised things, but we are still dealing with some delays in processing events from Jira.
We are continuing to investigate latencies that are causing problems loading the web app. This ties into the incident from yesterday. There is some delay in processing events from Jira as well as a result of this.
We are currently monitoring to make sure the system is back to full health. Customers can expect some delay in processing Jira issue updates.
The incident has been resolved. During the incident we had to block Jira Issue webhook processing, but any updates in Jira since September 16th at 8:30pm have been processed normally.
We are currently experiencing an issue where Tempo is failing to load for a subset of customers in our US instance. Our development team is actively investigating the cause.
The incident affected a subset of our customers running connect on forge, and legacy connect apps. We have identified the problem and are looking into a solution to restore access as soon as possible
A solution has been deployed. Access is being restored to affected customers. We are currently monitoring the rollout.
This incident has been resolved. The affected Tempo apps have been restored and are operating normally for impacted customers. A fix has been deployed to prevent recurrence. If you're still experiencing issues, please contact Tempo Support.
Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
The issue was self-healed. However, we haven't identified the root cause yet. We are investigating and continue to monitor the issue.
This incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
The fix has been implemented. We are currently monitoring the rollout.
The issue has been resolved.
Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
Incident has been resolved.
We're currently investigating a brief outage that caused our systems to be inaccessible. The system is up and running now but users can expect delays in event processing.
The issue has been identified and fixed. We are currently monitoring.
Incident has been resolved.
Incident has been resolved.
Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
We had some delay in event processing during last night, the issue has been resolved.
Some users on affected instances are unable to use Tempo, while other users on the same instance are able to. The affected users will see the error `403 The app is not installed on this instance` if they open the browser's network tab and look for the `/rest/api/3/mypermissions` being called. We are investigating.
We are still working with Atlassian on identifying the root cause for this issue.
Atlassian reported overnight that they've identified and fixed a problem with automation events. We've confirmed on our side that affected instances should now again be able to access. According to Atlassian status page delays can be expected in processing events that have accumulated during the incident.
Our customers are reporting that they're able to access Tempo now.
Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
We are still investigating a partial outage affecting Tempo for Jira Cloud, primarily impacting a subset of customers in the us-east-1 region. AWS Health has reported a severe degradation in the relevant region. Their team is currently investigating our particular issue and we are waiting for an update from them.
Together with AWS Support we were able to restore function to our backend systems that were affected by the outage. AWS continues to have degraded performance in the region, but we are now fully operational again. We will continue to monitor the situation.
Incident has been resolved.
The migration of Timesheets, Capacity Planner, and Financial Manager to [Forge](https://www.tempo.io/product-news/tempo-moves-to-forge) is underway, but the **automatic rollout did not start on March 31, 2026 as planned.** The automatic migration to Forge is tentatively scheduled to begin on June 15, 2026. You have the option to do either of the following: • **Perform a manual update** Review the expected changes (see links below) and assess any impacts to your workflows. If the impact is manageable, we recommend updating manually to control the timing of your instance’s migration. • **Wait for automatic update** The automatic rollout will occur gradually, so we are unable to confirm the exact date your instance will be updated. It will not be possible to schedule, delay, or opt out once started. After your instance is updated, you will receive an in-app notification confirming the change. You can also verify if your instance has migrated to Forge by **[checking the app versions](https://tempo-io.atlassian.net/wiki/spaces/DRAFTTIMESHEETS/pages/5679415354/Timesheets+Migration+to+Forge+FAQs#How-to-Check-Your-Current-Version).** **Breaking changes** Most of the migration is seamless, but a few things will change that may affect you, particularly around JQL filters: • JQL filter syntax – `issueInternal`, Account, Tempo Team, and custom field IDs • Tempo Panels in Jira issue view • Keyboard shortcuts • OAuth app URLs Please review the relevant documentation to prepare for changes that might affect you: • [Expected Changes in Timesheets on Forge](https://help.tempo.io/timesheets/latest/expected-changes-in-timesheets-on-forge) • [Expected Changes in Capacity Planner on Forge](https://help.tempo.io/planner/latest/expected-changes-in-capacity-planner-on-forge) • [Expected Changes in Financial Manager on Forge](https://help.tempo.io/financialmanager/latest/expected-changes-in-financial-manager-on-forge)
We are currently experiencing delays in calendar event synchronization for users with Microsoft Outlook (O365) and Google Calendar integrations. Events may not appear in Tempo Timesheets as expected. Our engineering team is actively investigating the issue. We will provide further updates as we learn more. We apologize for the inconvenience.
We have temporarily remedied the degraded performance by scaling up the system. We continue to investigate the root cause.
We have identified and addressed the root cause of the delays. The issue is now resolved.
We're experiencing a high number of API errors in the EU cluster. We are actively investigating the cause.
The issue is self-recovering. We are monitoring the issue.
Partial outages are still being observed in the cluster.
The inbound requests have been processed stably. We continue to monitor the cluster.
The incident was resolved. Root cause analysis for a permanent solution is in progress.
We are currently investigating the issue.
The disruption has now been resolved.
We identified the root cause and applied a fix.
We're experiencing degraded performance on our US based service and are currently looking into the issue.
Our systems are operational again. We are monitoring.
Resolved
We are currently investigating issues reported in the Production EU region.
A fix has been applied. We will continue to monitor the EU production environment to ensure all issues have been resolved.
EU production services have been restored. We will continue to monitor.
We are currently experiencing slow data sync with Jira. Worklogs created on new Jira issues or newly updated Jira issues might not display correctly until after a delay.
Service disruption in EU has been fully resolved, and data sync with Jira is up to date.
Incident has been resolved.
We're experiencing widespread issues due to an ongoing provider outage
AWS appears to have fixed the issue, and our services have recovered. We are monitoring the situation closely.
We have investigated and we are continuing to experience widespread issues due to an ongoing AWS incident with the US-EAST-1 Region ( https://health.aws.amazon.com/health/status ) . We will continue to provide update as the situation evolves.
Our cloud provider AWS is continuing to recover from the outage earlier today, but we are still experiencing degraded performance because of this. Atlassian are also affected because of this outage. No ETA has been provided yet by the cloud provider and we continue to monitor the situation.
AWS have resolved the incident on their end, and Atlassian reported that they are not seeing problems in their systems anymore.
We are currently investigating issues reported in the Production EU region.
A fix has been applied. We will continue to monitor the EU production environment to ensure all issues have been resolved.
The issue has been identified and a fix is being tested.
We are continuing to work on a fix for this issue.
EU production services have been stabilised and latency issues (slow response times) are being addressed.
This incident has been resolved.
We are continuing to monitor for any further issues.
We are currently investigating this issue.
We identified the issue and working on the resolution.
We are continuing to investigate this issue.
This incident was resolved
Our infrastructure is now back up. We will keep monitoring the system.
We are currently investigating an issue where the Tempo Account and Tempo Team fields may not appear when editing issues in Jira. The fields are still visible in the `Create Issue` screen but disappear in the issue side panel when editing. Our team is working with Atlassian to determine the root cause. In the meantime, you may be unable to update these fields when editing issues. We will provide updates as soon as more information is available.
We are continuing to investigate this issue.
This incident has been resolved.
