Codacy Outage History

Codacy is up right now

Pingoru has recorded 236 incidents for Codacy: 58 in the last 12 months and 7 in the last 90 days.

Source: status.codacy.com

236incidents recorded
58last 12 months
7last 90 days
17 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Codacy in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026549 of 720 (7%)
May 20267147 of 744 (20%)
June 20267155 of 720 (21%)
July 202645 of 744 (1%)
August 2026334 of 744 (5%)
September 2026210 of 720 (1%)
October 202622 of 526 (0%)

Incidents, newest first

Minor March 11, 2026 Issues authenticating with GitHub 26m [ Status] Incident History service

Started Mar 11, 2026, 02:39 PM UTC· resolved Mar 11, 2026, 03:05 PM UTC

  1. investigating Mar 11, 2026, 02:39 PM UTC

    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.

  2. resolved Mar 11, 2026, 02:39 PM UTC

    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.

  3. investigating Mar 11, 2026, 02:39 PM UTC

    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.

  4. identified Mar 11, 2026, 02:51 PM UTC

    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.

  5. resolved Mar 11, 2026, 03:05 PM UTC

    Resolved

Read the full incident report →

Minor March 5, 2026 Major Outage on GitHub Actions and GitHub Webhooks 2h 42m [ Status] Incident History service

Started Mar 05, 2026, 05:12 PM UTC· resolved Mar 05, 2026, 07:55 PM UTC

  1. investigating Mar 05, 2026, 05:12 PM UTC

    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/

  2. resolved Mar 05, 2026, 05:12 PM UTC

    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/

  3. identified Mar 05, 2026, 05:12 PM UTC

    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/

  4. resolved Mar 05, 2026, 07:55 PM UTC

    Resolved

Read the full incident report →

Minor February 21, 2026 Coverage uploads failing for files larger than 1 MB 4d 22h [ Status] Incident History service

Started Feb 21, 2026, 01:01 PM UTC· resolved Feb 26, 2026, 11:17 AM UTC

  1. investigating Feb 21, 2026, 01:01 PM UTC

    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.

  2. resolved Feb 21, 2026, 01:01 PM UTC

    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.

  3. monitoring Feb 21, 2026, 01:01 PM UTC

    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.

  4. identified Feb 24, 2026, 12:10 PM UTC

    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/

  5. monitoring Feb 24, 2026, 04:32 PM UTC

    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.

  6. resolved Feb 26, 2026, 11:17 AM UTC

    After monitoring we are not seeing any new issues related to coverage file-size and API Token header.

Read the full incident report →

Minor February 12, 2026 New SRM findings not showing on SRM Dashboard 1d 5h [ Status] Incident History service

Started Feb 12, 2026, 10:35 AM UTC· resolved Feb 13, 2026, 04:05 PM UTC

  1. investigating Feb 12, 2026, 10:35 AM UTC

    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.

  2. resolved Feb 12, 2026, 10:35 AM UTC

    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.

  3. investigating Feb 12, 2026, 10:35 AM UTC

    We are investigating an issue that is preventing new SRM findings from being correctly processed and displayed in the SRM Dashboard.

  4. investigating Feb 12, 2026, 11:41 AM UTC

    We continue investigating the root cause of the issue that is preventing new SRM finding from showing on SRM Dashboard.

  5. identified Feb 12, 2026, 11:56 AM UTC

    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.

  6. identified Feb 12, 2026, 02:03 PM UTC

    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.

  7. monitoring Feb 12, 2026, 02:45 PM UTC

    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.

  8. investigating Feb 12, 2026, 04:35 PM UTC

    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.

  9. identified Feb 13, 2026, 12:34 PM UTC

    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

  10. investigating Feb 13, 2026, 01:57 PM UTC

    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.

  11. resolved Feb 13, 2026, 04:05 PM UTC

    The long tail of failing cases have now been solved and the processing is more reliable for large repositories with large numbers of findings.

Read the full incident report →

Minor February 12, 2026 Performance issues in Vulnerability detection tooling leading to longer analysis times 1h 4m [ Status] Incident History service

Started Feb 12, 2026, 09:25 AM UTC· resolved Feb 12, 2026, 10:30 AM UTC

  1. investigating Feb 12, 2026, 09:25 AM UTC

    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.

  2. resolved Feb 12, 2026, 09:25 AM UTC

    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.

  3. identified Feb 12, 2026, 09:25 AM UTC

    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.

  4. monitoring Feb 12, 2026, 09:59 AM UTC

    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.

  5. resolved Feb 12, 2026, 10:30 AM UTC

    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.

Read the full incident report →

Minor February 9, 2026 Increased error rate in API 2h 58m [ Status] Incident History service

Started Feb 09, 2026, 01:31 PM UTC· resolved Feb 09, 2026, 04:30 PM UTC

  1. investigating Feb 09, 2026, 01:31 PM UTC

    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.

  2. resolved Feb 09, 2026, 01:31 PM UTC

    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.

  3. identified Feb 09, 2026, 01:31 PM UTC

    We have investigated and identified a problem with Codacy's API that is causing an increased error rate and UI failures.

  4. monitoring Feb 09, 2026, 02:06 PM UTC

    Monitoring

  5. resolved Feb 09, 2026, 04:27 PM UTC

    We found and mitigated the issue causing an increased error rate and UI failures.

  6. resolved Feb 09, 2026, 04:30 PM UTC

    Resolved

Read the full incident report →

Minor February 5, 2026 Delays in the SRM tabs 3d 15h [ Status] Incident History service

Started Feb 05, 2026, 06:17 PM UTC· resolved Feb 09, 2026, 09:26 AM UTC

  1. investigating Feb 05, 2026, 06:17 PM UTC

    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.

  2. resolved Feb 05, 2026, 06:17 PM UTC

    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.

  3. investigating Feb 05, 2026, 06:17 PM UTC

    We are investigating an issue which is causing Security Findings to take longer than usual to show up on our SRM dashboards.

  4. monitoring Feb 06, 2026, 09:25 AM UTC

    No further delays have been observed in the processing of Security Findings and SRM module is fully operational. We will continue to monitor.

  5. resolved Feb 09, 2026, 09:26 AM UTC

    SRM module had no problems during the monitoring period. The incident is considered to be resolved.

Read the full incident report →

Minor February 4, 2026 Cluster Maintenance –

Started Feb 04, 2026, 11:06 AM UTC· resolved Feb 04, 2026, 11:06 AM UTC

  1. resolved Feb 04, 2026, 11:06 AM UTC

    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.

Read the full incident report →

Minor February 3, 2026 Delays starting analysis and finishing ongoing analysis 21h 10m [ Status] Incident History service

Started Feb 03, 2026, 01:05 PM UTC· resolved Feb 04, 2026, 10:15 AM UTC

  1. investigating Feb 03, 2026, 01:05 PM UTC

    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.

  2. resolved Feb 03, 2026, 01:05 PM UTC

    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.

  3. investigating Feb 03, 2026, 01:05 PM UTC

    We are investigating a spike in analysis processing time resulting in analysis jobs queuing.

  4. investigating Feb 03, 2026, 01:25 PM UTC

    We are investigating abnormal load in our analysis systems that is causing the delays.

  5. investigating Feb 03, 2026, 01:35 PM UTC

    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.

  6. monitoring Feb 03, 2026, 03:14 PM UTC

    We have identified and deployed a fix for the problem in the analysis pipeline. We are currently monitoring the system.

  7. monitoring Feb 03, 2026, 03:48 PM UTC

    The rolled out fix was successful and analysis performance is now back to normal. We will keep closely monitoring performance throughout the day.

  8. resolved Feb 04, 2026, 10:15 AM UTC

    Since rolling out the fix we haven seen any further service degradation.

Read the full incident report →

Minor January 15, 2026 Degraded performance due to Github Incident 22h 38m [ Status] Incident History service

Started Jan 15, 2026, 05:19 PM UTC· resolved Jan 16, 2026, 03:58 PM UTC

  1. investigating Jan 15, 2026, 05:19 PM UTC

    Jan 16, 2026, 15:58 UTC Resolved - Jan 15, 2026, 19:04 UTC Resolved - Jan 15, 2026, 17:19 UTC Monitoring - We are monitoring the impact of an ongoing Github incident (https://www.githubstatus.com/incidents/q987xpbqjbpl) that is resulting in degraded analysis and experience performance in Codacy. Particularly we've experienced moments when logging in to Codacy via Github connecter was impossible.

  2. resolved Jan 15, 2026, 05:19 PM UTC

    Jan 16, 2026, 15:58 UTC Resolved - Jan 15, 2026, 19:04 UTC Resolved - Jan 15, 2026, 17:19 UTC Monitoring - We are monitoring the impact of an ongoing Github incident (https://www.githubstatus.com/incidents/q987xpbqjbpl) that is resulting in degraded analysis and experience performance in Codacy. Particularly we've experienced moments when logging in to Codacy via Github connecter was impossible.

  3. monitoring Jan 15, 2026, 05:19 PM UTC

    We are monitoring the impact of an ongoing Github incident (https://www.githubstatus.com/incidents/q987xpbqjbpl) that is resulting in degraded analysis and experience performance in Codacy. Particularly we've experienced moments when logging in to Codacy via Github connecter was impossible.

  4. resolved Jan 15, 2026, 07:04 PM UTC

    Resolved

  5. resolved Jan 16, 2026, 03:58 PM UTC

    Resolved

Read the full incident report →

Minor January 7, 2026 Timeout loading dependencies in Security and risk management dashboard 1d 7h [ Status] Incident History service

Started Jan 07, 2026, 10:16 AM UTC· resolved Jan 08, 2026, 05:55 PM UTC

  1. investigating Jan 07, 2026, 10:16 AM UTC

    Jan 8, 2026, 17:55 UTC Resolved - This incident has been fully resolved. The affected query was improved and is now functioning as expected, and all security dependencies functionalities are fully operational. We will continue to closely monitor the system and implement minor enhancements to further improve reliability and performance. Jan 8, 2026, 10:04 UTC Monitoring - Security dependency functionality is now operational. Team is working on further optimizations identified during the investigation and monitoring already deployed improvements. Jan 7, 2026, 16:35 UTC Monitoring - The inefficient query has been optimized, and the fix has been deployed. We are now monitoring the system to ensure performance remains stable. Jan 7, 2026, 14:28 UTC Investigating - We have identified the cause of the slowdown as an inefficient database query. A fix is in progress, and we are working to restore normal performance. Jan 7, 2026, 11:13 UTC Investigating - We have identified a performance degradation affecting one of our databases. Our team is actively investigating the root cause and working to restore normal performance. Jan 7, 2026, 10:16 UTC Investigating - We are investigating timeouts loading the dependencies tab in the Security and risk management dashboard.

  2. resolved Jan 07, 2026, 10:16 AM UTC

    Jan 8, 2026, 17:55 UTC Resolved - This incident has been fully resolved. The affected query was improved and is now functioning as expected, and all security dependencies functionalities are fully operational. We will continue to closely monitor the system and implement minor enhancements to further improve reliability and performance. Jan 8, 2026, 10:04 UTC Monitoring - Security dependency functionality is now operational. Team is working on further optimizations identified during the investigation and monitoring already deployed improvements. Jan 7, 2026, 16:35 UTC Monitoring - The inefficient query has been optimized, and the fix has been deployed. We are now monitoring the system to ensure performance remains stable. Jan 7, 2026, 14:28 UTC Investigating - We have identified the cause of the slowdown as an inefficient database query. A fix is in progress, and we are working to restore normal performance. Jan 7, 2026, 11:13 UTC Investigating - We have identified a performance degradation affecting one of our databases. Our team is actively investigating the root cause and working to restore normal performance. Jan 7, 2026, 10:16 UTC Investigating - We are investigating timeouts loading the dependencies tab in the Security and risk management dashboard.

  3. investigating Jan 07, 2026, 10:16 AM UTC

    We are investigating timeouts loading the dependencies tab in the Security and risk management dashboard.

  4. investigating Jan 07, 2026, 11:13 AM UTC

    We have identified a performance degradation affecting one of our databases. Our team is actively investigating the root cause and working to restore normal performance.

  5. investigating Jan 07, 2026, 02:28 PM UTC

    We have identified the cause of the slowdown as an inefficient database query. A fix is in progress, and we are working to restore normal performance.

  6. monitoring Jan 07, 2026, 04:35 PM UTC

    The inefficient query has been optimized, and the fix has been deployed. We are now monitoring the system to ensure performance remains stable.

  7. monitoring Jan 08, 2026, 10:04 AM UTC

    Security dependency functionality is now operational. Team is working on further optimizations identified during the investigation and monitoring already deployed improvements.

  8. resolved Jan 08, 2026, 05:55 PM UTC

    This incident has been fully resolved. The affected query was improved and is now functioning as expected, and all security dependencies functionalities are fully operational. We will continue to closely monitor the system and implement minor enhancements to further improve reliability and performance.

Read the full incident report →

Minor December 15, 2025 Cache Systems Maintenance –

Started Dec 15, 2025, 03:30 PM UTC· resolved Dec 15, 2025, 03:30 PM UTC

  1. resolved Dec 15, 2025, 03:30 PM UTC

    Dec 15, 2025, 22:33 UTC Completed - Updates went through as expected without any downtime or system impact. Dec 15, 2025, 15:30 UTC Scheduled - We'll be performing an update to our cache systems. We expected minimal to no impact on overall service availability.

Read the full incident report →

Minor December 11, 2025 GitHub running with degraded performance 2h 12m

Started Dec 11, 2025, 04:31 PM UTC· resolved Dec 11, 2025, 06:44 PM UTC

  1. resolved Dec 11, 2025, 04:31 PM UTC

    Dec 11, 2025, 18:44 UTC Resolved - Incident is marked as resolved at the source. Dec 11, 2025, 16:39 UTC Identified - Dec 11, 2025, 16:31 UTC Identified - Dec 11, 2025, 16:31 UTC Investigating - Github is experiencing an incident (https://www.githubstatus.com/incidents/xntfc1fz5rfb) that is affecting the performance of Codespaces, Copilot, Git Operations, Packages, Pages, Pull Requests and Webhooks. This may result in PRs, Commits and their analysis to show up and start later than usual in Codacy.

  2. investigating Dec 11, 2025, 04:31 PM UTC

    Github is experiencing an incident (https://www.githubstatus.com/incidents/xntfc1fz5rfb) that is affecting the performance of Codespaces, Copilot, Git Operations, Packages, Pages, Pull Requests and Webhooks. This may result in PRs, Commits and their analysis to show up and start later than usual in Codacy.

  3. identified Dec 11, 2025, 04:31 PM UTC

    Identified

  4. identified Dec 11, 2025, 04:39 PM UTC

    Identified

  5. resolved Dec 11, 2025, 06:44 PM UTC

    Incident is marked as resolved at the source.

Read the full incident report →

Minor December 2, 2025 Increased tool time outs for analysis 2d 22h

Started Dec 02, 2025, 10:57 AM UTC· resolved Dec 05, 2025, 09:07 AM UTC

  1. investigating Dec 02, 2025, 10:57 AM UTC

    We are investigating a recent increase in analysis tool timeouts, which is leading to higher tool-failure rates and missing results.

  2. investigating Dec 02, 2025, 12:04 PM UTC

    We are still investigating the root cause of the frequent timeouts starting up analysis tools.

  3. monitoring Dec 02, 2025, 01:23 PM UTC

    The source of the timeouts was traced to an underlying infrastructure issue that we have mitigated. We will continue monitoring and work to fully understand the root cause of the issue.

  4. resolved Dec 05, 2025, 09:07 AM UTC

    Resolved

Read the full incident report →

Minor November 19, 2025 Github incident with Git Operations resulting in failed analyses 1h 22m

Started Nov 19, 2025, 10:26 AM UTC· resolved Nov 19, 2025, 11:49 AM UTC

  1. investigating Nov 19, 2025, 10:26 AM UTC

    GitHub has resolved the incident that lasted from 20:30 UTC to 22:UTC (https://www.githubstatus.com/incidents/5q7nmlxz30sk). That incident caused a few repositories in Codacy to be in a state where it is not detecting new analysis (You'll see a banner at the top of the repository page, "We no longer have access to this repository. Please contact support"). We are fully identifying the affected repos and looking to bring them up to normal behaviour.

  2. investigating Nov 19, 2025, 10:30 AM UTC

    Investigating

  3. resolved Nov 19, 2025, 11:49 AM UTC

    We have successfully identified all affected repositories and restored them to normal status.

  4. resolved Nov 19, 2025, 11:49 AM UTC

    We have successfully identified all affected repositories and restored them to normal status.

Read the full incident report →

Minor November 12, 2025 Github incident with webhooks resulting in delayed activity in Codacy 2h 54m

Started Nov 12, 2025, 02:48 PM UTC· resolved Nov 12, 2025, 05:43 PM UTC

  1. identified Nov 12, 2025, 02:48 PM UTC

    Github is experiencing an incident (https://www.githubstatus.com/incidents/l0brgg302bf5) that is causing webhooks to be delayed. This will result in PRs, Commits and their analysis to show up and start later than usual in Codacy.

  2. resolved Nov 12, 2025, 05:43 PM UTC

    Github has considered the incident resolved.

Read the full incident report →

Minor November 11, 2025 Bitbucket Cloud Incident - Potential Degraded Performance 2h 40m

Started Nov 11, 2025, 05:11 PM UTC· resolved Nov 11, 2025, 07:52 PM UTC

  1. 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

  2. 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.

  3. 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.

Read the full incident report →

Minor October 24, 2025 GitHub degraded performance for git operations over ssh 5d 21h

Started Oct 24, 2025, 09:59 AM UTC· resolved Oct 30, 2025, 07:57 AM UTC

  1. investigating Oct 24, 2025, 09:59 AM UTC

    Incident in GitHub might affect git operations performed by Codacy. https://www.githubstatus.com/incidents/n7hf73qtpz2l

  2. monitoring Oct 24, 2025, 10:14 AM UTC

    GitHub is currently experiencing an incident affecting SSH connections (see GitHub status: https://www.githubstatus.com/incidents/n7hf73qtpz2l). Codacy services are not impacted, as we don’t rely on SSH for our GitHub integrations. All Codacy features remain fully operational.

  3. monitoring Oct 24, 2025, 10:16 AM UTC

    Monitoring

  4. resolved Oct 24, 2025, 10:39 AM UTC

    GitHub incident was resolved upstream.

  5. resolved Oct 30, 2025, 07:57 AM UTC

    Resolved

Read the full incident report →

Minor October 23, 2025 Infrastructure failure resulted in Codacy unavailability 6h 23m

Started Oct 23, 2025, 08:53 AM UTC· resolved Oct 23, 2025, 03:17 PM UTC

  1. investigating Oct 23, 2025, 08:53 AM UTC

    We are investigating infrastructure issues resulting in codacy UI not being available.

  2. investigating Oct 23, 2025, 09:04 AM UTC

    We are currently investigating a failure in Codacy's infrastructure, that starting from 8:45 UTC onwards is causing failures that prevent Codacy's system to be available. This is an application wide failure that prevent App and API from correctly running and therefore also prevents new analysis from being detected.

  3. identified Oct 23, 2025, 09:22 AM UTC

    We are working to re-establish a healthy state to our infrastructure. App and API have availability improvements but still with degraded performance.

  4. monitoring Oct 23, 2025, 09:47 AM UTC

    By 9:20 UTC infrastructure failures had been mitigated and all systems are now back to normal performance and availability. We will keep monitoring our infrastructure and work on fully understanding and preventing further occurrences of the same issue. During the incident, due to API unavailability, new analysis were not triggered, and PRs/Commits might be missing in Codacy's UI. New activity on affected repositories will solve the issue.

  5. resolved Oct 23, 2025, 03:17 PM UTC

    Due to an infrastructure misconfigurations applied at 08:44:48 UTC essential components of Codacy's system became unable to spawn resulting in complete unavailability. Once the origin of the issue was identified configuration was promptly reverted to a stable version and by 09:19:00 UTC system was back to normal performance and availability. We have been monitoring the behaviour of our system since then and can consider the issue fully resolved.

Read the full incident report →

Minor October 20, 2025 AWS Incident may result in degraded performance 23h 14m

Started Oct 20, 2025, 09:29 AM UTC· resolved Oct 21, 2025, 08:44 AM UTC

  1. monitoring Oct 20, 2025, 09:29 AM UTC

    AWS is experiencing an incident (https://health.aws.amazon.com/health/status) affecting the US-EAST-1 region. This incident can have branching impact that affect some git providers (specifically Bitbucket) and if not contained can end up affecting Codacy. We are monitoring the situation and haven't seen a significant impact in Codacy's systems.

  2. resolved Oct 21, 2025, 08:44 AM UTC

    Resolved

Read the full incident report →

Minor October 9, 2025 Github incident with webhooks resulting in Codacy not being notified of new activity 2h 5m

Started Oct 09, 2025, 03:12 PM UTC· resolved Oct 09, 2025, 05:17 PM UTC

  1. identified Oct 09, 2025, 03:12 PM UTC

    Starting around 14:35 UTC we are seeing an abnormally low number of received webhooks from Github. This drop in number of received webhooks is related to "Incident with Webhooks https://www.githubstatus.com/incidents/k7bhmjkblcwp". This results in analysis not being started in Codacy until Github mitigates or fixes the incident. We'll keep updating as Github releases more information.

  2. monitoring Oct 09, 2025, 04:00 PM UTC

    Github's performance seems to be back to normal levels and we are receiving normal numbers of webhooks and performing git operations without noticeable delays. During the duration of Github's incident we did not receive the webhooks necessary to trigger new analysis. New commits might be needed if PRs haven't been analysed.

  3. resolved Oct 09, 2025, 05:17 PM UTC

    Incident is marked as resolved on Github side and we are seeing no additional impact.

Read the full incident report →

Minor September 30, 2025 New analyses fail to start 1h 17m

Started Sep 30, 2025, 01:26 PM UTC· resolved Sep 30, 2025, 02:44 PM UTC

  1. identified Sep 30, 2025, 01:26 PM UTC

    Identified

  2. identified Sep 30, 2025, 01:27 PM UTC

    Identified

  3. monitoring Sep 30, 2025, 01:28 PM UTC

    Monitoring

  4. resolved Sep 30, 2025, 02:44 PM UTC

    Resolved

Read the full incident report →

Minor September 15, 2025 Degraded performance in Codacy API - search or get PR endpoints 3h 10m

Started Sep 15, 2025, 11:16 AM UTC· resolved Sep 15, 2025, 02:26 PM UTC

  1. investigating Sep 15, 2025, 11:16 AM UTC

    The Codacy API endpoints to search or get a Pull Request are experiencing performance degradations.

  2. identified Sep 15, 2025, 11:50 AM UTC

    The problem was identified and is being mitigated.

  3. identified Sep 15, 2025, 12:39 PM UTC

    We have identified problems in the Coverage pipeline as the source of these problems, which is causing an outage on the Coverage pipeline and some related APIs.

  4. monitoring Sep 15, 2025, 01:10 PM UTC

    We have applied mitigation measures and are monitoring the system.

  5. resolved Sep 15, 2025, 02:26 PM UTC

    The mitigation strategy worked in full and the problem is now resolved.

Read the full incident report →

Minor August 28, 2025 New analysis not triggering 3d 18h

Started Aug 28, 2025, 02:40 PM UTC· resolved Sep 01, 2025, 08:57 AM UTC

  1. investigating Aug 28, 2025, 02:40 PM UTC

    We're investigating increased queue times for analysis.

  2. investigating Aug 28, 2025, 02:54 PM UTC

    We're investigating increased queue times for analysis.

  3. investigating Aug 28, 2025, 02:55 PM UTC

    Investigating

  4. investigating Aug 28, 2025, 02:57 PM UTC

    We are investigating an issue that is preventing all analysis from starting.

  5. identified Aug 28, 2025, 03:34 PM UTC

    We have identified the source of the problem and we are working to fully mitigate the problem. In the meanwhile some Analysis are already being processed at a slower than usual rate.

  6. monitoring Aug 28, 2025, 04:29 PM UTC

    System has caught up with the backlog of analysis and analysis are expected to trigger in a timely manner. We are still digging deeper in fully understanding the source of the problem and are monitoring analysis activity.

  7. monitoring Aug 28, 2025, 04:41 PM UTC

    System seems to be performing up to expectation. We are going to keep monitoring analysis performance.

  8. resolved Sep 01, 2025, 08:57 AM UTC

    Resolved

Read the full incident report →

Minor August 18, 2025 Failures to trigger specific tools resulting in Analysis Delays 2h 30m

Started Aug 18, 2025, 08:34 AM UTC· resolved Aug 18, 2025, 11:04 AM UTC

  1. identified Aug 18, 2025, 08:34 AM UTC

    We are experiencing backed up analysis jobs and overall analysis delays caused by failures to trigger some analysis tools. We have identified the issue and are working on a fix.

  2. monitoring Aug 18, 2025, 10:04 AM UTC

    A fix has been rolled out to production a while ago and analysis are now triggering as expected and the queue of backed off jobs is decreasing. Delays for some analysis results are still to be expected while the system catches up.

  3. resolved Aug 18, 2025, 11:04 AM UTC

    Resolved

Read the full incident report →