Codacy incident
Degraded analysis performance leading to longer analysis times
Resolved after 36 minutes, on April 17, 2024.
The root cause of the issue was found and mitigated. A burst of analysis resulted in a central system being overloaded and becoming unresponsive. This mitigated by assigning up resources for that system. Ongoing analysis are quickly being processed and we expect to be back to nominal performance shortly. It's possible that some analysis jobs failed during the incident period. If specifics Commits or PRs take longer that normally expected, a re-analysis will solve the issue. We are working on improving auto-scaling logic for the affected component in order to prevent this issue from reoccurring.
Update timeline
- investigating Apr 17, 2024, 09:01 AM UTC
We are investigating an issue that is causing analysis to take longer than expected resulting in queuing and overall analysis delays.
- monitoring Apr 17, 2024, 09:33 AM UTC
The root cause of the issue was found and mitigated. A burst of analysis resulted in a central system being overloaded and becoming unresponsive. This mitigated by assigning up resources for that system. Ongoing analysis are quickly being processed and we expect to be back to nominal performance shortly. It's possible that some analysis jobs failed during the incident period. If specifics Commits or PRs take longer that normally expected, a re-analysis will solve the issue. We are working on improving auto-scaling logic for the affected component in order to prevent this issue from reoccurring.
- resolved Apr 17, 2024, 09:37 AM UTC
Resolved
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