Codacy incident

Delays starting analysis and finishing ongoing analysis

Minor Resolved View vendor source →
Started
Feb 03, 2026, 01:05 PM UTC
Resolved
Feb 03, 2026, 01:05 PM UTC
Duration
Detected by Pingoru
Feb 03, 2026, 01:05 PM UTC

Update timeline

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

Looking to track Codacy downtime and outages?

Pingoru polls Codacy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Codacy reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Codacy alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Codacy for free

5 free monitors · No credit card required