Update timeline
- resolved Feb 12, 2026, 10:35 AM UTC
Feb 13, 2026, 16:05 UTC Resolved - The long tail of failing cases have now been solved and the processing is more reliable for large repositories with large numbers of findings. Feb 13, 2026, 13:57 UTC Investigating - Remediation actions have improved processing for the majority of affected cases. Few remaining edge cases are under investigation. We will provide further updates as progress is confirmed. Feb 13, 2026, 12:34 UTC Identified - We have identified and implemented a mitigation to an additional contributing issue affecting timeliness for a subset of large repositories.Changes are being rolled out incrementally and monitored closely to validate impact. Further updates will follow as results are confirmed Feb 12, 2026, 16:35 UTC Investigating - SRM findings timeliness is back to normal for most old and all new findings. The exception is for a small groups of large repos with large numbers of findings that we still working on fully unblocking. Feb 12, 2026, 14:45 UTC Monitoring - Improvements have been rolled out and we are validating that the root cause is resolved. SRM findings ingestion is recovering and remaining delays should continue to reduce. Feb 12, 2026, 14:03 UTC Identified - We have deployed mitigations that partially restored ingestion of SRM findings, and we are processing the backlog. A subset of findings is still failing or taking significantly longer to process, which can cause newly generated findings to appear delayed on the SRM Dashboard. We will soon roll out an improvement aimed at fully restoring normal ingestion for all findings. Feb 12, 2026, 11:56 UTC Identified - We have identified the root cause of the issue and were able to roll out mitigating measures that resulted in ingestion of some SRM Findings being unblocked. We are now processing some of the findings backlog but there still ongoing investigation in order to unblock ingestion for all SRM Findings. Feb 12, 2026, 11:41 UTC Investigating - We continue investigating the root cause of the issue that is preventing new SRM finding from showing on SRM Dashboard. Feb 12, 2026, 10:35 UTC Investigating - We are investigating an issue that is preventing new SRM findings from being correctly processed and displayed in the SRM Dashboard.
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
5 free monitors · No credit card required