Resolved -
The incident impacting Bitbucket Pipelines and Webhooks History has now been resolved and all components are fully back to normal.
Dec 8, 01:46 UTC
Update -
We are continuing to monitor for any further issues. Most of the features in Bitbucket Pipelines are back to normal and the service if mostly recovered and operational. We are still investigating and monitoring minor impact caused by some errors in AWS ECR during the build execution.
Dec 8, 00:33 UTC
Monitoring -
We have started to see recovery for both Pipelines and Webhook History. We are now monitoring closely and expect recovery shortly.
Dec 7, 22:38 UTC
Update -
We continue to work together with AWS to resolve the customer impact and get our services restored as soon as possible. Our incident team has assessed the impact of the expected surge in load once the AWS outage is resolved and has put the necessary mitigations in place.
Webhooks History is unavailable and has been root caused to a downstream outage with in our underlying platform provider AWS in us-east-1. Webhooks delivery is not impacted and continues to function normally.
Dec 7, 20:40 UTC
Update -
We continue to work together with AWS to resolve the customer impact and get our services restored as soon as possible. Our incident team has assessed the impact of the expected surge in load once the AWS outage is resolved and has put the necessary mitigations in place.
Webhooks History is unavailable and has been root caused to a downstream outage with in our underlying platform provider AWS in us-east-1. Webhooks delivery is not impacted and continues to function normally.
Dec 7, 19:38 UTC
Update -
We continue to work on resolving the incident with pipelines stuck in "pending" status. We have identified the root cause and will provide additional updates as soon as possible.
Dec 7, 19:01 UTC
Identified -
Bitbucket Pipelines is still not operational with builds currently stuck in "pending" state. We have identified the issue to be related with a downstream outage in our underlying platform provider AWS in us-east-1. We are working together with AWS to resolve the customer impact and get our services restored as soon as possible. You may be required to restart your Pipelines once the issue is resolved.
Dec 7, 17:52 UTC
Investigating -
We are currently investigating this issue. Your Pipelines could be stuck in "Pending" state while we resolve this issue. You may be required to restart your Pipelines once the issue is resolved.
Dec 7, 16:33 UTC