All Systems Operational
Website ? Operational
API ? Operational
SSH ? Operational
Authentication and user management Operational
Git via HTTPS ? Operational
Webhooks ? Operational
Source downloads ? Operational
Pipelines ? Operational
Git LFS ? Operational
Email delivery Operational
Purchasing & Licensing Operational
Signup Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Apr 27, 23:42 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Apr 27, 23:43 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Jun 10, 04:46 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Jun 10, 04:47 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Jun 10, 04:48 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Jun 10, 04:49 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Jun 10, 04:49 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Jun 10, 04:50 UTC
The Bitbucket team will be performing maintenance to improve our storage infrastructure. To minimize disruption, maintenance will be performed during weekends in June - August 2021 (20:00 Friday - 23:00 Sunday UTC).

A subset of repositories and snippets will be processed every weekend. Each individual repository/snippet will be in a read-only state for a period of time. An active repository/snippet will be read-only for up to 30 minutes. An inactive one will be read-only for up to 4 hours.

While a repository/snippet is read-only, it cannot be modified via Bitbucket Cloud Services, including the Website, Git operations via SSH and HTTPS, API requests, and Pipelines. During this period, a git push will fail with the message “Repository is in read only mode.”

All services are expected to be back to normal after this maintenance is complete.
Posted on Jun 10, 04:51 UTC
Past Incidents
Jun 22, 2021

No incidents reported today.

Jun 21, 2021
Resolved - This incident has been resolved.
Jun 21, 00:34 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 20, 23:56 UTC
Investigating - We are investigating an issue causing some pipelines to be stuck due to steps being Queued from 22:30 UTC - 23:45 UTC. As a workaround, these pipelines can be stopped and manually re-run.
Jun 20, 23:51 UTC
Jun 20, 2021
Jun 19, 2021

No incidents reported.

Jun 18, 2021

No incidents reported.

Jun 17, 2021
Postmortem - Read details
Jun 20, 18:48 UTC
Resolved - Starting June 17, a bug was introduced that caused extra webhooks to be delivered for all open pull requests when a pull request was merged. This issue was resolved on June 18.

(This incident is being created retroactively in order to publish a postmortem.)
Jun 17, 17:33 UTC
Jun 16, 2021
Resolved - This incident has been resolved.
Jun 16, 21:41 UTC
Monitoring - We have rolled back impacted services and we are seeing continued improvements in reliability and performance as a result. We will continue monitoring the impact of the service rollbacks. We also believe we have identified the root cause.
Jun 16, 21:27 UTC
Update - We are continuing to investigate this issue.
Jun 16, 21:19 UTC
Investigating - We are currently investigating the issue and working towards a resolution.
Jun 16, 21:15 UTC
Jun 15, 2021
Resolved - This incident has been resolved
Jun 15, 09:17 UTC
Monitoring - We have identified the root cause of the performance degradation and have mitigated the problem. We are now monitoring closely.
Jun 15, 08:58 UTC
Investigating - We are investigating cases of degraded performance for Bitbucket Cloud customers affecting few features including website performance and webhooks

We will provide more details within the next hour.
Jun 15, 08:35 UTC
Resolved - This incident has been resolved.
Jun 15, 00:06 UTC
Monitoring - A workaround to AWS ECR connectivity issue in eu-west-1 has been implemented. We are monitoring and looking into the root cause.
Jun 11, 19:09 UTC
Investigating - We are investigating issues pulling AWS ECR images hosted in eu-west-1.
Jun 4, 13:16 UTC
Jun 14, 2021

No incidents reported.

Jun 13, 2021

No incidents reported.

Jun 12, 2021

No incidents reported.

Jun 11, 2021
Resolved - This incident has been resolved.
Jun 11, 14:09 UTC
Monitoring - After making a configuration change to our service responsible for handling Git hooks, we are seeing response times return to normal across all operations. We'll continue to monitor our systems and resolve this incident after performance has remained stable for 30 minutes.
Jun 11, 11:59 UTC
Update - We have successfully resolved the bottleneck in our database layer and have seen response times return to normal across most operations. However, we are continuing to see issues affecting pushes and merges. We are now directing our efforts towards identifying the cause of these last remaining issues and addressing it.
Jun 11, 11:50 UTC
Identified - We have identified the issue as a bottleneck in our database layer, which is impacting multiple systems including the website and API in addition to our GIt services. We are investigating possible mitigations now.
Jun 11, 11:40 UTC
Investigating - We have received alerts that Git push and merge operations are currently degraded. We are investigating and will provide additional updates shortly.
Jun 11, 11:28 UTC
Jun 10, 2021
Resolved - This incident has been resolved.
Jun 10, 03:18 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 10, 02:55 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 10, 02:46 UTC
Investigating - We are currently investigating this issue.
Jun 10, 02:17 UTC
Jun 9, 2021
Resolved - This incident has been resolved.
Jun 9, 02:54 UTC
Update - We are continuing to monitor for any further issues.
Jun 9, 02:53 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 8, 16:05 UTC
Identified - We have identified a bottleneck in our infrastructure that causing slowness for Git operations over both SSH and HTTPS. We are working to mitigate the issue and will continue to provide updates as we make progress.
Jun 8, 15:04 UTC
Investigating - We are currently investigating slowness affecting Git operations over SSH. We are in the process of increasing capacity for the services handling this traffic and will continue to monitor the situation.
Jun 8, 14:30 UTC
Jun 8, 2021