Resolved after 11 days 4 hours, on April 4, 2025.
Analysis queue size has been stable and performing up to standards and no abnormal delays to analysis are to be expected. During the incident period we lost provider notifications of new analysis to run which will lead to specific PRs or Commits not showing up in Codacy. This is self-healed by normal activity (pushing commits) but can also be proactively fixed by redelivering any `pull_request.*` and `push` events that failed (https://docs.github.com/en/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks). If any PRs in Codacy were not analysed as a result of this incident, you can a) re-analyze PR b) re-analyze the head commit or c) update the PR by adding new commits.
Update timeline
- investigating Apr 04, 2025, 06:37 AM UTC
Codacy API is having a Partial Outage. It's under investigation now.
- investigating Apr 04, 2025, 06:43 AM UTC
We are investigating a failure that has caused Codacy services to be unavailable starting at around 2:30 UTC.
- investigating Apr 04, 2025, 07:13 AM UTC
We are seeing improvements in availability and lowered errors rates across the board. Application UI, API and analysis activities are now available. Analysis is running for backed up analysis.
- monitoring Apr 04, 2025, 07:13 AM UTC
Monitoring
- monitoring Apr 04, 2025, 07:33 AM UTC
Unexpected load from daily proactive Software Composition Analysis (SCA) caused Codacy's analysis system to enter severely degraded performance also impacting the UI and API. Infrastructure capacity was increased to comfortably support this workload and prevent further failures.
- monitoring Apr 04, 2025, 09:54 AM UTC
Analysis queue size has been stable and performing up to standards and no abnormal delays to analysis are to be expected. During the incident period we lost provider notifications of new analysis to run which will lead to specific PRs or Commits not showing up in Codacy. This is self-healed by normal activity (pushing commits) but can also be proactively fixed by redelivering any `pull_request.*` and `push` events that failed (https://docs.github.com/en/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks). If any PRs in Codacy were not analysed as a result of this incident, you can a) re-analyze PR b) re-analyze the head commit or c) update the PR by adding new commits.
- resolved Apr 15, 2025, 11:16 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