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.
Status: Investigating Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
Status: Resolved Incident has been resolved.
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)
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)
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)
Status: Resolved Our customers are reporting that they're able to access Tempo now. Affected components Financial Manager (Operational) Capacity Planner (Operational) Timesheets (Operational)
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)
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)
Status: Resolved We have identified and addressed the root cause of the delays. The issue is now resolved. Affected components Timesheets (Operational)
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)
Status: Monitoring The issue is self-recovering. We are monitoring the issue. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)
Status: Monitoring Partial outages are still being observed in the cluster. Affected components Capacity Planner (Degraded performance) Timesheets (Degraded performance) Financial Manager (Degraded performance)
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)
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)