- Detected by Pingoru
- Jun 15, 2026, 04:02 PM UTC
- Resolved
- Jun 15, 2026, 04:02 PM UTC
- Duration
- —
Timeline · 1 update
-
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
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 11:02 AM UTC
- Resolved
- Jun 11, 2026, 11:02 AM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 10:28 PM UTC
- Resolved
- Jun 04, 2026, 10:28 PM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 08:59 AM UTC
- Resolved
- May 29, 2026, 08:59 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- May 27, 2026, 01:09 PM UTC
- Resolved
- May 27, 2026, 01:09 PM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 09:14 AM UTC
- Resolved
- May 27, 2026, 09:14 AM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 11:05 AM UTC
- Resolved
- May 21, 2026, 11:05 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 10:18 PM UTC
- Resolved
- May 19, 2026, 10:18 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- May 11, 2026, 09:05 AM UTC
- Resolved
- May 11, 2026, 09:05 AM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 08:12 AM UTC
- Resolved
- May 08, 2026, 08:12 AM UTC
- Duration
- —
Timeline · 1 update
-
monitoring May 08, 2026, 08:12 AM UTC
May 8, 2026, 08:12 UTC Monitoring - Ongoing Bitbucket incident (https://bitbucket.status.atlassian.com/incidents/hpkdy4vmq470) might result in degraded performance across several parts of Codacy for Bitbucket customers. Login, managing repositories, analysis discovery and analysis execution might be (or have been) impacted by the ongoing incident.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 10:38 PM UTC
- Resolved
- Apr 28, 2026, 10:38 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Apr 28, 2026, 10:38 PM UTC
Apr 28, 2026, 22:39 UTC Identified - Apr 28, 2026, 22:38 UTC Identified - GitHub is experiencing degraded performance for Pull Requests, which in turn is affecting Codacy's PR analysis. https://www.githubstatus.com
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 03:12 PM UTC
- Resolved
- Apr 28, 2026, 03:12 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Apr 28, 2026, 03:12 PM UTC
Apr 28, 2026, 15:12 UTC Scheduled - We will do an upgrade to the version of the nodes used in our system to keep our system up-to-date. Running nodes at this time will not be affected, only nodes that are created past this upgrade will be affected. As such, no downtime is expected during this maintenance. Afterwards, we will be monitoring newly created nodes to verify the overall stability of the system.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 03:25 PM UTC
- Resolved
- Apr 23, 2026, 03:25 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Apr 23, 2026, 03:25 PM UTC
Apr 23, 2026, 15:25 UTC Scheduled - We will be performing a minor version upgrade on a few of our databases. During this maintenance window, Codacy may experience degraded performance and intermittent issues across the platform, including analysis, API requests, and the UI.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 02:10 PM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 64d 21h
Affected: [ Status] Incident History service
Timeline · 1 update
-
investigating Mar 19, 2026, 02:10 PM UTC
Mar 19, 2026, 14:10 UTC Resolved - We identified and fixed a bug that affected issue reporting in Codacy between February 11, 2026 and March 19, 2026. During that period, some issues detected by analysis were not surfaced correctly in dashboards or pull request results. This may have caused some repositories to show fewer issues than expected and, in some cases, may have allowed pull requests to pass quality gates when they otherwise would have been blocked. The fix is now deployed. New analyses and re-analyses will now report issues correctly. As a result, some customers may see higher issue counts or different pull request outcomes going forward. Existing historical results are not automatically backfilled. More details here: https://codacy.slite.page/p/p9ZvJmbH3MPPS0/Codacy-underreported-issues-between-February-11-and-March-19-2026
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 03:05 PM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 72d 20h
Affected: [ Status] Incident History service
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 07:55 PM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 78d 15h
Affected: [ Status] Incident History service
Timeline · 1 update
-
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/
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 11:17 AM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 85d 23h
Affected: [ Status] Incident History service
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 04:05 PM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 98d 19h
Affected: [ Status] Incident History service
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 10:30 AM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 100d
Affected: [ Status] Incident History service
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 04:30 PM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 102d 18h
Affected: [ Status] Incident History service
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 09:26 AM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 103d 1h
Affected: [ Status] Incident History service
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 11:06 AM UTC
- Resolved
- Feb 04, 2026, 11:06 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Feb 04, 2026, 10:15 AM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 108d 1h
Affected: [ Status] Incident History service
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 03:58 PM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 126d 19h
Affected: [ Status] Incident History service
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 05:55 PM UTC
- Resolved
- May 23, 2026, 11:16 AM UTC
- Duration
- 134d 17h
Affected: [ Status] Incident History service
Timeline · 1 update
Read the full incident report →