All Systems Operational
Website   ? Operational
API   ? Operational
SSH   ? Operational
Git via HTTPS   ? Operational
Mercurial via HTTPS   ? Operational
Webhooks   ? Operational
Source downloads   ? Operational
Pipelines   ? Operational
Git LFS   ? Operational
Email delivery   Operational
Atlassian account signup and login   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Website average response time
Fetching
API average response time
Fetching
Git average response time (HTTPS)
Fetching
Mercurial average response time (HTTPS)
Fetching
Past Incidents
Jan 21, 2018

No incidents reported today.

Jan 20, 2018

No incidents reported.

Jan 19, 2018

No incidents reported.

Jan 18, 2018

No incidents reported.

Jan 17, 2018
Resolved - We have successfully resolved the issue with malformed logs. All pipelines run now should have log structured in expected formats.
Jan 17, 09:00 UTC
Investigating - We're currently investigating an issue where logging infrastructure is showing errors on upload. Some customer logs may become malformed during this time.
Jan 17, 07:45 UTC
Jan 16, 2018

No incidents reported.

Jan 15, 2018

No incidents reported.

Jan 14, 2018

No incidents reported.

Jan 13, 2018

No incidents reported.

Jan 12, 2018
Postmortem - Read details
Jan 19, 23:37 UTC
Resolved - We have successfully returned Bitbucket Cloud to normal response times and will no longer be providing status updates about the recent performance degradation. We want to thank all customers for your patience as we worked on resolving the issue. We know that you rely on Bitbucket to keep your teams working and your businesses running, and apologize for the disruption this has caused.

We will be publishing a post-mortem next week on this Statuspage.

If you have a specific question about your repository, you can raise an issue with our support team here: https://support.atlassian.com/contact
Jan 12, 19:13 UTC
Update - The effort to repair Bitbucket Cloud's affected storage volumes is approximately 50% complete and we are continuing to target Saturday, Jan 13 for completion of this process. We will provide status updates every 12 hours to communicate our progress.
Jan 12, 06:55 UTC
Update - The effort to repair Bitbucket Cloud's affected storage volumes is approximately 40% complete and we are continuing to target Saturday, Jan 13 for completion of this process. We will provide status updates every 12 hours to communicate our progress.
Jan 11, 18:48 UTC
Update - As communicated previously, we are continuing the maintenance process to return Bitbucket Cloud to normal performance after an issue with our storage system. There was no data loss associated with this incident.

The repair effort for the affected storage volumes is approximately 30% complete and we are continuing to target Saturday, Jan 13 for completion of this process. We will provide status updates every 12 hours to communicate our progress.

If you have a specific question about your repository, you can raise an issue with our support team here: https://support.atlassian.com/contact
Jan 11, 06:57 UTC
Update - We are running a multi-day maintenance process to rebuild our storage volumes and return to normal performance. Bitbucket Cloud services and repositories are online and available for all users, however some will experience slower than normal response times until the maintenance completes. We are continuing to make improvements throughout the day to enhance performance in the interim.

We expect Bitbucket Cloud to return to normal response times by Saturday, January 13th, 2018, and will continue to provide status updates every 12 hours to communicate our progress.

If you have a specific question about your repository, you can raise an issue with our support team here: https://support.atlassian.com/contact/#/
Jan 10, 18:54 UTC
Monitoring - Our team continues to work around the clock to recover from an incident that involved a failure in Bitbucket's storage layer. Most services and repositories are functioning normally, albeit slower than usual while the storage layer repairs itself. No data has been lost, but we are continuing to run a maintenance process to bring everything back online at full capacity.
Jan 10, 02:21 UTC
Identified - All services and all repositories are back, but overall performance of the website and SSH/HTTPS transactions will continue to be slow.
We are still in the process of mitigating the performance issue and will be able to share additional information soon.
Thank you for your patience. Next update 1 hour.
Jan 9, 23:47 UTC
Update - All services and all repositories are back, but overall performance of the website, and SSH/HTTPS transactions will continue to be slow.

We are in the process of mitigating the performance issue, but cannot currently give an accurate eta for when this will be completed.

Thank you for your patience. Next update in three hours.
Jan 9, 20:22 UTC
Update - All services and all repositories are back, but overall performance of the website, and SSH/HTTPS transactions will continue to be slow.
We are in the process of fixing the overall issue with our vendor, but cannot currently give an accurate eta for when this will be completed.

Thank you for your patience. Next update in an hour.
Jan 9, 19:16 UTC
Update - The team is working with our storage vendor to address performance issues. Thank you for your patience. Next update in an hour.
Jan 9, 18:14 UTC
Update - The team is continuing to investigate possible network and/or storage layer issues, thank you for your patience. Next update in an hour.
Jan 9, 16:58 UTC
Update - We are continuing to investigate and test potential fixes for this service degradation, thank you for your patience. Next update in 60 minutes or if there is a notable change in status.
Jan 9, 15:51 UTC
Update - We are continuing to investigate the service degradation and are testing out potential fixes. Thank you for your patience, the next update will be in 60 minutes.
Jan 9, 14:50 UTC
Investigating - We are presently investigating service issues with Bitbucket resulting in degraded performance on the website and via SSH & Git via HTTPS. Next update in 60 minutes
Jan 9, 13:47 UTC
Jan 8, 2018

No incidents reported.

Jan 7, 2018

No incidents reported.