Confluence outage: Job processing and scheduling is degraded affecting multiple Atlassian products

Affected components

• Confluence Automations

1. resolvedOct 1, 2026, 07:51 UTC

   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.

2. identifiedOct 1, 2026, 07:01 UTC

   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.

3. identifiedOct 1, 2026, 05:00 UTC

   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.

4. identifiedOct 1, 2026, 04:03 UTC

   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.

5. identifiedOct 1, 2026, 03:47 UTC

   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.

6. investigatingOct 1, 2026, 02:55 UTC

   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.

What APIStatus.watch saw

• Oct 1, 2026, 03:00 UTCoperational → degraded
• Oct 1, 2026, 07:55 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Shippo: Deutsche Post Tracking DisruptionCritical · Oct 1, 2026, 04:41 UTC
• Bitbucket: Job processing and scheduling is degraded affecting multiple Atlassian productsMajor · Oct 1, 2026, 02:55 UTC
• OVHcloud: [US-EAST-LZ-MIA][Network] - Localzone incident notificationMajor · Oct 1, 2026, 06:09 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Cloudflare: Cloudflare One Clients are incorrectly challenged on some sitesMinor · Sep 22, 2026, 19:23 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC
• Snyk: Snyk CLI Scans DegradedMinor · Sep 28, 2026, 14:26 UTC
• Clerk: Development instances only - Apple rejecting emailsMinor · Sep 28, 2026, 15:23 UTC
• Supabase: Intermittent latency in Eastern USMinor · Sep 29, 2026, 16:26 UTC

How often does Confluence have incidents?

Confluence reported 7 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 3h 40m. See Confluence's uptime and incident history