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 August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 35m agoLive, rechecked every 60s
Start monitoring Qlty CloudOfficial Qlty Cloud status page
How we know: the official Qlty Cloud status page, PulsAPI's own check every 60 seconds, 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.

Create a free account

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.

Uptime history4 days observed
Aug 8100.00% averageAug 11
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>

Github API degradationResolved Jul 16, 2026 · 1h 14mResolved

This incident has been resolved. --- [2026-07-17T00:09:03Z] (monitoring) Github has remediated the source of the incident and are monitoring. --- [2026-07-16T23:00:30Z] (identified) Github API requests are throwing 503, Github has declared an incident and is investigating. <https://www.githubstatus.com/incidents/gxycch3076xk>

Coverage uploads and analysis are delayedResolved Jun 16, 2026 · 4h 15mResolved

This incident has been resolved. --- [2026-06-16T18:00:21Z] (monitoring) We have remediated the source of the incident and are monitoring. --- [2026-06-16T14:44:23Z] (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.

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?

PulsAPI checks Qlty Cloud every 60 seconds. 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.

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%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Qlty Cloud.

How fast does PulsAPI detect Qlty Cloud outages?

PulsAPI polls the official Qlty Cloud status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

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 PulsAPI account and subscribe to Qlty Cloud. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Qlty Cloud status changes.

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. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Qlty Cloud alongside up to 9 other services at pulsapi.com/signup.

Track Qlty Cloud with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Qlty Cloud status changes.

Start free trial