Tempo Outage History

Tempo is up right now

Tempo had 9 outages in the last 2 years totaling 624h 29m of downtime — averaging 0.4 incidents per month.

There were 9 Tempo outages since September 8, 2025 totaling 624h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tempo.io

Minor June 15, 2026

Degraded performance

Detected by Pingoru
Jun 15, 2026, 04:19 PM UTC
Resolved
Jun 15, 2026, 04:19 PM UTC
Duration
Timeline · 2 updates
  1. investigating Jun 15, 2026, 01:30 PM UTC

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

  2. resolved Jun 15, 2026, 04:19 PM UTC

    Status: Resolved Incident has been resolved.

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 →

Minor February 26, 2026

Elevated API Errors

Detected by Pingoru
Feb 26, 2026, 05:46 PM UTC
Resolved
Feb 26, 2026, 05:46 PM UTC
Duration
Affected: Capacity PlannerTimesheetsFinancial Manager
Timeline · 5 updates
  1. investigating Feb 26, 2026, 03:41 PM UTC

    Status: Investigating We're experiencing a high number of API errors in the EU cluster. We are actively investigating the cause. Affected components Financial Manager (Degraded performance) Capacity Planner (Degraded performance) Timesheets (Degraded performance)

  2. monitoring Feb 26, 2026, 03:54 PM UTC

    Status: Monitoring The issue is self-recovering. We are monitoring the issue. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

  3. monitoring Feb 26, 2026, 04:11 PM UTC

    Status: Monitoring Partial outages are still being observed in the cluster. Affected components Capacity Planner (Degraded performance) Timesheets (Degraded performance) Financial Manager (Degraded performance)

  4. monitoring Feb 26, 2026, 05:13 PM UTC

    Status: Monitoring The inbound requests have been processed stably. We continue to monitor the cluster. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

  5. resolved Feb 26, 2026, 05:46 PM UTC

    Status: Resolved The incident was resolved. Root cause analysis for a permanent solution is in progress. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

Read the full incident report →