Tempo Outage History

Tempo is up right now

Tempo had 11 outages in the last 2 years totaling 603h 30m of downtime — averaging 0.5 incidents per month.

There were 11 Tempo outages since October 13, 2025 totaling 603h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tempo.io

Minor October 1, 2026

Disruption to Atlassian services

Detected by Pingoru
Oct 01, 2026, 07:25 AM UTC
Resolved
Oct 01, 2026, 07:25 AM UTC
Duration
—
Affected: Tempo for Jira Cloud Help CenterCapacity PlannerJiraTempo for SlackTimesheetsFinancial Manager
Timeline · 2 updates
  1. identified Oct 01, 2026, 01:00 AM UTC

    Status: Identified Disruption to Atlassian services first reported. Tempo services in both regions (US and EU) failed to load for many customers at this time. Affected components Capacity Planner (Partial outage) Timesheets (Partial outage) Financial Manager (Partial outage) Jira (Partial outage) Tempo for Slack (Partial outage) Tempo for Jira Cloud Help Center (Partial outage)

  2. resolved Oct 01, 2026, 07:25 AM UTC

    Status: Resolved 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. Affected components Financial Manager (Operational) Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Capacity Planner (Operational) Timesheets (Operational)

Read the full incident report →

Minor September 17, 2026

Slow response times and elevated errors

Detected by Pingoru
Sep 17, 2026, 10:53 AM UTC
Resolved
Sep 17, 2026, 10:53 AM UTC
Duration
—
Affected: Capacity PlannerTimesheetsFinancial Manager
Timeline · 5 updates
  1. investigating Sep 15, 2026, 04:22 PM UTC

    Status: Investigating We're experiencing an elevated level of request errors and slow response times. We are currently looking into the issue. Affected components Capacity Planner (Degraded performance) Timesheets (Degraded performance) Financial Manager (Degraded performance)

  2. monitoring Sep 15, 2026, 07:47 PM UTC

    Status: Monitoring We've applied some fixes that have stabilised things, but we are still dealing with some delays in processing events from Jira. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

  3. investigating Sep 16, 2026, 11:36 AM UTC

    Status: Investigating 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. Affected components Capacity Planner (Degraded performance) Timesheets (Degraded performance) Financial Manager (Degraded performance)

  4. monitoring Sep 16, 2026, 08:28 PM UTC

    Status: Monitoring We are currently monitoring to make sure the system is back to full health. Customers can expect some delay in processing Jira issue updates. Affected components Financial Manager (Degraded performance) Capacity Planner (Degraded performance) Timesheets (Degraded performance)

  5. resolved Sep 17, 2026, 10:53 AM UTC

    Status: Resolved 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. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

Read the full incident report →

Minor August 31, 2026

Tempo App Unavailability

Detected by Pingoru
Aug 31, 2026, 04:00 PM UTC
Resolved
Aug 31, 2026, 04:00 PM UTC
Duration
—
Affected: Tempo for Jira Cloud Help CenterTempo LoopCapacity PlannerTime TrackerJiraTempo for SlackTimesheetsFinancial Manager
Timeline · 5 updates
  1. investigating Aug 27, 2026, 08:36 AM UTC

    Status: Investigating 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. Affected components Financial Manager (Partial outage) Jira (Partial outage) Tempo for Slack (Partial outage) Tempo for Jira Cloud Help Center (Partial outage) Adaptive Planner (Partial outage) Time Tracker (Partial outage) Capacity Planner (Partial outage) Timesheets (Partial outage)

  2. identified Aug 27, 2026, 11:05 AM UTC

    Status: Identified 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. Affected components Tempo for Slack (Partial outage) Tempo for Jira Cloud Help Center (Partial outage) Adaptive Planner (Partial outage) Time Tracker (Partial outage) Capacity Planner (Partial outage) Timesheets (Partial outage) Financial Manager (Partial outage) Jira (Partial outage)

  3. identified Aug 27, 2026, 11:10 AM UTC

    Status: Identified 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 Affected components Adaptive Planner (Operational) Time Tracker (Operational) Capacity Planner (Partial outage) Timesheets (Partial outage) Financial Manager (Partial outage) Jira (Partial outage) Tempo for Slack (Partial outage) Tempo for Jira Cloud Help Center (Partial outage)

  4. monitoring Aug 28, 2026, 12:31 AM UTC

    Status: Monitoring A solution has been deployed. Access is being restored to affected customers. We are currently monitoring the rollout. Affected components Financial Manager (Partial outage) Jira (Partial outage) Tempo for Slack (Partial outage) Tempo for Jira Cloud Help Center (Partial outage) Adaptive Planner (Operational) Time Tracker (Operational) Capacity Planner (Partial outage) Timesheets (Partial outage)

  5. resolved Aug 31, 2026, 04:00 PM UTC

    Status: Resolved 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. Affected components Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Adaptive Planner (Operational) Time Tracker (Operational) Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational) Jira (Operational)

Read the full incident report →

Minor August 25, 2026

Degraded performance

Detected by Pingoru
Aug 25, 2026, 03:40 PM UTC
Resolved
Aug 25, 2026, 03:40 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Aug 25, 2026, 08:57 AM UTC

    Status: Investigating Status: We are currently investigating issues. Impact: Some users may experience degraded performance.

  2. monitoring Aug 25, 2026, 01:11 PM UTC

    Status: Monitoring The issue was self-healed. However, we haven't identified the root cause yet. We are investigating and continue to monitor the issue.

  3. resolved Aug 25, 2026, 03:40 PM UTC

    Status: Resolved This incident has been resolved.

Read the full incident report →

Minor July 31, 2026

Elevated API Errors

Detected by Pingoru
Jul 31, 2026, 12:30 PM UTC
Resolved
Jul 31, 2026, 12:30 PM UTC
Duration
—
Affected: Tempo Loop
Timeline · 3 updates
  1. investigating Jul 31, 2026, 04:40 AM UTC

    Status: Investigating We're experiencing an elevated level of API errors and are currently looking into the issue. Affected components Adaptive Planner (Full outage)

  2. monitoring Jul 31, 2026, 05:39 AM UTC

    Status: Monitoring The fix has been implemented. We are currently monitoring the rollout. Affected components Adaptive Planner (Full outage)

  3. resolved Jul 31, 2026, 12:30 PM UTC

    Status: Resolved The issue has been resolved. Affected components Adaptive Planner (Operational)

Read the full incident report →

Minor June 15, 2026

Brief outage

Detected by Pingoru
Jun 15, 2026, 04:20 PM UTC
Resolved
Jun 15, 2026, 04:20 PM UTC
Duration
—
Affected: Tempo for Jira Cloud Help CenterCapacity PlannerTime TrackerJiraTempo for SlackTimesheetsFinancial Manager
Timeline · 4 updates
  1. investigating Jun 15, 2026, 01:28 PM UTC

    Status: Investigating 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. Affected components Timesheets (Partial outage) Financial Manager (Partial outage) Jira (Partial outage) Tempo for Slack (Partial outage) Tempo for Jira Cloud Help Center (Partial outage) Time Tracker (Partial outage) Capacity Planner (Partial outage)

  2. monitoring Jun 15, 2026, 01:31 PM UTC

    Status: Monitoring The issue has been identified and fixed. We are currently monitoring. Affected components Financial Manager (Operational) Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Time Tracker (Operational) Capacity Planner (Operational) Timesheets (Operational)

  3. monitoring Jun 15, 2026, 04:19 PM UTC

    Status: Monitoring Incident has been resolved. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational) Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Time Tracker (Operational)

  4. resolved Jun 15, 2026, 04:20 PM UTC

    Status: Resolved Incident has been resolved. Affected components Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Time Tracker (Operational) Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

Read the full incident report →

Minor May 13, 2026

Some users unable to use Tempo

Detected by Pingoru
May 13, 2026, 09:16 AM UTC
Resolved
May 13, 2026, 09:16 AM UTC
Duration
—
Affected: Capacity PlannerTimesheetsFinancial Manager
Timeline · 4 updates
  1. investigating May 12, 2026, 05:31 AM UTC

    Status: Investigating 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. Affected components Financial Manager (Partial outage) Capacity Planner (Partial outage) Timesheets (Partial outage)

  2. investigating May 12, 2026, 05:19 PM UTC

    Status: Investigating We are still working with Atlassian on identifying the root cause for this issue. Affected components Capacity Planner (Partial outage) Timesheets (Partial outage) Financial Manager (Partial outage)

  3. identified May 13, 2026, 09:02 AM UTC

    Status: Identified 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. Affected components Capacity Planner (Degraded performance) Timesheets (Degraded performance) Financial Manager (Degraded performance)

  4. resolved May 13, 2026, 09:16 AM UTC

    Status: Resolved Our customers are reporting that they're able to access Tempo now. Affected components Financial Manager (Operational) Capacity Planner (Operational) Timesheets (Operational)

Read the full incident report →

Minor March 18, 2026

Data Processing Delays - Reporting Tools Affected

Detected by Pingoru
Mar 18, 2026, 02:24 PM UTC
Resolved
Mar 18, 2026, 02:24 PM UTC
Duration
—
Affected: Timesheets
Timeline · 3 updates
  1. investigating Mar 03, 2026, 01:48 PM UTC

    Status: Investigating 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. Affected components Timesheets (Degraded performance)

  2. investigating Mar 13, 2026, 08:50 PM UTC

    Status: Investigating We have temporarily remedied the degraded performance by scaling up the system. We continue to investigate the root cause. Affected components Timesheets (Degraded performance)

  3. resolved Mar 18, 2026, 02:24 PM UTC

    Status: Resolved We have identified and addressed the root cause of the delays. The issue is now resolved. Affected components Timesheets (Operational)

Read the full incident report →