Jira Software 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, Jira Software had a major outage from 02:56 to 07:52 UTC (4 h 55 min), in which scheduled and background jobs such as automations, notifications and email-to-ticket processing were delayed or missed. The status page's own updates said interactive use was unaffected, and that the impact started earlier and ended sooner than the incident was open, running from 01:00 to 07:25 UTC. The status page attributed it to an unexpected volume of scheduled tasks overwhelming a shared job scheduling platform, and Confluence, Bitbucket and Jira Service Management also had problems at the same time.
Jira Software’s own incident page ↗- When
- 02:56–07:52 UTC
- How long
- 4 h 55 min
- Incident open on its page
- 02:55–07:51 UTC
- Components affected
- 2
- Jira Software, 30 days before
- No other outages
What broke when
From Jira Software’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
- Automation for Jira: partial outage
- Cause identified
- Automation for Jira: back to normal
- Notifications: partial outage
- Notifications: degraded performance
- Resolved
- Notifications: back to normal
Where this comes from
Stackpulse reads Jira Software’s official status page at jira-software.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 Jira Software. Names and logos belong to their owners.