Atlassian Bitbucket
Collaborate on code with inline comments and pull requests. Manage and share your Git repositories to build and ship software, as a team.
Homepage: https://bitbucket.org/
Status Page: https://status.bitbucket.org/
Open Incidents
No open incidents
Scheduled Incidents
Network maintenance; MTU/MSS changes coming
2017-01-10 00:07:13| Action | Date | Description |
|---|---|---|
| Scheduled | 2017-01-10 00:07:00 | We will be performing network maintenance from 00:00-03:00 UTC on 7 February 2017. As part of this maintenance, we will be reducing the MTU and MSS values on our public-facing resources.Most users will be unaffected by the MTU and MSS changes. If you begin experiencing trouble with your HTTPS or SSH connections after this maintenance is complete, though, then please see https://confluence.atlassian.com/bbkb/troubleshooting-bitbucket-cloud-mtu-mss-issues-858778091.html for troubleshooting help.As always, please contact our support team at support.atlassian.com if you need further assistance. |
Previous Incidents
Bitbucket Pipelines users may experience issues with private docker hub images
2017-01-25 22:09:38| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-25 22:09:00 | A permanent fix has been successfully deployed |
| Identified | 2017-01-25 21:19:00 | The cause identified previously only resolved the issue partially. We have identified an additional problem and a fix is currently being deployed. |
| Monitoring | 2017-01-25 20:39:00 | The root cause of the issue has been identified and corrected, and we believe this issue affected a very small number of active users. We are currently monitoring to make sure the issue is fully resolved. |
| Investigating | 2017-01-25 19:25:00 | We aware aware of an issue impacting Bitbucket Pipelines users who are attempting to use private docker hub images and we are investigating. |
Bitbucket users may experience issues logging in after resetting their password
2017-01-12 08:50:34| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-12 12:25:00 | The issue has been resolved and all users who reset their password should be able to login. |
| Identified | 2017-01-12 11:18:00 | We've identified the problem and are working on a fix as quickly as possible. |
| Investigating | 2017-01-12 08:50:00 | Some users are having trouble logging in after resetting their password. We are very sorry for the inconvenience. We are investigating and will have an update for you soon. |
We are investigating an issue where users are reporting degraded performance and intermittent connection issues.
2017-01-11 15:34:15| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-11 20:09:00 | This incident has been resolved. |
| Monitoring | 2017-01-11 16:55:00 | We have identified the issue as high load on one of our databases. Load on that database is now back to normal levels. End users should no longer be experiencing degraded performance. We will be investigating mitigation strategies to reduce the load on that database and reduce the impact of this sort of problem in the future. |
| Investigating | 2017-01-11 15:34:00 | Bitbucket users may experience degraded performance. We are currently investigating. |
Pipelines not functioning.
2017-01-05 05:22:24| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-05 06:17:00 | The incident has been resolved. Commits that were pushed between 04:51 UTC - 05:42 UTC will have not created a Pipeline and will need to be triggered again with a new commit or a manual run. |
| Monitoring | 2017-01-05 05:42:00 | We have implemented a fix for the outage, and Pipelines should be functioning as normal again. We are now monitoring the situation. |
| Investigating | 2017-01-05 05:22:00 | We are investigating an issue where all requests to Bitbucket Pipelines fail. New Pipelines are not currently starting at the moment. And old Pipelines can not be viewed. The UI will incorrectly state that Pipelines is currently disabled. We are currently investigating the cause of this issue and apologise for the outage. |
Network maintenance; brief service interruptions possible
2017-01-03 22:15:50| Action | Date | Description |
|---|---|---|
| Completed | 2017-01-15 21:30:00 | The scheduled maintenance has been completed. |
| Update | 2017-01-15 21:03:00 | Scheduled maintenance is currently in progress. We will provide updates as necessary. |
| Scheduled | 2017-01-15 21:02:00 | We're performing internal network maintenance on January 15 2017 between 21:00 and 21:30 UTC. This work will improve network reliability, but some services may be unavailable for a few minutes within that maintenance window. |
| Update | 2017-01-15 21:02:00 | Scheduled maintenance is currently in progress. We will provide updates as necessary. |
| Scheduled | 2017-01-03 22:15:00 | We're performing internal network maintenance on January 15 2017 between 21:00 and 21:30 UTC. This work will improve network reliability, but some services may be unavailable for a few minutes within that maintenance window. |
We are seeing connection issues with gitweb/hgweb
2016-12-01 05:08:26| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-01 05:08:00 | Service has been restored. |
| Monitoring | 2016-12-01 04:10:00 | We have experienced a short period of disruption to background processing tasks such as merging pull requests and processing of webhooks requests.This has also caused Bitbucket Pipelines builds to fail to run or to be delayed. Failed builds can be manually re-run or triggered from an additional commit.The team have identified the cause of the issue and are working to clear the backlog of requests. |
| Investigating | 2016-12-01 03:47:00 | We are seeing connection issues between gitweb/hgweb and our end users. We are investigating. |
Pipelines are currently failing without logs
2016-11-25 02:33:51| Action | Date | Description |
|---|---|---|
| Resolved | 2016-11-25 02:33:00 | All pipelines are starting normally. Any pipelines run between 0130 UTC - 0200 UTC will need to be rerun. |
| Monitoring | 2016-11-25 02:05:00 | We've identified an issue with our API gateway that was preventing our pipeline-agent from retrieving pipeline information. This has been resolved are seeing pipelines complete successfully. |
| Investigating | 2016-11-25 01:34:00 | new Pipelines are failing, generating no logs. |
Pipelines not running entire script
2016-11-24 06:20:10| Action | Date | Description |
|---|---|---|
| Resolved | 2016-11-24 06:20:00 | At 2:12AM UTC time, a mis-configured Docker agent image was propagated to our production cluster due to incorrect tagging. This caused builds to skip the clone step. We resolved the issue at 3:15 UTC time. |
| Monitoring | 2016-11-24 03:29:00 | Pipelines has experienced an issue where only the first command in the build script was being run. |
Bitbucket authentication experiencing issues
2016-11-10 18:04:50| Action | Date | Description |
|---|---|---|
| Resolved | 2016-11-10 18:04:00 | After the rollback of Atlassian Accounts, engineers have not witnessed any issues with authentication by users after a final reset of their credentials. At this point we consider this incident resolved. |
| Monitoring | 2016-11-10 17:10:00 | After rolling back a recent change to authentication for Atlassian Accounts. Customers can now login successfully to Bitbucket. Some customers may be expected to still reset their password, but should no longer experience the redirect loop. Engineers will continue to monitor the state of authentication. |
| Identified | 2016-11-10 16:20:00 | Some users may experience issues when attempting to login to Bitbucket which will redirect them to reset their password in a loop, keeping them from being able to login successfully. Engineers are working on mitigating the change which resulted in this issue. |