Tempo Outage History

Some users on affected Tempo instances were unable to access the service and received "403 The app is not installed on this instance" errors, while other users on the same instances could access it normally. The issue affected Timesheets, Planner, and Cost Tracker components for 19.3 hours. Atlassian identified and fixed the root cause related to automation events, restoring access to affected instances.

Tempo experienced degraded performance for 7.9 hours, affecting the Timesheets, Planner, and Cost Tracker components primarily for customers in the us-east-1 region. The issue was caused by AWS backend system problems in that region, which Tempo worked with AWS Support to resolve. Service was fully restored once the underlying AWS infrastructure issues were addressed.

Tempo experienced calendar event synchronization delays affecting users with Microsoft Outlook and Google Calendar integrations, preventing events from appearing properly in Tempo Timesheets. The incident lasted approximately 15 days and impacted the Timesheets component. The engineering team temporarily resolved the performance issues by scaling up the system while continuing to investigate the root cause.

Tempo experienced elevated API errors in the EU cluster for 2.1 hours, affecting Timesheets, Planner, and Cost Tracker components. The issue was classified as minor and self-recovered, with partial outages observed during the incident. The service was restored to stable processing with continued monitoring.