Job processing and scheduling is degraded affecting multiple Atlassian products

Summary

Job processing and scheduling is degraded affecting multiple Atlassian products

On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

• Started

  Oct 1, 2026 · 2:55 AM

• Resolved

  Oct 1, 2026 · 7:51 AM

• Duration

  4h 55m

• Severity

  Major

• ◐

  Investigating

  Oct 1 · 2:55 AM Jira Software

  Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

• ◆

  Identified

  Oct 1 · 3:47 AM Jira Software

  Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

• ◆

  Identified

  Oct 1 · 4:03 AM Jira Software

  Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

• ◆

  Identified

  Oct 1 · 5:00 AM Jira Software

  Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

• ◆

  Identified

  Oct 1 · 7:01 AM Jira Software

  Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

• ✓

  Resolved

  Oct 1 · 7:51 AM Jira Software

  On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.