Codacy Outage History

Codacy is up right now

Codacy had 75 outages in the last 2 years totaling 672h 39m of downtime — averaging 3.1 incidents per month.

There were 75 Codacy outages since November 7, 2024 totaling 672h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.codacy.com

Minor March 5, 2026

Major Outage on GitHub Actions and GitHub Webhooks

Detected by Pingoru
Mar 05, 2026, 05:12 PM UTC
Resolved
Mar 05, 2026, 07:55 PM UTC
Duration
2h 42m
Affected: [ Status] Incident History service
Timeline · 4 updates
  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 12, 2026

Performance issues in Vulnerability detection tooling leading to longer analysis times

Detected by Pingoru
Feb 12, 2026, 09:25 AM UTC
Resolved
Feb 12, 2026, 10:30 AM UTC
Duration
1h 4m
Affected: [ Status] Incident History service
Timeline · 2 updates
  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.

Read the full incident report →

Minor February 9, 2026

Increased error rate in API

Detected by Pingoru
Feb 09, 2026, 01:31 PM UTC
Resolved
Feb 09, 2026, 04:30 PM UTC
Duration
2h 58m
Affected: [ Status] Incident History service
Timeline · 2 updates
  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.

Read the full incident report →

Minor February 5, 2026

Delays in the SRM tabs

Detected by Pingoru
Feb 05, 2026, 06:17 PM UTC
Resolved
Feb 09, 2026, 09:26 AM UTC
Duration
3d 15h
Affected: [ Status] Incident History service
Timeline · 2 updates
  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.

Read the full incident report →

Minor February 4, 2026

Cluster Maintenance

Detected by Pingoru
Feb 04, 2026, 11:06 AM UTC
Resolved
Feb 04, 2026, 11:06 AM UTC
Duration
—
Timeline · 1 update
  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

Detected by Pingoru
Feb 03, 2026, 01:05 PM UTC
Resolved
Feb 04, 2026, 10:15 AM UTC
Duration
21h 10m
Affected: [ Status] Incident History service
Timeline · 2 updates
  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.

Read the full incident report →

Minor January 15, 2026

Degraded performance due to Github Incident

Detected by Pingoru
Jan 15, 2026, 05:19 PM UTC
Resolved
Jan 16, 2026, 03:58 PM UTC
Duration
22h 38m
Affected: [ Status] Incident History service
Timeline · 2 updates
  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.

Read the full incident report →

Minor December 15, 2025

Cache Systems Maintenance

Detected by Pingoru
Dec 15, 2025, 03:30 PM UTC
Resolved
Dec 15, 2025, 03:30 PM UTC
Duration
—
Timeline · 1 update
  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

Detected by Pingoru
Dec 11, 2025, 04:31 PM UTC
Resolved
Dec 11, 2025, 06:44 PM UTC
Duration
2h 12m
Timeline · 1 update
  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.

Read the full incident report →