Tempo Outage History
Tempo is up right nowPingoru has recorded 21 incidents for Tempo: 19 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 336 of 720 (47%) |
| May 2026 | 2 | 36 of 744 (5%) |
| June 2026 | 3 | 10 of 720 (1%) |
| July 2026 | 1 | 8 of 744 (1%) |
| August 2026 | 2 | 110 of 744 (15%) |
| September 2026 | 1 | 43 of 720 (6%) |
| October 2026 | 1 | 6 of 583 (1%) |
Incidents, newest first
Minor October 1, 2026 Disruption to Atlassian services 6h 25m Tempo for Jira Cloud Help Center, Capacity Planner, Jira, Tempo for Slack and 2 more
Started Oct 01, 2026, 01:00 AM UTC· resolved Oct 01, 2026, 07:25 AM UTC
- identified Oct 01, 2026, 01:00 AM UTC
Disruption to Atlassian services first reported. Tempo services in both regions (US and EU) failed to load for many customers at this time.
- resolved Oct 01, 2026, 07:25 AM UTC
Atlassian has reported an incident which occured between 01:00 UTC and 07:25 UTC: https://jira-software.status.atlassian.com/incidents/vwrp378v0zmk This resulted in Tempo failing to load for many customers. The incident has resolved and Tempo services are confirmed to be working normally.
Minor September 15, 2026 Slow response times and elevated errors 1d 18h Capacity Planner, Timesheets, Financial Manager
Started Sep 15, 2026, 04:22 PM UTC· resolved Sep 17, 2026, 10:53 AM UTC
- investigating Sep 15, 2026, 04:22 PM UTC
We're experiencing an elevated level of request errors and slow response times. We are currently looking into the issue.
- monitoring Sep 15, 2026, 07:47 PM UTC
We've applied some fixes that have stabilised things, but we are still dealing with some delays in processing events from Jira.
- investigating Sep 16, 2026, 11:36 AM UTC
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.
- monitoring Sep 16, 2026, 08:28 PM UTC
We are currently monitoring to make sure the system is back to full health. Customers can expect some delay in processing Jira issue updates.
- resolved Sep 17, 2026, 10:53 AM UTC
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.
Minor August 27, 2026 Tempo App Unavailability 4d 7h Tempo for Jira Cloud Help Center, Tempo Loop, Capacity Planner, Time Tracker and 4 more
Started Aug 27, 2026, 08:36 AM UTC· resolved Aug 31, 2026, 04:00 PM UTC
- investigating Aug 27, 2026, 08:36 AM UTC
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.
- identified Aug 27, 2026, 11:05 AM UTC
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.
- identified Aug 27, 2026, 11:10 AM UTC
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
- monitoring Aug 28, 2026, 12:31 AM UTC
A solution has been deployed. Access is being restored to affected customers. We are currently monitoring the rollout.
- resolved Aug 31, 2026, 04:00 PM UTC
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.
Minor August 25, 2026 Degraded performance 6h 43m
Started Aug 25, 2026, 08:57 AM UTC· resolved Aug 25, 2026, 03:40 PM UTC
- investigating Aug 25, 2026, 08:57 AM UTC
Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
- monitoring Aug 25, 2026, 01:11 PM UTC
The issue was self-healed. However, we haven't identified the root cause yet. We are investigating and continue to monitor the issue.
- resolved Aug 25, 2026, 03:40 PM UTC
This incident has been resolved.
Minor July 31, 2026 Elevated API Errors 7h 50m Tempo Loop
Started Jul 31, 2026, 04:40 AM UTC· resolved Jul 31, 2026, 12:30 PM UTC
- investigating Jul 31, 2026, 04:40 AM UTC
We're experiencing an elevated level of API errors and are currently looking into the issue.
- monitoring Jul 31, 2026, 05:39 AM UTC
The fix has been implemented. We are currently monitoring the rollout.
- resolved Jul 31, 2026, 12:30 PM UTC
The issue has been resolved.
Minor June 15, 2026 Brief outage 2h 51m Tempo for Jira Cloud Help Center, Capacity Planner, Time Tracker, Jira and 3 more
Started Jun 15, 2026, 01:28 PM UTC· resolved Jun 15, 2026, 04:20 PM UTC
- investigating Jun 15, 2026, 01:28 PM UTC
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.
- monitoring Jun 15, 2026, 01:31 PM UTC
The issue has been identified and fixed. We are currently monitoring.
- monitoring Jun 15, 2026, 04:19 PM UTC
Incident has been resolved.
- resolved Jun 15, 2026, 04:20 PM UTC
Incident has been resolved.
Minor May 12, 2026 Some users unable to use Tempo 1d 3h Capacity Planner, Timesheets, Financial Manager
Started May 12, 2026, 05:31 AM UTC· resolved May 13, 2026, 09:16 AM UTC
- investigating May 12, 2026, 05:31 AM UTC
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.
- investigating May 12, 2026, 05:19 PM UTC
We are still working with Atlassian on identifying the root cause for this issue.
- identified May 13, 2026, 09:02 AM UTC
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.
- resolved May 13, 2026, 09:16 AM UTC
Our customers are reporting that they're able to access Tempo now.
Notice April 2, 2026 Forge Migration Update 24d 3h
Started Apr 02, 2026, 09:46 PM UTC· resolved Apr 27, 2026, 01:30 AM UTC
No vendor updates were posted for this incident.
Minor March 3, 2026 Data Processing Delays - Reporting Tools Affected 15d Timesheets
Started Mar 03, 2026, 01:48 PM UTC· resolved Mar 18, 2026, 02:24 PM UTC
- investigating Mar 03, 2026, 01:48 PM UTC
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.
- investigating Mar 13, 2026, 08:50 PM UTC
We have temporarily remedied the degraded performance by scaling up the system. We continue to investigate the root cause.
- resolved Mar 18, 2026, 02:24 PM UTC
We have identified and addressed the root cause of the delays. The issue is now resolved.
Major January 2, 2026 Service disruptions in the EU region –
Started Jan 02, 2026, 04:37 PM UTC· resolved Jan 02, 2026, 04:37 PM UTC
No vendor updates were posted for this incident.
Critical October 20, 2025 Widespread issues due to ongoing provider outage 23h 46m
Started Oct 20, 2025, 09:10 AM UTC· resolved Oct 21, 2025, 08:56 AM UTC
No vendor updates were posted for this incident.