We started checking Bitbucket on August 22, 2026, which is 63 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Bitbucket's own status page declared. Below it, any public chatter we saw about Bitbucket and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Bitbucket's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Bitbucket in the last 24 hours, which is not evidence that nothing is wrong.
Bitbucket's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Bitbucket's own declaration, shown as they made it.
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Bitbucket's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Disrupted Bitbucket availabilityMajor outage
Oct 21, 2026, 5:22 PM UTC to Oct 21, 2026, 6:01 PM UTC (40 min)resolved
their latest update (Oct 21, 2026, 6:01 PM UTC): 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 Cloud - Service DisruptionMajor outage
Oct 15, 2026, 10:07 AM UTC to Oct 15, 2026, 12:08 PM UTC (2h 1m)resolved
their latest update (Oct 15, 2026, 12:08 PM UTC): On October 15th, 2026, between 10:42 UTC to 11:14 UTC, some Bitbucket Cloud users may have experienced disruptions accessing the web interface and running Pipelines.
The issue has now been resolved and the service is operating normally for all the customers.
Job processing and scheduling is degraded affecting multiple Atlassian productsPartial outage
Oct 1, 2026, 2:55 AM UTC to Oct 1, 2026, 7:51 AM UTC (4h 56m)postmortem published
their latest update (Oct 9, 2026, 6:24 PM UTC): ### 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 bac…
Delays with Bitbucket Pipelines ExecutionMinor incident
Sep 16, 2026, 9:32 AM UTC to Sep 16, 2026, 10:15 AM UTC (44 min)resolved
their latest update (Sep 16, 2026, 10:15 AM UTC): 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 aut…
Intermittent reliability issue with Bitbucket CloudMinor incident
Sep 11, 2026, 6:31 AM UTC to Sep 11, 2026, 8:00 AM UTC (1h 28m)resolved
their latest update (Sep 11, 2026, 8:00 AM UTC): 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 reso…
BitBucket Site fails to LoadAll systems operational
Jul 31, 2026, 1:09 PM UTC to Jul 31, 2026, 3:38 PM UTC (2h 29m)resolved
their latest update (Jul 31, 2026, 3:38 PM UTC): On July 31, 2026, affected Bitbucket Cloud users for some customers may have experienced failures loading the site and impacts to associated pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.
Degraded performance of BitbucketMinor incident
Jun 11, 2026, 10:48 PM UTC to Jun 12, 2026, 12:14 AM UTC (1h 26m)resolved
their latest update (Jun 12, 2026, 12:14 AM UTC): On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.
Users experiencing issues accessing multiple Atlassian productsMajor outage
May 14, 2026, 5:03 AM UTC to May 14, 2026, 6:48 AM UTC (1h 45m)postmortem published
their latest update (May 19, 2026, 7:07 PM UTC): ### Summary
On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback …
Multiple Atlassian services are experiencing issuesMinor incident
May 8, 2026, 1:31 AM UTC to May 8, 2026, 7:45 PM UTC (18h 14m)postmortem published
their latest update (May 20, 2026, 6:56 AM UTC): All dates and times below are in UTC unless stated otherwise.
### Summary
On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded per…
Bitbucket Pipelines degraded performanceMinor incident
Apr 16, 2026, 8:23 PM UTC to Apr 16, 2026, 8:44 PM UTC (22 min)resolved
their latest update (Apr 16, 2026, 8:44 PM UTC): On April 16 at 8:00PM UTC Bitbucket Pipelines users may have experienced performance degradation running new pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.
Showing the 10 most recent of 55 incidents Bitbucket has declared in the history we hold.
These entries are Bitbucket's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Bitbucket's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.