Jira Service Management 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 Service Management had a major outage affecting job processing and scheduling, including email-to-ticket processing, SLA display and notifications. The incident was open from 02:57 to 07:52 UTC (4 h 55 min), though the status page's updates said impact began earlier, at 01:00, and cleared by 07:25. The status page said an unexpected volume of scheduled tasks overwhelmed a shared scheduling platform, and it noted that interactive product use was not affected. Confluence, Bitbucket, Jira Software, Atlassian Support, Aircall, Wix and Stripe also had problems at the same time.
Jira Service Management’s own incident page ↗- When
- 02:57–07:52 UTC
- How long
- 4 h 55 min
- Incident open on its page
- 02:55–07:51 UTC
- Components affected
- 2
- Jira Service Management, 30 days before
- No other outages
What broke when
From Jira Service Management’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
- Jira Service Management Email Requests: partial outage
- Automation for Jira: partial outage
- Cause identified
- Automation for Jira: back to normal
- Jira Service Management Email Requests: degraded performance
- Resolved
- Jira Service Management Email Requests: back to normal
Where this comes from
Stackpulse reads Jira Service Management’s official status page at jira-service-management.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 Service Management. Names and logos belong to their owners.