Codacy incident
Updates and analysis for some Github repositories are not being correctly detected
Resolved after 2 hours 31 minutes, on January 16, 2025.
All affected repositories have now been reverted to nominal state. Analysis detecting and execution should be back to normal for the affected repositories.
Update timeline
- identified Jan 16, 2025, 09:01 AM UTC
In the wake of Monday 13th Github's incident (https://www.githubstatus.com/incidents/qd96yfgvmcf9) some repositories were erroneously marked as permanently failed by Codacy, and new analysis for those repositories were not being detected and triggered. The affected repositories have been identified and we are working to solve the issue
- resolved Jan 16, 2025, 11:33 AM UTC
All affected repositories have now been reverted to nominal state. Analysis detecting and execution should be back to normal for the affected repositories.
Your product runs on more than Codacy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services