Live / Atlassian Bitbucket / Incident
Atlassian Bitbucket: Job processing and scheduling is degraded affecting multiple Atlassian products
Atlassian Bitbucket · bitbucket.orgMajor incidentResolved2026-10-01 07:51 UTC
Public — what happened
Summary
Atlassian Bitbucket reported a major problem starting at 02:55 UTC on 2026-10-01 in which background and scheduled tasks were slowed or failed to run across several Atlassian products, including Jira, Confluence and Bitbucket Cloud. The company said users could notice tasks running late or not at all, such as emails taking longer to become tickets and schedules not firing. By 03:47 UTC Atlassian said it had found the underlying cause, though it did not describe it, and later noted that new Jira Service Management tickets were missing SLA information and notifications, which could affect response times. After gradual recovery work, the incident was marked resolved at 07:51.
Timeline
- Started — 2026-10-01 02:55 UTC
- Investigating — 2026-10-01 02:55 UTC
- Identified — 2026-10-01 03:47 UTC (4 updates)
- Resolved — 2026-10-01 07:51 UTC · 4h 56m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Atlassian Bitbucket against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Atlassian Bitbucket: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Atlassian Bitbucket report →
More from Atlassian Bitbucket
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.