Codacy Outage History

Apr 18, 2026, 09:38 UTC Completed - The scheduled maintenance has been completed successfully, and Codacy is now fully available again. The intervention went according to plan, and the UI, API, and major platform features are back up. Analysis detection and execution have resumed. Thank you for your patience during this maintenance window. Apr 18, 2026, 08:28 UTC In Progress - Our scheduled maintenance window is about to begin. As previously communicated, Codacy will be unavailable during this intervention. The UI, API, and all major platform features will be inaccessible, and no analyses will be detected or executed until the maintenance is complete. We apologize for the disruption and thank you for your patience. Apr 15, 2026, 13:45 UTC Scheduled - We will be carrying out scheduled maintenance in production this Saturday 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. This maintenance is part of a broader effort that will require additional scheduled maintenance windows in the coming weeks and months. We are planning these interventions during low-demand periods wherever possible to reduce impact. We are sorry for the inconvenience and thank you for your patience and understanding.

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 12, 2026, 13:01 UTC Resolved - Mar 12, 2026, 09:15 UTC Monitoring - An ongoing Bitbucket Cloud incident (https://bitbucket.status.atlassian.com/incidents/l8hf15zcrvt0) may affect Codacy for Bitbucket-connected repositories, including the UI, API, and analysis workflows. We’ll share updates if needed.

Mar 11, 2026, 15:05 UTC Resolved - Mar 11, 2026, 14:51 UTC Identified - We have identified the likely cause of the authentication issues affecting the GitHub connector as the ongoing GitHub incident. We are seeing intermittent behaviour, with some login attempts succeeding, some failing with “Could not retrieve token to authenticate the account” or “Bad credentials,” and some succeeding on retry. We have also observed that clearing cookies or re-authenticating with GitHub may improve success in some cases. We are continuing to monitor the situation. Mar 11, 2026, 14:39 UTC Investigating - We are investigating an issue affecting authentication through the GitHub connector. Some users may be unable to log in or sign up and may see the message: “Could not retrieve token to authenticate the account.” We are actively working to identify the cause and will provide another update as soon as we have more information. This issue might be related with the ongoing GitHub incident https://www.githubstatus.com/incidents/zy1gjfc6x2z9.

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 26, 2026, 11:17 UTC Resolved - After monitoring we are not seeing any new issues related to coverage file-size and API Token header. Feb 24, 2026, 16:32 UTC Monitoring - We have now rolled out a fix intended to fully resolve this issue. We are monitoring the platform to confirm the fix is effective and that coverage report requests are processing normally. Feb 24, 2026, 12:10 UTC Identified - We identified an additional issue affecting a small percentage of coverage report requests that use a deprecated coverage API request format. In these requests, some authentication headers were being sent with underscores (`_`) instead of hyphens (`-`), which caused requests to fail with `404` responses. We deployed a mitigation at 11:57 UTC and are working on a permanent fix. This issue affected a very small percentage of coverage report requests. For background on the deprecated header format, see: https://docs.codacy.com/release-notes/cloud/cloud-2020-04-01-deprecating-http-headers-for-api-tokens/ Feb 21, 2026, 13:01 UTC Monitoring - We have deployed a mitigation and are monitoring its effectiveness for an issue that was causing some coverage file uploads larger than 1 MB to fail in Codacy (HTTP 413 error). The issue began around Feb 20, 2026 12:00 UTC and was mitigated on Feb 21, 2026 at 12:45 UTC. We are continuing to monitor to ensure coverage uploads are functioning normally.

Feb 13, 2026, 16:05 UTC Resolved - The long tail of failing cases have now been solved and the processing is more reliable for large repositories with large numbers of findings. Feb 13, 2026, 13:57 UTC Investigating - Remediation actions have improved processing for the majority of affected cases. Few remaining edge cases are under investigation. We will provide further updates as progress is confirmed. Feb 13, 2026, 12:34 UTC Identified - We have identified and implemented a mitigation to an additional contributing issue affecting timeliness for a subset of large repositories.Changes are being rolled out incrementally and monitored closely to validate impact. Further updates will follow as results are confirmed Feb 12, 2026, 16:35 UTC Investigating - SRM findings timeliness is back to normal for most old and all new findings. The exception is for a small groups of large repos with large numbers of findings that we still working on fully unblocking. Feb 12, 2026, 14:45 UTC Monitoring - Improvements have been rolled out and we are validating that the root cause is resolved. SRM findings ingestion is recovering and remaining delays should continue to reduce. Feb 12, 2026, 14:03 UTC Identified - We have deployed mitigations that partially restored ingestion of SRM findings, and we are processing the backlog. A subset of findings is still failing or taking significantly longer to process, which can cause newly generated findings to appear delayed on the SRM Dashboard. We will soon roll out an improvement aimed at fully restoring normal ingestion for all findings. Feb 12, 2026, 11:56 UTC Identified - We have identified the root cause of the issue and were able to roll out mitigating measures that resulted in ingestion of some SRM Findings being unblocked. We are now processing some of the findings backlog but there still ongoing investigation in order to unblock ingestion for all SRM Findings. Feb 12, 2026, 11:41 UTC Investigating - We continue investigating the root cause of the issue that is preventing new SRM finding from showing on SRM Dashboard. Feb 12, 2026, 10:35 UTC Investigating - We are investigating an issue that is preventing new SRM findings from being correctly processed and displayed in the SRM Dashboard.

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.

Feb 10, 2026, 09:18 UTC Resolved - The incident has been resolved on GitHub's side and the Codacy platform is no longer affected by their degraded performance. Feb 9, 2026, 16:32 UTC Identified - Feb 9, 2026, 16:30 UTC Identified - GitHub is experiencing degraded performance in it's API and some pages, which in turn is affecting Codacy's API and UI. https://www.githubstatus.com/

Feb 9, 2026, 16:30 UTC Resolved - Feb 9, 2026, 16:27 UTC Resolved - We found and mitigated the issue causing an increased error rate and UI failures. Feb 9, 2026, 14:06 UTC Monitoring - Feb 9, 2026, 13:31 UTC Identified - We have investigated and identified a problem with Codacy's API that is causing an increased error rate and UI failures.

Feb 9, 2026, 09:26 UTC Resolved - SRM module had no problems during the monitoring period. The incident is considered to be resolved. Feb 6, 2026, 09:25 UTC Monitoring - No further delays have been observed in the processing of Security Findings and SRM module is fully operational. We will continue to monitor. Feb 5, 2026, 18:17 UTC Investigating - We are investigating an issue which is causing Security Findings to take longer than usual to show up on our SRM dashboards.

Feb 4, 2026, 12:17 UTC Completed - Problems were found on our testing environments. To make sure we have a stable migration, we will proceed to further testing and delay the maintenance that was scheduled for today. Feb 4, 2026, 11:43 UTC Scheduled - Feb 4, 2026, 11:06 UTC Scheduled - We are migrating our NGINX Ingress to the newly supported Gateway API. So during this time, we will be testing the routing. As a result of these changes, some endpoints and views might be unavailable for a short period of time until the routes are fully migrated.

Feb 4, 2026, 10:15 UTC Resolved - Since rolling out the fix we haven seen any further service degradation. Feb 3, 2026, 15:48 UTC Monitoring - The rolled out fix was successful and analysis performance is now back to normal. We will keep closely monitoring performance throughout the day. Feb 3, 2026, 15:14 UTC Monitoring - We have identified and deployed a fix for the problem in the analysis pipeline. We are currently monitoring the system. Feb 3, 2026, 13:35 UTC Investigating - We are still investigation and trying to mitigate abnormal load being generated by analysis jobs that is preventing new analysis from starting and performing analysis in a timely manner. Feb 3, 2026, 13:25 UTC Investigating - We are investigating abnormal load in our analysis systems that is causing the delays. Feb 3, 2026, 13:05 UTC Investigating - We are investigating a spike in analysis processing time resulting in analysis jobs queuing.