Tempo incident

Degraded performance

Minor Resolved View vendor source →

Tempo experienced a minor incident on May 8, 2026 affecting Capacity Planner and Timesheets and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 08, 2026, 02:54 PM UTC
Resolved
May 08, 2026, 02:54 PM UTC
Duration
Detected by Pingoru
May 08, 2026, 02:54 PM UTC

Affected components

Capacity PlannerTimesheetsFinancial Manager

Update timeline

  1. investigating May 08, 2026, 07:00 AM UTC

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

  2. investigating May 08, 2026, 10:26 AM UTC

    Status: Investigating We are still investigating a partial outage affecting Tempo for Jira Cloud, primarily impacting a subset of customers in the us-east-1 region. AWS Health has reported a severe degradation in the relevant region. Their team is currently investigating our particular issue and we are waiting for an update from them. Affected components Timesheets (Partial outage) Financial Manager (Partial outage) Capacity Planner (Partial outage)

  3. monitoring May 08, 2026, 02:05 PM UTC

    Status: Monitoring Together with AWS Support we were able to restore function to our backend systems that were affected by the outage. AWS continues to have degraded performance in the region, but we are now fully operational again. We will continue to monitor the situation. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

  4. resolved May 08, 2026, 02:54 PM UTC

    Status: Resolved Incident has been resolved. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)