Codacy had 34 outages in the last 2 years totaling 12028h 35m of downtime — averaging 1.4 incidents per month.
There were 34 Codacy outages since December 11, 2025 totaling 12028h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
Aug 1, 2026, 15:23 UTC Investigating - We are investigating an issues that is causing slower analysis, results reporters and also impacting UI responsiveness.
Jul 23, 2026, 08:04 UTC Monitoring - We are currently monitoring an ongoing GitHub incident (https://www.githubstatus.com/incidents/zq3c1jst2vkq) affecting Actions, Issues, and Webhooks. Due to the impact on Webhooks, some repositories may experience delays in the start of analysis. We are tracking GitHub's status and will update this page as more information becomes available.
Jul 15, 2026, 09:52 UTC Monitoring - Between 08:35 and 09:45 UTC, customers may have experienced delays in analysis results being posted back to pull requests across all connected providers (GitHub, GitLab, Bitbucket). We identified the issue as a performance inefficiency in one of our backend processes. A mitigation has been applied, and we are now deploying a permanent fix. We apologize for any inconvenience this may have caused. Jul 15, 2026, 09:49 UTC Identified - Jul 15, 2026, 09:49 UTC Identified - We have identified an issue affecting the delivery of analysis results back to pull requests across all connected providers (GitHub, GitLab, Bitbucket). Customers may notice that analysis results are delayed in appearing on pull requests. Our team is actively investigating the root cause and working on a resolution. We will provide an update as soon as we have more information.
Jul 3, 2026, 08:43 UTC Scheduled - We will be carrying out scheduled maintenance in Production as part of ongoing improvements to our database infrastructure. During this maintenance window, although metrics shown for repositories and commits might be incomplete during the upgrade duration, Codacy will still be available.
Jul 1, 2026, 09:08 UTC Investigating - We are investigating a problem in our databases that is causing Codacy to become non responsive.
Jun 19, 2026, 13:34 UTC Identified - We have identified the cause of a degraded performance in Security and Risk management API
Jun 19, 2026, 06:05 UTC Scheduled - We will be carrying out scheduled maintenance in Production as part of ongoing improvements to our database infrastructure. During this maintenance window, Codacy will be unavailable. The UI, API, and all major platform features will be inaccessible, and no analyses will be detected or executed until the intervention is complete. We are sorry for the disruption and thank you for your patience and understanding.
Jun 15, 2026, 16:02 UTC Monitoring - GitHub is currently experiencing an incident affecting webhook delivery times. As a result, pull requests, commits, and their analysis may appear and start later than usual in Codacy. We are monitoring the situation and will update this page as GitHub resolves the issue. You can follow GitHub's incident status here: https://www.githubstatus.com/incidents/67w72l5v25x3
Jun 11, 2026, 11:02 UTC Identified - We identified a problem with the Analysis system, we are working on a mitigation.
Jun 4, 2026, 22:28 UTC Monitoring - We have mitigated an issue that was preventing analyses for GitHub-hosted repositories from starting. The issue began at approximately 17:00 UTC and was mitigated at approximately 22:15 UTC. This issue caused delays in detecting and processing new work for GitHub repositories, impacting analysis triggering. As a result, some analyses may have been delayed during this period. Our systems are now processing the backlog accumulated while the issue was ongoing. During this catch-up period, the platform will be operating under heavier-than-normal load, and analyses may continue to experience delays until the backlog has been fully cleared. We will continue to monitor the recovery and provide a further update once processing has returned to normal.
May 29, 2026, 08:59 UTC Scheduled - We will be upgrading the version of our Kubernetes cluster. The upgrade is estimated to take 5-10 minutes, with downtime associated to it. During this time, Codacy may present degraded performance overall.
May 27, 2026, 13:09 UTC Monitoring - We are aware of an ongoing GitHub incident affecting Pull Requests, Issues, Git Operations, and API Requests. Customers using Codacy with GitHub-hosted repositories may experience degraded performance or failures during analysis and other Git-dependent operations. This issue originates from GitHub's infrastructure and is currently under investigation by their team. We are monitoring the situation closely and will provide updates as more information becomes available. For details on the upstream incident, see GitHub's status page: https://www.githubstatus.com/incidents/xy1tt3hs572m We apologize for any inconvenience and will update this page when the issue is resolved.
May 27, 2026, 09:14 UTC Monitoring - We are aware of an ongoing GitLab incident affecting Git operations. Customers using Codacy with GitLab-hosted repositories may experience degraded performance or failures during analysis, commits, or other Git-dependent operations. This issue originates from GitLab's infrastructure and is being investigated by their Gitaly team. We are monitoring the situation closely and will provide updates as more information becomes available. For details on the upstream incident, see GitLab's status page: https://status.io/pages/incident/5b36dc6502d06804c08349f7/6a169dbf50c7630597c4d7ff We apologize for any inconvenience and will update this page when the issue is resolved.
May 19, 2026, 22:18 UTC Scheduled - We will be carrying out scheduled maintenance in production as part of ongoing improvements to our database infrastructure and data management. During this maintenance window, Codacy will be unavailable. The UI, API, and all major platform features will be inaccessible, and no analyses will be detected or executed until the intervention is complete. We are sorry for the disruption and thank you for your patience and understanding.
May 11, 2026, 09:05 UTC Monitoring - We are monitoring a GitLab service disruption (https://status.io/pages/incident/5b36dc6502d06804c08349f7/6a019654c45d27050d60be2d) that can impact Codacy analysis.
May 8, 2026, 08:12 UTC Monitoring - Ongoing Bitbucket incident (https://bitbucket.status.atlassian.com/incidents/hpkdy4vmq470) might result in degraded performance across several parts of Codacy for Bitbucket customers. Login, managing repositories, analysis discovery and analysis execution might be (or have been) impacted by the ongoing incident.
Apr 28, 2026, 22:39 UTC Identified - Apr 28, 2026, 22:38 UTC Identified - GitHub is experiencing degraded performance for Pull Requests, which in turn is affecting Codacy's PR analysis. https://www.githubstatus.com
Apr 28, 2026, 15:12 UTC Scheduled - We will do an upgrade to the version of the nodes used in our system to keep our system up-to-date. Running nodes at this time will not be affected, only nodes that are created past this upgrade will be affected. As such, no downtime is expected during this maintenance. Afterwards, we will be monitoring newly created nodes to verify the overall stability of the system.
Mar 19, 2026, 14:10 UTC Resolved - We identified and fixed a bug that affected issue reporting in Codacy between February 11, 2026 and March 19, 2026. During that period, some issues detected by analysis were not surfaced correctly in dashboards or pull request results. This may have caused some repositories to show fewer issues than expected and, in some cases, may have allowed pull requests to pass quality gates when they otherwise would have been blocked. The fix is now deployed. New analyses and re-analyses will now report issues correctly. As a result, some customers may see higher issue counts or different pull request outcomes going forward. Existing historical results are not automatically backfilled. More details here: https://codacy.slite.page/p/p9ZvJmbH3MPPS0/Codacy-underreported-issues-between-February-11-and-March-19-2026
Mar 5, 2026, 19:55 UTC Resolved - Mar 5, 2026, 17:12 UTC Identified - We are aware of a major outage reported by GitHub affecting GitHub Actions and GitHub Webhooks. As a result, some Codacy services that rely on GitHub integrations may be impacted, including workflows that depend on GitHub events or Actions triggers. We are currently monitoring the situation while GitHub investigates the incident. More information is available on the official GitHub status page: https://www.githubstatus.com/
Feb 12, 2026, 10:30 UTC Resolved - The performance issue affecting Vulnerability Detection has been resolved and analysis performance is back to normal. Any Vulnerability Detection failures that occurred between February 11, 2026 22:19 UTC and February 12, 2026 09:53 UTC will be automatically corrected on the next analysis run. No action is required. Feb 12, 2026, 09:59 UTC Monitoring - The fix to the performance issue has been deployed and we analysis performance is already improved. Some delays are to be expected for a short term while the systems catches up with queued jobs. Feb 12, 2026, 09:25 UTC Identified - We have identified and are deploying a fix to a performance issue in Vulnerability identification that is causing longer analysis times. We expect analysis to be back to normal performance in a short timeframe.