Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Atlassian Bitbucket and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Atlassian Bitbucket.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API | Active |
| Authentication and user management | Active |
| Email delivery | Active |
| Git LFS | Active |
| Git via HTTPS | Active |
| Git via SSH | Active |
| Pipelines | Active |
| Purchasing & Licensing | Active |
| Signup | Active |
| Source downloads | Active |
| Webhooks | Active |
| Website | Active |
View the latest incidents for Atlassian Bitbucket and check for official updates:
Description: We have resolved a case of degraded performance for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details within the next hour.
Status: Resolved
Impact: None | Started At: Aug. 22, 2023, 1:08 a.m.
Description: We have resolved a case of degraded performance for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details within the next hour.
Status: Resolved
Impact: None | Started At: Aug. 22, 2023, 1:08 a.m.
Description: ### **SUMMARY** On 2023-08-02, Atlassian customers were unable to perform a range of billing and cloud provisioning actions. It affected the Jira family of products, Confluence, Marketplace apps, and Bitbucket. The event started when in the normal order of operation, traffic to Atlassian billing systems increased and new nodes were supposed to be created. However, due to a prior rotation of passwords, new nodes were unable to connect to the Atlassian billing systems database. This meant that no new nodes were spun up to handle the increased traffic and the existing nodes became overloaded. The incident was mitigated by resetting the passwords and new nodes were able to be created. ### **IMPACT** The overall impact was on 2023-08-02, on [www.atlassian.com](http://www.atlassian.com), [my.atlassian.com](http://my.atlassian.com), Billing Admin UI, Marketplace, and Bitbucket. The incident caused customers to be unable to use the aforementioned Atlassian billing systems in all regions. The outage lasted for 3 hours and 10 minutes and impacted the following products and services: [www.atlassian.com](http://www.atlassian.com) * Could not signup for new cloud accounts * Could not activate new products on existing cloud accounts * Could not create, view or pay for quotes [my.atlassian.com](http://my.atlassian.com) * Offline In-app billing admin UI for cloud accounts * Could not view/update billing details * Could not provide bill estimate * Could not activate new products or apps Marketplace * Could not activate or deactivate apps on existing cloud accounts * Vendors could not update their configuration or the configuration of their apps * Some delay in updating vendor sales reports during the time of the incident Bitbucket * Could not update billing details * Could not provide bill estimate ### **ROOT CAUSE** For reasons related to keeping our systems secure, passwords used for some of the Atlassian billing systems are rotated. However, the same passwords were used in other parts of the Atlassian billing infrastructure. This had the unintended side effect that it became impossible to create new nodes to handle increased traffic. Nodes that already were up and running kept functioning, but weren't able to handle the increased load. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that any outage impacts your productivity. We make every effort to keep all our systems up and running in a reliable and secure manner. Unfortunately, in this case, rotating passwords for security reasons had the unintended side effect of making our billing systems unavailable. As a high-priority action, we have separated the passwords being used in different services across the billing systems. Furthermore, we are undertaking a comprehensive program to modernize the security infrastructure for our billing systems, significantly reducing the need to use passwords. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Status: Postmortem
Impact: None | Started At: Aug. 2, 2023, 1:41 p.m.
Description: ### **SUMMARY** On 2023-08-02, Atlassian customers were unable to perform a range of billing and cloud provisioning actions. It affected the Jira family of products, Confluence, Marketplace apps, and Bitbucket. The event started when in the normal order of operation, traffic to Atlassian billing systems increased and new nodes were supposed to be created. However, due to a prior rotation of passwords, new nodes were unable to connect to the Atlassian billing systems database. This meant that no new nodes were spun up to handle the increased traffic and the existing nodes became overloaded. The incident was mitigated by resetting the passwords and new nodes were able to be created. ### **IMPACT** The overall impact was on 2023-08-02, on [www.atlassian.com](http://www.atlassian.com), [my.atlassian.com](http://my.atlassian.com), Billing Admin UI, Marketplace, and Bitbucket. The incident caused customers to be unable to use the aforementioned Atlassian billing systems in all regions. The outage lasted for 3 hours and 10 minutes and impacted the following products and services: [www.atlassian.com](http://www.atlassian.com) * Could not signup for new cloud accounts * Could not activate new products on existing cloud accounts * Could not create, view or pay for quotes [my.atlassian.com](http://my.atlassian.com) * Offline In-app billing admin UI for cloud accounts * Could not view/update billing details * Could not provide bill estimate * Could not activate new products or apps Marketplace * Could not activate or deactivate apps on existing cloud accounts * Vendors could not update their configuration or the configuration of their apps * Some delay in updating vendor sales reports during the time of the incident Bitbucket * Could not update billing details * Could not provide bill estimate ### **ROOT CAUSE** For reasons related to keeping our systems secure, passwords used for some of the Atlassian billing systems are rotated. However, the same passwords were used in other parts of the Atlassian billing infrastructure. This had the unintended side effect that it became impossible to create new nodes to handle increased traffic. Nodes that already were up and running kept functioning, but weren't able to handle the increased load. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that any outage impacts your productivity. We make every effort to keep all our systems up and running in a reliable and secure manner. Unfortunately, in this case, rotating passwords for security reasons had the unintended side effect of making our billing systems unavailable. As a high-priority action, we have separated the passwords being used in different services across the billing systems. Furthermore, we are undertaking a comprehensive program to modernize the security infrastructure for our billing systems, significantly reducing the need to use passwords. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Status: Postmortem
Impact: None | Started At: Aug. 2, 2023, 1:41 p.m.
Description: ### **SUMMARY** On July 25, 2023, between 16:29 UTC and 16:44 UTC, Atlassian customers were unable to access the Bitbucket Cloud website. This was caused by a code bug that made it to our production environment. The incident was detected immediately by our internal monitoring and fully resolved within 15 minutes by reverting the change. ### **IMPACT** Customers who were impacted were unable to access the [Bitbucket | Git solution for teams using Jira](http://bitbucket.org/) website during the duration of the incident. APIs, Bitbucket Pipelines, and Git over HTTPS and SSH were fully functional. ### **ROOT CAUSE** The incident was caused by a bug that made it into our production environment. This bug affected our ability to communicate with our caches and prevented some of our internal services from starting up to serve traffic to our website. This bug has been fixed and deployed to production. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating these types of incidents in the future and reduce recovery time: * Improve testing in non-production environments * Enhance monitoring around service deployments We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s availability. Thanks, Atlassian Customer Support
Status: Postmortem
Impact: Major | Started At: July 25, 2023, 4:47 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
