Qlty Cloud logo

Is Qlty Cloud Down?

SaaSLive status, outages, and incident history

No. Qlty Cloud is up right now.

Every monitored Qlty Cloud system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 16m agoLive · 60s while moving

Know the moment Qlty Cloud breaks

Qlty Cloud is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

Official Qlty Cloud status page
How we know: the official Qlty Cloud status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Qlty Cloud Component Status

The main Qlty Cloud systems on this page. All 5 are operational right now.

5operational
API
Operational
Code Analysis
Operational
Code Coverage
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking GitHub.com, Website.

See all of them free

Component statuses may change independently during partial outages.

Recent Qlty Cloud Outages & Incidents

Incident history from the official Qlty Cloud status page, including resolution updates.

GitHub incident causing degraded performanceResolved Aug 17, 2026 · 8h 5mResolved

This incident has been resolved. --- [2026-08-17T14:29:45Z] (identified) We have identified the source of this incident, GitHub's various APIs are experiencing degrading performance <https://www.githubstatus.com/incidents/zkxwbgr0cnmx>.

Intermittent build failuresResolved Aug 12, 2026 · 3h 56mResolved

GitHub acknowledged that this [was an incident](https://www.githubstatus.com/incidents/lsvy8xsf0gxv) and resolved it. --- [2026-08-12T21:57:57Z] (identified) We have identified the source of this incident and are working on remediation. --- [2026-08-12T20:32:53Z] (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. --- [2026-08-12T19:15:22Z] (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.

Coverage and analysis maybe affected by Github actions incidentResolved Aug 6, 2026 · 16h 3mResolved

This incident has been resolved. --- [2026-08-06T21:57:45Z] (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. --- [2026-08-06T17:02:49Z] (identified) Coverage using Github OIDC appears to be affected by a Github Actions incident <https://www.githubstatus.com/incidents/qcvjkzcs7j74> --- [2026-08-06T17:02:26Z] (identified) We have identified the source of this incident and are working on remediation. --- [2026-08-06T17:01:44Z] (identified) Coverage using Github OIDC appears to be affected by a Github Actions incident <https://www.githubstatus.com/incidents/qcvjkzcs7j74>

Qlty Cloud Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Qlty Cloud incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 2 days with incidentsSep 25

Live Qlty Cloud Outage Reports

Problems reported by engineers using Qlty Cloud. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Qlty Cloud problems reported yet.

Something wrong with Qlty Cloud on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Qlty Cloud

Qlty Cloud publishes a public status page at status.qlty.sh covering 5 components, including Code Coverage, Website and GitHub.com. PulsAPI tracks Qlty Cloud outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Qlty Cloud uptime at 100.00%. Response times, incident history, and SLA tracking for Qlty Cloud are available on the PulsAPI dashboard.

Qlty Cloud Status FAQ

Is Qlty Cloud down right now?

The verdict at the top of this page comes from the latest poll of the official Qlty Cloud status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Qlty Cloud is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Qlty Cloud recovers.

How do I check Qlty Cloud uptime history?

PulsAPI tracks Qlty Cloud uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Qlty Cloud changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Qlty Cloud outages?

PulsAPI reads the official Qlty Cloud status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Qlty Cloud components?

Yes. PulsAPI monitors 5 individual Qlty Cloud components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Qlty Cloud goes down?

Yes. Create a free account and subscribe to Qlty Cloud: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Qlty Cloud to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Qlty Cloud problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Qlty Cloud?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Qlty Cloud plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Qlty Cloud with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services