Codacy incident

Degraded analysis performance

Minor Resolved View vendor source →

Codacy experienced a minor incident on June 1, 2026, lasting 25m. The incident has been resolved; the full update timeline is below.

Started
Jun 01, 2026, 08:32 AM UTC
Resolved
Jun 01, 2026, 08:58 AM UTC
Duration
25m
Detected by Pingoru
Jun 01, 2026, 08:32 AM UTC

Update timeline

  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.