Codacy incident
Bitbucket Cloud Incident - Potential Degraded Performance
Resolved after 2 hours 40 minutes, on November 11, 2025.
As of 19:35 UTC Bitbucket incident has been marked as resolved and we've receiving webhooks at a normal rate.
Update timeline
- investigating Nov 11, 2025, 05:11 PM UTC
Investigating the impact of ongoing Bitbucket incident (https://bitbucket.status.atlassian.com/incidents/xwqvgfv2wfqw) for users using it's git and repository systems
- identified Nov 11, 2025, 05:20 PM UTC
We have confirmed that activity webhooks that should be sent by Bitbucket to trigger analysis on Codacy are not being sent. While incident is not mitigated and Codacy won't be notified of new items (PRs and Commits) to resulting in analysis not starting and PRs and Commits not showing in Codacy's UI. Once the issue is mitigated, activity (new commits, updated PRs) on affected repositories should bring Codacy back to sync with Bitbucket status.
- resolved Nov 11, 2025, 07:52 PM UTC
As of 19:35 UTC Bitbucket incident has been marked as resolved and we've receiving webhooks at a normal rate.
Your product runs on more than Codacy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services