Bitbucket reported this critical-impact incident on its official status page on Dec 27, 2025, 04:42 UTC. It was resolved after 38 min.
Right now Bitbucket is operational. Live Bitbucket status →
### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS certificates used by Atlassian’s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions. All impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began. ### IMPACT During the impact window, customers experienced: * **Outbound product email failures** \(notifications and other product emails did not send\). * **Identity and account flow failures** where emails were required \(e.g. sign‑ups, password resets, one‑time‑password / step‑up challenges\). * **Jira and Confluence mobile pu
We have successfully mitigated the incident and all affected services are now fully operational. Our teams have verified that normal functionality has been restored across all areas. Thank you for your patience and understanding while we worked to resolve this issue.
We have taken steps to mitigate the issue and are seeing recovery in the affected services. Our teams will continue to closely monitor the situation and are actively working to confirm that all services are fully restored. We will provide further updates as we make additional progress.
Our 5-minute checks didn't record a change in Bitbucket's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Bitbucket reported 3 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 28m. See Bitbucket's uptime and incident history