Bitbucket change history

Bitbucket Cloud reported a critical disruption affecting API, Pipelines and Website, with connection errors, timeouts and access failures. It started at 2026-10-15 10:07 UTC and resolved at 2026-10-15 12:08 UTC (2 h 0 min); a fix restored core services while Pipelines cleared backlogged builds.

Major job-processing and scheduling degradation affected Bitbucket Cloud Pipelines and other Atlassian products across all commercial cloud regions, delaying or missing background tasks; interactive use was unaffected. The recorded incident started 2026-10-01 02:55 UTC and lasted 4 h 55 min. Atlassian implemented a fix and confirmed recovery.

Bitbucket reported a critical outage affecting access, authentication, APIs, Git and Pipelines from 2026-05-14 05:03 UTC to 2026-05-14 06:48 UTC (1 h 44 min). Atlassian attributed the disruption to a race condition during a core identity service rollback in us-east; all affected products and services were reported recovered.

Bitbucket reported a critical outage affecting Website, API, Git via HTTPS, Git via SSH, and Pipelines, leaving affected users unable to access services. It started at 2026-03-06 02:44 UTC and was resolved at 2026-03-06 05:11 UTC, lasting 2 h 27 min. The postmortem attributed the disruption to a hosting-provider regional provisioning API rate limit blocking application workers from handling website traffic.

Bitbucket Cloud reported a critical outage starting 2026-01-07 16:23 UTC, resolved at 2026-01-07 18:53 UTC (2 h 29 min). Affected customers could not load the dashboard and experienced degraded navigation and intermittent public REST API failures; the postmortem attributed the disruption to unexpected public API load causing long-running database queries.

Bitbucket reported a critical incident affecting email, mobile push notifications and support ticket delivery across cloud products, recorded from 2025-12-27 04:42 UTC to 2025-12-27 05:20 UTC (37 min), then fully restored. The postmortem reports impact starting at 02:48 UTC and attributes the issue to expired monitoring TLS certificates disrupting the metrics pipeline.

Bitbucket Cloud reported a critical disruption affecting its website, APIs and Git services, starting 2025-11-11 16:59 UTC and resolved at 2025-11-11 21:10 UTC (4 h 11 min). The postmortem reports 1 hour 16 minutes of degraded performance and 1 hour 32 minutes of unavailability, triggered by a code change.

Bitbucket Cloud reported a major incident involving degraded performance and a partial Website outage starting 2025-08-19 14:27 UTC, lasting 54 min and resolving at 2025-08-19 15:22 UTC. Website functionality had recovered by 2025-08-19 14:41 UTC; no cause or fix was stated.

Bitbucket reported a major-impact degradation affecting push and clone operations over Git via HTTPS and Git via SSH for some customers. The incident started at 2025-08-01 08:16 UTC and was resolved at 2025-08-01 09:22 UTC, lasting 1 h 5 min; the vendor confirmed normal service had resumed.

Bitbucket reported a major Pipelines outage affecting some customers’ builds from 2025-07-03 01:23 UTC to 2025-07-03 02:12 UTC, lasting 49 min. The vendor linked the issues to an infrastructure provider and marked the incident resolved after that provider’s services were fully restored.

Bitbucket reported a major outage that made the product unavailable for most users, tracked from 2025-07-01 03:03 UTC to 2025-07-01 05:12 UTC (2 h 8 min). An inconsistent network access control list (ACL) rule blocked IP ranges needed for file system access; correcting the rule restored service.

Bitbucket reported a critical degradation affecting website loading and API requests, starting 2025-06-13 13:14 UTC and resolved at 2025-06-13 15:52 UTC (computed duration: 2 h 37 min). The postmortem cited high database resource usage and increased query response times; Bitbucket reported deploying a mitigation and restoring service while working on a permanent fix.

Bitbucket reported critical intermittent availability affecting API, authentication, Git operations, Pipelines and other services, disrupting access for affected users. The incident started at 2025-06-13 09:14 UTC and lasted 2 h 7 min, resolving at 2025-06-13 11:21 UTC; mitigation restored normal service by 10:31 UTC.