Confluence outage on 1 October 2026
Major outageAn email when it goes down, and when it’s back.
“Job processing and scheduling is degraded affecting multiple Atlassian products”
On 1 October, Confluence had a major outage affecting Confluence Automations. The status page incident was open from 02:55 to 07:51 UTC (4 h 56 min), but its updates said delayed or missed background tasks began at 01:00 and had cleared by 07:25, while interactive use was not affected. The status page attributed this to an unexpected volume of scheduled tasks overwhelming a shared job scheduling platform, and Bitbucket, Jira Software and Jira Service Management also had problems at the same time.
Confluence’s own incident page ↗- When
- 02:56–07:52 UTC
- How long
- 4 h 56 min
- Incident open on its page
- 02:55–07:51 UTC
- Components affected
- 1
- Confluence, 30 days before
- No other outages
What broke when
From Confluence’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 144 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Update posted
- Investigating
- Confluence Automations: partial outage
- Cause identified
- Confluence Automations: degraded performance
- Resolved
- Confluence Automations: back to normal
Where this comes from
Stackpulse reads Confluence’s official status page at confluence.status.atlassian.com every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with Confluence. Names and logos belong to their owners.