Codacy incident

Codacy underreporting issues

Minor Resolved View vendor source →
Started
Mar 19, 2026, 02:10 PM UTC
Resolved
Mar 19, 2026, 02:10 PM UTC
Duration
Detected by Pingoru
Mar 19, 2026, 02:10 PM UTC

Update timeline

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

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