Jira Software had a job processing and scheduling failure lasting 4h 58m on 1 October 2026. Atlassian traced it to degraded job processing affecting Jira, Confluence and Bitbucket Cloud, and the fault sat on their side, not yours.
Started
02:55 UTC
Duration
Lasted 4h 58m
Source
IsDown
Next time
Jira Software is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Notifications, Automation for Jira
What happened?
The incident started at 02:55 UTC when Atlassian reported that job processing and job scheduling was degraded, affecting scheduled and asynchronous work across several products including Jira, Confluence and Bitbucket Cloud. Affected users could see delayed or missing job execution, including delayed email-to-ticket processing and schedules that did not run as expected. At 03:47 UTC Atlassian said its teams had identified the root cause and were working on mitigation, promising an update within the hour. By 04:03 UTC they reported corrective steps had been taken and some improvement was being observed, though the incident was still open. At 05:00 UTC Atlassian added that an SLA component in Jira Service Management was not appearing as expected, widening the visible impact beyond job scheduling alone. The 07:01 UTC update confirmed a further knock-on effect: new support tickets were missing their SLA component and notifications, which could affect response times and backlog management on some tickets. The incident was marked resolved at 07:51 UTC, with Atlassian stating that between 01:00 UTC and 07:25 UTC users may have seen missing job execution and delayed email-to-ticket processing, and that a fix had since restored normal operation. Atlassian also noted that Bitbucket customers with scheduled pipelines that did not run during the window should wait for the next scheduled run or trigger them manually. The affected components on record are Notifications and Automation for Jira, two of the areas where delayed job execution would show up first. No user reports were filed during the window on this page's record. Atlassian's status page is the only source here, and its six updates are the full account of what happened and when.
Learning
This was a backend job scheduling failure inside Atlassian's infrastructure, not a problem with reachability of Jira's front end or API, which is why an external uptime check hitting Jira's login or API endpoint could easily have stayed green throughout. The failure showed up as delayed or missing background work: notifications not sending, SLA timers not appearing, email-to-ticket processing lagging, scheduled pipelines not firing. None of that necessarily breaks a simple HTTP check, because the page loads and the API responds even while the jobs behind it stall. If you run Jira-dependent workflows that depend on timely notifications or SLA tracking, this is the failure mode to watch for: everything looks up, but nothing happens on schedule. Atlassian's own 90-day history shows 17 incidents with a median duration of 2 hours 45 minutes, so this one ran longer than typical. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
