Qlty Software Outage History

Status: Identified We have identified the source of this incident, GitHub's various APIs are experiencing degrading performance https://www.githubstatus.com/incidents/zkxwbgr0cnmx. Affected components Code Analysis (Degraded performance) Code Coverage (Degraded performance) GitHub.com (Degraded performance)

Status: Identified Since approximately 9:30 AM PT, a portion of analysis builds have been failing during the tool-installation step, with errors like "Error installing tool …" in the build log. We've traced this to an upstream disruption affecting downloads of release assets from GitHub — the archives our builds fetch to install linters and language runtimes. The disruption is intermittent: during failure bursts roughly 1 in 8 builds fails, and between bursts builds complete normally. We have escalated it to GitHub. What you can do: re-running a failed build will usually succeed, though a retry may still hit a failure window while the disruption continues. No action is needed for builds that completed successfully. Coverage uploads and processing, qlty.sh: http://qlty.sh, and the API are unaffected. We're monitoring failure rates continuously and will post an update when the disruption clears. Affected components Code Analysis (Partial outage)

Status: Identified We have identified the source of this incident and are working on remediation. Affected components Code Analysis (Partial outage) GitHub.com (Partial outage)

Status: Identified Coverage using Github OIDC appears to be affected by a Github Actions incident https://www.githubstatus.com/incidents/qcvjkzcs7j74 Affected components GitHub.com (Partial outage)

Status: Identified We have identified the source of this incident and are working on remediation. Affected components Code Coverage (Degraded performance) GitHub.com (Partial outage)

Status: Identified Coverage using Github OIDC appears to be affected by a Github Actions incident https://www.githubstatus.com/incidents/qcvjkzcs7j74 Affected components Code Coverage (Degraded performance) GitHub.com (Partial outage)

Status: Identified There have been multiple impacts due to Github outage https://www.githubstatus.com/incidents/qcvjkzcs7j74 such as coverage action using OIDC breaking and delayed results on analysis due to webhooks being throttled. Affected components GitHub.com (Partial outage) Code Analysis (Degraded performance) Code Coverage (Degraded performance)

Status: Identified Github API requests are throwing 503, Github has declared an incident and is investigating. https://www.githubstatus.com/incidents/gxycch3076xk Affected components GitHub.com (Partial outage)

Status: Identified We are currently investigating delays in Code Coverage processing. Coverage uploads that require mapping commits to pull requests may be delayed due to degraded performance in GitHub’s Pull Requests and Search APIs. This can impact the timely delivery of coverage statuses and comments on pull requests. Analysis processing is not affected. The issue is limited to coverage ingestion and reporting. We are actively monitoring the situation and will provide updates as GitHub recovers. For more information, see GitHub’s status page: https://www.githubstatus.com/: https://www.githubstatus.com/?utm_source=chatgpt.com Affected components Code Coverage (Degraded performance)

Status: Identified A recent update has caused format builds to fail during Qlty Cloud analysis. We've identified the issue and are actively working on a fix. In the meantime, as a workaround, you can format your code locally (using `qlty fmt`) and push your changes as usual. Affected components Code Analysis (Partial outage)

Status: Identified Trivy experienced a security incident on 2026-03-01, which resulted in GitHub releases between v0.27.0 and v0.69.1 being deleted, causing build failures for any project using an affected version of the Trivy plugin. Workarounds: • Pin Trivy to v0.69.2 in your .qlty/qlty.toml • Or temporarily disable the Trivy plugin until the situation is resolved For more details on the upstream incident, see the Trivy security incident report: https://github.com/aquasecurity/trivy/discussions/10265. Affected components Code Analysis (Partial outage)

Status: Identified We have identified the source of this incident and applied a partial fix. Quality analysis results should now be published to GitHub as expected. Affected components Code Analysis (Operational)