All Systems Operational
Uptime over the past 90 days. View historical uptime.
Website ? Operational
API ? Operational
Git via 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
Person SSoT ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Past Incidents
Jul 6, 2022

No incidents reported today.

Jul 5, 2022

No incidents reported.

Jul 4, 2022

No incidents reported.

Jul 3, 2022

No incidents reported.

Jul 2, 2022

No incidents reported.

Jul 1, 2022

No incidents reported.

Jun 30, 2022

No incidents reported.

Jun 29, 2022

No incidents reported.

Jun 28, 2022

No incidents reported.

Jun 27, 2022
Pipelines not authenticating with OICD
Resolved - AWS have informed us that they have cleared their OIDC caches, we have confirmed via automated testing and the AWS console that the old correct thumbprint a031c46782e6e6c662c2c87c76da9aa62ccabd8e is now being returned consistently.
Jun 27, 12:20 UTC
Update - We are still investigating why AWS is returning the new thumbprint of 1c58a3a8518e8759bf075b76b750d4f2df264fcd rather than a031c46782e6e6c662c2c87c76da9aa62ccabd8e for the Bitbucket identity provider. To work around the issue in the meantime you can add both thumbprints to your identity provider settings in the AWS console to ensure your tokens are validated against either the new or old certificate whilst we investigate the issue more with AWS.
Jun 27, 04:11 UTC
Investigating - We are investigating a reoccurence of OIDC thumbprints being invalid with AWS causing steps using OIDC to not authenticate.
Jun 27, 02:04 UTC
Pipelines not authenticating with OICD
Resolved - A fix has been rolled out. You can rerun your pipelines using OIDC and they should now authenticate correctly again.
Jun 27, 01:00 UTC
Identified - We've identified the root cause and are currently releasing a fix for this incident.
Jun 27, 00:43 UTC
Investigating - We're currently investigating an issue with pipelines authenticating with OIDC.
Jun 27, 00:40 UTC
Jun 26, 2022

No incidents reported.

Jun 25, 2022

No incidents reported.

Jun 24, 2022

No incidents reported.

Jun 23, 2022

No incidents reported.

Jun 22, 2022
Pipelines failing due start due to docker-public.packages.atlassian.com outage
Resolved - This incident has been resolved.
Jun 22, 04:26 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 22, 04:11 UTC
Update - We’ve restored service for cloud hosted pipelines, however self hosted runners are still impacted.
Jun 22, 03:30 UTC
Investigating - An outage with docker-public.packages.atlassian.com is causing pipelines to be stuck in pending. These pipelines need to be manually stopped, and newly triggered pipelines should complete successfully.

We've mitigated the impact for cloud pipelines by failing over to an alternative docker registry, however pipelines on self hosted runners will be failing.
Jun 22, 02:26 UTC
Bitbucket webhooks and pipelines are failing for some customers
Resolved - On 21/Jun/22 8:36PM UTC we detected intermittent errors for some Atlassian Bitbucket Cloud customers. Customers would have experienced webhooks failing to be sent and pipelines failing to run. The root cause was a configuration error with our asynchronous event service. This has been resolved. If customers experienced errors with pipelines they can be re-run through the UI
Jun 22, 00:38 UTC
Monitoring - We are investigating reports of intermittent errors running webhooks or pipelines for some Atlassian Bitbucket Cloud customers.
Jun 22, 00:38 UTC
← Incident History Powered by Atlassian Statuspage