Codacy Outage History

Started Oct 24, 2026, 08:22 AM UTC· resolved Oct 26, 2026, 09:27 PM UTC

1. investigating Oct 24, 2026, 08:22 AM UTC

   We’re investigating an issue where users can’t log in with GitHub, and operations involving GitHub organizations may fail.

2. identified Oct 24, 2026, 09:20 AM UTC

   We have identified the source of the issue and are rolling out a fix.

3. monitoring Oct 24, 2026, 09:30 AM UTC

   We have rolled out the fix and are seeing that logins and API requests are now working as expected. We are monitoring.

4. investigating Oct 24, 2026, 09:42 AM UTC

   We have identified further problems and are investigating.

5. investigating Oct 24, 2026, 10:01 AM UTC

   We are still investigating the root cause of failures to login.

6. identified Oct 24, 2026, 11:22 AM UTC

   We are still working to restore reliable GitHub logins and API access. Some users may be unable to log in with GitHub, and some API requests and operations involving GitHub organizations may fail intermittently. Starting at approximately 21:45 WEST on Oct 23, after an unannounced change on GitHub's side, responses from GitHub's sign-in service became larger than a size limit in our platform. This prevented our platform from completing GitHub logins and from renewing the GitHub access that many API requests rely on. We rolled out a fix for this at 10:30 WEST on Oct 24, raising that limit with extra headroom. However, many GitHub authorizations could not be renewed while the issue was ongoing and were left in an inconsistent state. Restoring them has caused GitHub to repeatedly throttle requests from our platform, which is still preventing some logins and causing API requests to fail authentication. We are working on changes to reduce these requests and resolve the throttling.

7. identified Oct 24, 2026, 11:54 AM UTC

   We continue working to resolve the GitHub throttling affecting logins and API requests. Some GitHub authorizations could not be renewed during the incident and will need to be restored by logging in again: if you are affected, please log out of Codacy, log in again at app.codacy.com using "Log in with GitHub", and approve the authorization if GitHub asks for it. This may particularly affect service accounts used only through the Codacy API, for example in CI pipelines and scripts, since they don't log in regularly. Their requests may fail with 404 Not Found errors (such as "Could not find repository") or authentication errors even though the repository exists and the account still has access. To restore them, log in once to the Codacy web app as that service account's GitHub user and authorize Codacy when prompted. Existing Codacy API tokens remain valid and don't need to be changed. If problems persist after logging in again, please contact our support team.

8. identified Oct 24, 2026, 11:55 AM UTC

   Identified

9. monitoring Oct 24, 2026, 12:34 PM UTC

   We have rolled out mitigation measures to prevent GitHub throttling. We are monitoring the situation closely. Some GitHub authorizations could not be renewed during the incident and must be restored by logging in again through the Codacy web app: if you are still affected, please log out of Codacy, log in again at app.codacy.com using "Log in with GitHub", and approve the authorization if GitHub asks for it. This is especially important for service accounts used only through the Codacy API, for example in CI pipelines and scripts, whose requests may keep failing with 404 Not Found errors (such as "Could not find repository") or authentication errors until someone logs in once to the Codacy web app as that service account's GitHub user and authorizes Codacy. Existing Codacy API tokens remain valid and don't need to be changed. If problems persist after logging in again, please contact our support team.

10. monitoring Oct 26, 2026, 10:05 AM UTC

    Monitoring

Read the full incident report →

Started Oct 21, 2026, 01:41 PM UTC· resolved Oct 21, 2026, 02:35 PM UTC

1. investigating Oct 21, 2026, 01:41 PM UTC

   We are investigating a failure that is resulting in new analysis not starting and PR checks to not be cleared.

2. identified Oct 21, 2026, 01:52 PM UTC

   We have identified the root cause of the problem and have rolled out mitigations measures. No analysis were lost and we are now working through the accumulated backlog.

3. monitoring Oct 21, 2026, 02:00 PM UTC

   We are monitoring as the analysis jobs queue backlog is being processed. Progress is happening at a steady pace and root cause of issue seems to have been fixed. We'll keep monitoring and will update once normal analysis backlog is processed and analysis times are fully back to normal values.

Read the full incident report →

Started Oct 19, 2026, 09:39 AM UTC· resolved Oct 19, 2026, 10:37 AM UTC

1. investigating Oct 19, 2026, 09:39 AM UTC

   We had an issue on a internal component for the analysis configuration. We are monitoring the service and restoring the usual speed

2. monitoring Oct 19, 2026, 10:09 AM UTC

   We identified and fixed the underlying problem

3. resolved Oct 19, 2026, 10:37 AM UTC

   Resolved

Read the full incident report →

Started Sep 28, 2026, 09:13 AM UTC· resolved Sep 28, 2026, 04:01 PM UTC

1. monitoring Sep 28, 2026, 09:13 AM UTC

   Sep 28, 2026, 09:13 UTC Investigating - We are currently observing delays in analysis processing. Some analyses may take longer than usual to complete, and in some cases analysis tools may time out, which means results from those tools may be missing for the affected commits or pull requests. Our team is actively investigating and working to restore normal processing times. Analyses already queued are expected to complete once processing recovers, and no action is needed on your side at this time.

2. investigating Sep 28, 2026, 09:13 AM UTC

   We are currently observing delays in analysis processing. Some analyses may take longer than usual to complete, and in some cases analysis tools may time out, which means results from those tools may be missing for the affected commits or pull requests. Our team is actively investigating and working to restore normal processing times. Analyses already queued are expected to complete once processing recovers, and no action is needed on your side at this time.

3. investigating Sep 28, 2026, 09:45 AM UTC

   We have applied mitigation measures that have improved analysis processing times, and analyses are now completing closer to normal durations. Some analysis tools are still timing out in a subset of analyses, which means results from those tools may be missing for the affected commits or pull requests. Our team continues to investigate in order to implement measures that mitigate the cause of these timeouts.

4. monitoring Sep 28, 2026, 11:09 AM UTC

   We have deployed a fix that addresses the analysis tool timeouts, and we are seeing a significant improvement in analysis success rates and processing times. We will continue to monitor closely to confirm that analysis processing is fully back to normal. If any of your commits or pull requests are missing results from the affected period, you can reanalyze them to get complete results.

5. resolved Sep 28, 2026, 04:01 PM UTC

   Resolved

Read the full incident report →

Started Sep 25, 2026, 03:27 PM UTC· resolved Sep 25, 2026, 06:25 PM UTC

1. monitoring Sep 25, 2026, 03:27 PM UTC

   Sep 25, 2026, 15:27 UTC Identified - We're currently experiencing higher than normal load on our platform, which is causing analyses to take longer than usual to complete. New commits and pull requests are still being analyzed, but results may appear later than expected. Our team is actively working to restore normal processing times, and we'll share an update as soon as we have more information.

2. identified Sep 25, 2026, 03:27 PM UTC

   We're currently experiencing higher than normal load on our platform, which is causing analyses to take longer than usual to complete. New commits and pull requests are still being analyzed, but results may appear later than expected. Our team is actively working to restore normal processing times, and we'll share an update as soon as we have more information.

3. monitoring Sep 25, 2026, 04:15 PM UTC

   We've taken steps to address the increased load, and analysis times are have returned to normal. We're continuing to monitor closely.

4. resolved Sep 25, 2026, 06:25 PM UTC

   Resolved

Read the full incident report →

Started Aug 17, 2026, 01:59 PM UTC· resolved Aug 17, 2026, 09:28 PM UTC

1. monitoring Aug 17, 2026, 01:59 PM UTC

   Aug 17, 2026, 13:59 UTC Monitoring - We are currently monitoring an ongoing GitHub incident (https://www.githubstatus.com/incidents/zkxwbgr0cnmx) affecting API requests, Webhooks and Pull Requests. 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.

2. monitoring Aug 17, 2026, 01:59 PM UTC

   We are currently monitoring an ongoing GitHub incident (https://www.githubstatus.com/incidents/zkxwbgr0cnmx) affecting API requests, Webhooks and Pull Requests. 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.

3. resolved Aug 17, 2026, 09:28 PM UTC

   GitHub has resolved the incident affecting API requests, Webhooks, and Pull Requests. Our systems are operating normally, and we are not observing any ongoing impact to repository analysis. We will continue to monitor the situation, but no further disruption is expected at this time.

Read the full incident report →

Started Aug 03, 2026, 02:34 PM UTC· resolved Aug 04, 2026, 09:08 AM UTC

1. monitoring Aug 03, 2026, 02:34 PM UTC

   Aug 3, 2026, 14:34 UTC Monitoring - Ongoing gitlab incident might impact analysis performance in Codacy https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6a70a6536b705304ebb769b6

2. monitoring Aug 03, 2026, 02:34 PM UTC

   Ongoing gitlab incident might impact analysis performance in Codacy https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6a70a6536b705304ebb769b6

3. resolved Aug 04, 2026, 09:08 AM UTC

   Resolved

Read the full incident report →

Started Aug 01, 2026, 03:23 PM UTC· resolved Aug 01, 2026, 11:04 PM UTC

1. monitoring Aug 01, 2026, 03:23 PM UTC

   Aug 1, 2026, 15:23 UTC Investigating - We are investigating an issues that is causing slower analysis, results reporters and also impacting UI responsiveness.

2. investigating Aug 01, 2026, 03:23 PM UTC

   We are investigating an issues that is causing slower analysis, results reporters and also impacting UI responsiveness.

3. monitoring Aug 01, 2026, 03:53 PM UTC

   We've identified and resolved the root cause affecting analysis performance and UI responsiveness. Performance is back to normal. We're continuing to monitor closely to ensure stability.

4. monitoring Aug 01, 2026, 03:55 PM UTC

   Monitoring

5. resolved Aug 01, 2026, 11:04 PM UTC

   Resolved

Read the full incident report →

Started Jul 23, 2026, 08:04 AM UTC· resolved Jul 23, 2026, 10:45 AM UTC

1. monitoring Jul 23, 2026, 08:04 AM UTC

   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.

2. monitoring Jul 23, 2026, 08:04 AM UTC

   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.

3. resolved Jul 23, 2026, 10:45 AM UTC

   Resolved

Read the full incident report →

Started Jul 15, 2026, 09:49 AM UTC· resolved Jul 15, 2026, 10:19 AM UTC

1. monitoring Jul 15, 2026, 09:49 AM UTC

   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.

2. identified Jul 15, 2026, 09:49 AM UTC

   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.

3. identified Jul 15, 2026, 09:49 AM UTC

   Identified

4. monitoring Jul 15, 2026, 09:52 AM UTC

   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.

5. resolved Jul 15, 2026, 10:19 AM UTC

   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 fix has been deployed and the issue is fully resolved. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jul 03, 2026, 08:43 AM UTC· resolved Jul 03, 2026, 08:43 AM UTC

1. monitoring Jul 03, 2026, 08:43 AM UTC

   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.

Read the full incident report →

Started Jul 01, 2026, 09:08 AM UTC· resolved Jul 01, 2026, 10:56 AM UTC

1. monitoring Jul 01, 2026, 09:08 AM UTC

   Jul 1, 2026, 09:08 UTC Investigating - We are investigating a problem in our databases that is causing Codacy to become non responsive.

2. investigating Jul 01, 2026, 09:08 AM UTC

   We are investigating a problem in our databases that is causing Codacy to become non responsive.

3. investigating Jul 01, 2026, 09:34 AM UTC

   We are seeing recovery in our services but are still working to fully identify the root cause of the issue and make sure our mitigation measures hold.

4. monitoring Jul 01, 2026, 09:43 AM UTC

   We are observing positive signs as we bring all services back up. There is a backlog of analysis jobs that will take longer than usual to process but signs are positive. We will keep on updating as the recovery progresses. Right now all services should be available but still not up to full performance.

5. monitoring Jul 01, 2026, 09:58 AM UTC

   Systems are back to normal capacity but delays in analysis are to be expected for a bit longer while we process backlog of analysis that were stopped during the duration of the outage.

6. resolved Jul 01, 2026, 10:56 AM UTC

   All systems are now operating at normal performance, and the analysis queue backlog has been fully consumed. Root cause: This incident was caused by an unplanned DDL (schema) change applied in production, which triggered cascading lock contention on a database table that is central to our platform's operation. Because of this table's role across multiple services, the impact extended well beyond the original change and affected system-wide performance. Next steps: We are hardening our deployment processes to ensure DDL operations cannot be run against production databases in ways that risk service disruption, particularly during peak hours. This includes stricter guardrails around when and how schema changes are applied. We apologize for the disruption this caused and appreciate your patience while we resolved it.

Read the full incident report →

Started Jun 19, 2026, 01:34 PM UTC· resolved Jun 20, 2026, 06:20 AM UTC

1. monitoring Jun 19, 2026, 01:34 PM UTC

   Jun 19, 2026, 13:34 UTC Identified - We have identified the cause of a degraded performance in Security and Risk management API

2. identified Jun 19, 2026, 01:34 PM UTC

   We have identified the cause of a degraded performance in Security and Risk management API

3. monitoring Jun 19, 2026, 01:49 PM UTC

   Mitigations are in place and we are actively monitoring the situation.

4. resolved Jun 20, 2026, 06:20 AM UTC

   Mitigations put in place have resolved the issue. We will continue to monitor to ensure stability.

Read the full incident report →

Started Jun 19, 2026, 06:05 AM UTC· resolved Jun 19, 2026, 06:05 AM UTC

1. monitoring Jun 19, 2026, 06:05 AM UTC

   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.

Read the full incident report →

Started Jun 17, 2026, 11:32 AM UTC· resolved Jun 18, 2026, 02:47 PM UTC

1. monitoring Jun 17, 2026, 11:32 AM UTC

   Jun 17, 2026, 11:32 UTC Investigating - We are investigating the cause of a degraded performance in Security and Risk management API

2. investigating Jun 17, 2026, 11:32 AM UTC

   We are investigating the cause of a degraded performance in Security and Risk management API

3. identified Jun 17, 2026, 11:52 AM UTC

   We have identified the cause of the problem, and are actively trying to mitigate

4. identified Jun 17, 2026, 04:22 PM UTC

   We have deployed improvements that have reduced the impact for the majority of customers. However, customers processing large datasets may continue to experience some impact. Our team continues to work on a full resolution.

5. monitoring Jun 18, 2026, 10:49 AM UTC

   Mitigations are in place and we are actively monitoring the situation. Some larger organizations may continue to experience some impact during this time.

6. resolved Jun 18, 2026, 02:47 PM UTC

   Mitigations put in place have resolved the issue. All customers should now be experiencing normal performance. We will continue to monitor to ensure stability.

Read the full incident report →

Started Jun 15, 2026, 04:02 PM UTC· resolved Jun 15, 2026, 05:42 PM UTC

1. monitoring Jun 15, 2026, 04:02 PM UTC

   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

2. monitoring Jun 15, 2026, 04:02 PM UTC

   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

3. monitoring Jun 15, 2026, 04:42 PM UTC

   Monitoring

4. resolved Jun 15, 2026, 05:42 PM UTC

   Resolved

Read the full incident report →

Started Jun 11, 2026, 11:02 AM UTC· resolved Jun 15, 2026, 05:44 PM UTC

1. monitoring Jun 11, 2026, 11:02 AM UTC

   Jun 11, 2026, 11:02 UTC Identified - We identified a problem with the Analysis system, we are working on a mitigation.

2. identified Jun 11, 2026, 11:02 AM UTC

   We identified a problem with the Analysis system, we are working on a mitigation.

3. monitoring Jun 11, 2026, 11:30 AM UTC

   The analysis queue is now again at a normal level. We are monitoring the system to ensure the mitigation continues to work as expected.

4. identified Jun 15, 2026, 03:06 PM UTC

   Analysis is currently experiencing delays due to an issue with our cloud provider. Our team is actively working on a fix. We apologize for the inconvenience and will update this page as soon as the issue is resolved.

5. investigating Jun 15, 2026, 03:06 PM UTC

   We are experiencing some delays in analysis. We are investigating the cause.

6. identified Jun 15, 2026, 03:08 PM UTC

   Analysis is currently experiencing delays due to an issue with our cloud provider. Our team is actively working on a fix. We apologize for the inconvenience and will update this page as soon as the issue is resolved.

7. monitoring Jun 15, 2026, 03:43 PM UTC

   The analysis backlog has been cleared and performance is back to normal. We have applied mitigations on our end to address the cloud provider capacity issue and are monitoring the system to ensure stability. We will follow up with improvements to prevent recurrence.

8. resolved Jun 15, 2026, 05:44 PM UTC

   The mitigation measures we applied are working as expected. Analysis performance has returned to normal and we are marking this as resolved. We will continue to monitor and work on longer-term improvements to prevent recurrence.

Read the full incident report →

Started Jun 04, 2026, 10:28 PM UTC· resolved Jun 05, 2026, 05:47 AM UTC

1. monitoring Jun 04, 2026, 10:28 PM UTC

   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.

2. monitoring Jun 04, 2026, 10:28 PM UTC

   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.

3. monitoring Jun 04, 2026, 11:39 PM UTC

   Recovery is progressing well and service levels have returned to normal for paid accounts. The remaining backlog consists primarily of analyses from Free and Open Source organizations that accumulated during the incident. We are actively processing this backlog, and those organizations may continue to experience some delays in analysis execution until it has been cleared. The platform is otherwise operating normally. We will continue to monitor processing and system performance to ensure the backlog is cleared and service remains stable.

4. resolved Jun 05, 2026, 05:47 AM UTC

   The remaining backlog has been processed, and the platform is operating normally.

Read the full incident report →

Started Jun 01, 2026, 08:32 AM UTC· resolved Jun 01, 2026, 08:58 AM UTC

1. monitoring Jun 01, 2026, 08:32 AM UTC

   Jun 1, 2026, 08:32 UTC Identified - We have identified an issue affecting one of our security analysis tool trivy. As a result, some analyses may be delayed or fail to complete successfully. We are working to mitigage the cause and will provide another update as soon as we have more information.

2. identified Jun 01, 2026, 08:32 AM UTC

   We have identified an issue affecting one of our security analysis tool trivy. As a result, some analyses may be delayed or fail to complete successfully. We are working to mitigage the cause and will provide another update as soon as we have more information.

3. monitoring Jun 01, 2026, 08:39 AM UTC

   We have rolled out a fix that fully mitigates the issue.

4. resolved Jun 01, 2026, 08:58 AM UTC

   We have resolved an issue that affected one of our security analysis tools. The issue was caused by a problem in our image publishing mechanism, which prevented the expected tool version from being available. This led to image pull failures for codacy-trivy starting on Sunday, May 31 at 15:00 GMT. As a result, analyses that depended on this tool between Sunday, May 31 at 15:00 GMT and Monday, June 1 at 08:35 GMT may not have produced complete or correct results. This also affected nightly proactive SCA runs during that period. The issue is now fixed. We are continuing to review the incident and are making changes to prevent this from happening again.

Read the full incident report →

Started May 29, 2026, 08:59 AM UTC· resolved May 29, 2026, 08:59 AM UTC

1. monitoring May 29, 2026, 08:59 AM UTC

   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.

Read the full incident report →

Started May 27, 2026, 01:09 PM UTC· resolved May 27, 2026, 02:02 PM UTC

1. monitoring May 27, 2026, 01:09 PM UTC

   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.

2. monitoring May 27, 2026, 01:09 PM UTC

   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.

3. resolved May 27, 2026, 02:02 PM UTC

   Resolved

Read the full incident report →

Started May 27, 2026, 09:14 AM UTC· resolved May 27, 2026, 10:07 AM UTC

1. monitoring May 27, 2026, 09:14 AM UTC

   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.

2. monitoring May 27, 2026, 09:14 AM UTC

   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.

3. resolved May 27, 2026, 10:07 AM UTC

   Resolved

Read the full incident report →

Started May 21, 2026, 11:05 AM UTC· resolved May 21, 2026, 12:07 PM UTC

1. monitoring May 21, 2026, 11:05 AM UTC

   May 21, 2026, 11:07 UTC Identified - The issue has been identified as elevated load on DependenciesDB caused by background SBOM reprocessing after a recent toolchain version update. This can cause dependency pages to load slowly or, in some cases, fail to load. The backlog is currently being processed and we expect performance to return to normal once it drains. We are monitoring the situation and will provide another update when the impact has been resolved. May 21, 2026, 11:05 UTC Investigating - We are currently seeing degraded performance when loading Dependencies/Security dependency pages for some organizations. The issue has been identified as elevated load on the database backing dependencies data, caused by background SBOM reprocessing after a recent toolchain version update. This can cause dependency pages to load slowly or, in some cases, fail to load. Some other Security dashboard pages that rely on dependencies data may also be affected. Analysis functionality is not expected to be affected. The backlog is currently being processed, and we expect performance to return to normal once it drains. We are monitoring the situation and will provide another update when the impact has been resolved.

2. investigating May 21, 2026, 11:05 AM UTC

   We are currently seeing degraded performance when loading Dependencies/Security dependency pages for some organizations. The issue has been identified as elevated load on the database backing dependencies data, caused by background SBOM reprocessing after a recent toolchain version update. This can cause dependency pages to load slowly or, in some cases, fail to load. Some other Security dashboard pages that rely on dependencies data may also be affected. Analysis functionality is not expected to be affected. The backlog is currently being processed, and we expect performance to return to normal once it drains. We are monitoring the situation and will provide another update when the impact has been resolved.

3. identified May 21, 2026, 11:07 AM UTC

   The issue has been identified as elevated load on DependenciesDB caused by background SBOM reprocessing after a recent toolchain version update. This can cause dependency pages to load slowly or, in some cases, fail to load. The backlog is currently being processed and we expect performance to return to normal once it drains. We are monitoring the situation and will provide another update when the impact has been resolved.

4. resolved May 21, 2026, 12:07 PM UTC

   The backlog caused by background SBOM reprocessing after the recent toolchain version update has been fully processed, and we are no longer observing degraded performance or page load failures affecting dependency-related pages. We will continue to monitor the system to ensure stability.

Read the full incident report →

Started May 19, 2026, 10:18 PM UTC· resolved May 19, 2026, 10:18 PM UTC

1. monitoring May 19, 2026, 10:18 PM UTC

   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.

Read the full incident report →

Started May 11, 2026, 09:05 AM UTC· resolved May 11, 2026, 11:33 AM UTC

1. monitoring May 11, 2026, 09:05 AM UTC

   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.

2. monitoring May 11, 2026, 09:05 AM UTC

   We are monitoring a GitLab service disruption (https://status.io/pages/incident/5b36dc6502d06804c08349f7/6a019654c45d27050d60be2d) that can impact Codacy analysis.

3. resolved May 11, 2026, 11:33 AM UTC

   Resolved

Read the full incident report →