Qlty Cloud Outage History

22 incidents recorded over the last 365 days, 22 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Qlty Cloud status100.00% uptime history

Every Recorded Qlty Cloud Incident

Qlty Cloud incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 21, 2026Security advisory: eMudhra certificate authority compromiseQlty services are running normally. This is a security issue in certificate trust, not an outage. We have published a security advisory with the status of each Qlty component and steps you can take now…11h 37mResolved
Oct 8, 2026Analysis builds failing for projects that use default Semgrep pluginThis incident has been resolved.1h 14mResolved
Oct 6, 2026Delayed analysis results and PR check timeoutsOn October 5, 2026, between 12:18 and 12:31 PM ET, Qlty stopped completing analysis results for 13 minutes. About 120 builds across roughly 60 workspaces never completed. On the affected pull requests, the Qlty check on…-1828 minResolved
Aug 17, 2026GitHub incident causing degraded performanceThis incident has been resolved.8h 5mResolved
Aug 12, 2026Intermittent build failuresGitHub acknowledged that this [was an incident](https://www.githubstatus.com/incidents/lsvy8xsf0gxv) and resolved it.3h 56mResolved
Aug 6, 2026Coverage and analysis maybe affected by Github actions incidentThis incident has been resolved.16h 3mResolved
Jul 16, 2026Github API degradationThis incident has been resolved.1h 14mResolved
Jun 16, 2026Coverage uploads and analysis are delayedThis incident has been resolved.4h 15mResolved
Apr 27, 2026Degraded Code Coverage Processing (GitHub Upstream Incident)This incident has been resolved.4h 44mResolved
Apr 21, 2026Delayed Commit StatusesThis incident has been resolved.15 minResolved
Apr 2, 2026Format builds failingThis incident has been resolved.306h 57mResolved
Mar 30, 2026Coverage Queue BackupThis incident has been resolved.32h 35mResolved
Mar 20, 2026Security Status Report: Trivy v0.69.4This incident has been resolved.789h 46mResolved
Mar 2, 2026Build failures for projects with Trivy enabledWe've released a fix for this issue. Here's what you need to know: • **No action needed** if you don't have Trivy pinned to a specific version — Qlty will now automatically use the latest available release today…23h 22mResolved
Feb 24, 2026Timeout commit status being sent for PRsThis incident has been resolved.2h 45mResolved
Feb 18, 2026Delayed analysis buildsThis incident has been resolved.4h 8mResolved
Feb 17, 2026Delayed analysis buildsThis incident has been resolved.4h 14mResolved
Jan 27, 2026GitHub analysis results delayedThis incident has been resolved.20h 33mResolved
Jan 15, 2026GitHub Incident resulting in downstream qlty.sh issuesThis incident has been resolved.2h 13mResolved
Jan 9, 2026Network issues in analysis buildsThis incident has been resolved.32 minResolved
Dec 23, 2025Elevated build errorsThis incident has been resolved.2h 25mResolved
Nov 18, 2025Builds failing due to Github incident.This incident has been resolved.50 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Qlty Cloud incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Qlty Cloud Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Qlty Cloud acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Qlty Cloud outage in this window ran 32d 21h, against a mean recovery of 2d 11h. If you depend on Qlty Cloud in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.