Job processing and scheduling is degraded affecting multiple Atlassian products
### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recu
The latest update from Bitbucket.
State
Resolved
Started
31 d ago
2026-10-01 02:55 UTC
Lasted
4 h 56 min
until 2026-10-01 07:51 UTC
Worst impact
Partial outage
Timeline
7 updatesInvestigating
52 min 18%
Identified
4 h 4 min 82%
Updates
Times in UTCAs posted by Bitbucket
### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recu
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.
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.
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.
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.
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.
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.
Affected components
1Bitbucket in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
5
Median duration
1 h 28 min
This incident
3.4× the median
Other Bitbucket incidents
All incidentsBitbucket·Disrupted Bitbucket availability
On October 21, 2026, Bitbucket experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Bitbucket·Bitbucket Cloud - Service Disruption
**SUMMARY** On October 15, 2026, between 9:38 and 10:14 UTC, Bitbucket Cloud customers were unable to access the web interface, API, and Pipelines. Git CLI operations over HTTPS or SSH were unaffected. The incident was triggered by a deployment that did not scale quickly enough to handle peak traffic, compounded by a capacity limit in our feature flag evaluation. Automated monitoring detected the issue within 2 minutes. We restored the web interface and API by rolling back to the previous deployment and scaling it up. Pipelines performance stayed degraded until 11:54 UTC, when all services were fully recovered. **ROOT CAUSE** The trigger for this incident was a hot fix designed to mitigate a previous performance issue that was deployed using an accelerated rollout. The website auto-scaling configuration had not been tuned for a recent infrastructure change and therefore was under provisioned following the hotfix deployment. During the incident the newly deployed web and API services co
Bitbucket·Delays with Bitbucket Pipelines Execution
The incident affecting Bitbucket Pipelines has been fully resolved and the pipeline backlog has cleared. Pipeline scheduling and build executions are now operating normally. Note: If you have any older builds that were queued or stalled during the incident window and did not automatically resume, please re-run or trigger a new build.
Bitbucket·Intermittent reliability issue with Bitbucket Cloud
On September 11 2026, between 5:30 UTC and 6:45 UTC, users experienced intermittent reliability issue that affected pull requests, commits view, related Bitbucket pages, and some Pipelines activity. Users may have also seen pages fail to load and timed out. The issue is now resolved and services have been restored to normal operation for all the affected customers.
Follow Bitbucket
Your coding agent knows when Bitbucket is down, and tells you when a failure is theirs, not yours. You can also get Bitbucket incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "bitbucket" and tell me if Bitbucket has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=bitbucket/feed subscribe https://outages.cc/feed.xml?providers=bitbucketFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane