Is Qlty Software down?
Last checked 2m agoNo incidents right now.
Qlty Software is operational right now. Last checked 2m ago; the most recent incident resolved 26d ago.
Real-time Qlty Software status, recent outages, and incident history — pulled directly from Qlty Software's official status page at https://status.qlty.sh every 5 minutes. Pingoru tracks 5 Qlty Software services and has captured 5 incidents in the last 90 days (96.67% uptime). Get email, Slack, Discord, or webhook alerts the moment Qlty Software reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- GitHub.comCode CoverageCode Analysis
Timeline · 2 updates
- identified · Aug 17, 2026, 02:29 PM UTC
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)
- resolved · Aug 17, 2026, 10:35 PM UTC
Status: Resolved This incident has been resolved. Affected components Code Analysis (Operational) Code Coverage (Operational) GitHub.com (Operational)
Latest: Status: Resolved This incident has been resolved. Affected components Code Analysis (Operational) Code Coverage (Operational) GitHub.com (Operational)
-
- GitHub.comCode Analysis
Timeline · 4 updates
- monitoring · Aug 12, 2026, 07:15 PM UTC
Status: Monitoring We are currently investigating intermittent build failures caused by network issues when downloading plugins from GitHub during analysis runs. Our team is actively identifying the root cause and working on a resolution. We will provide an update as soon as more details or a fix are available. Affected components Code Analysis (Partial outage)
- identified · Aug 12, 2026, 08:32 PM UTC
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)
- identified · Aug 12, 2026, 09:57 PM UTC
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)
- resolved · Aug 12, 2026, 11:12 PM UTC
Status: Resolved GitHub acknowledged that this was an incident: https://www.githubstatus.com/incidents/lsvy8xsf0gxv and resolved it. Affected components Code Analysis (Operational) GitHub.com (Operational)
Latest: Status: Resolved GitHub acknowledged that this was an incident: https://www.githubstatus.com/incidents/lsvy8xsf0gxv and resolved it. Affected components Code Analysis (Operational)…
-
- GitHub.comCode CoverageCode Analysis
Timeline · 5 updates
- identified · Aug 06, 2026, 05:01 PM UTC
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)
- identified · Aug 06, 2026, 05:02 PM UTC
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)
- identified · Aug 06, 2026, 05:02 PM UTC
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)
- identified · Aug 06, 2026, 09:57 PM UTC
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)
- resolved · Aug 07, 2026, 09:04 AM UTC
Status: Resolved This incident has been resolved. Affected components Code Analysis (Operational) Code Coverage (Operational) GitHub.com (Operational)
Latest: Status: Resolved This incident has been resolved. Affected components Code Analysis (Operational) Code Coverage (Operational) GitHub.com (Operational)
-
- GitHub.com
Timeline · 3 updates
- identified · Jul 16, 2026, 11:00 PM UTC
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)
- monitoring · Jul 17, 2026, 12:09 AM UTC
Status: Monitoring Github has remediated the source of the incident and are monitoring. Affected components GitHub.com (Partial outage)
- resolved · Jul 17, 2026, 12:15 AM UTC
Status: Resolved This incident has been resolved. Affected components GitHub.com (Operational)
Latest: Status: Resolved This incident has been resolved. Affected components GitHub.com (Operational)
-
- Code CoverageCode Analysis
Timeline · 3 updates
- investigating · Jun 16, 2026, 02:44 PM UTC
Status: Investigating Our coverage and analysis queues are erroring and delayed. We've narrowed the root cause down to our database vendor which ran a backwards incompatible upgrade. Affected components Code Coverage (Full outage) Code Analysis (Full outage)
- monitoring · Jun 16, 2026, 06:00 PM UTC
Status: Monitoring We have remediated the source of the incident and are monitoring. Affected components Code Analysis (Operational) Code Coverage (Operational)
- resolved · Jun 16, 2026, 07:00 PM UTC
Status: Resolved This incident has been resolved. Affected components Code Analysis (Operational) Code Coverage (Operational)
Latest: Status: Resolved This incident has been resolved. Affected components Code Analysis (Operational) Code Coverage (Operational)
-
- Started Aug 17, 2026, 10:35 PM UTC · Resolved Aug 17, 2026, 10:35 PM UTC · —
- Intermittent build failures ResolvedStarted Aug 12, 2026, 11:12 PM UTC · Resolved Aug 12, 2026, 11:12 PM UTC · —
- Started Aug 07, 2026, 09:04 AM UTC · Resolved Aug 07, 2026, 09:04 AM UTC · —
- Github API degradation ResolvedStarted Jul 17, 2026, 12:15 AM UTC · Resolved Jul 17, 2026, 12:15 AM UTC · —
- Started Jun 16, 2026, 07:00 PM UTC · Resolved Jun 16, 2026, 07:00 PM UTC · —