Is Qlty Software down?

Last checked 9m ago
Current status
Qlty Software is up

No incidents right now.

Get alerts when Qlty Software breaks →

Free · no credit card

Official status page: https://status.qlty.sh · Polled every 5 minutes · 5 components tracked

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 17 incidents in the last 90 days (96.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Qlty Software reports a new incident — free for 5 monitors, no credit card.

Users who monitor Qlty Software also follow these CI/CD services: PDQ Depot AppVeyor ServiceRocket Subsplash Happo PactFlow SimplyQ Progress Telerik Aviator View all 6,000+ providers
Qlty Software uptime 96.00% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Degraded Code Coverage Processing (GitHub Upstream Incident)
    Resolved —
    Started Apr 27, 2026, 10:36 PM UTC · Resolved Apr 27, 2026, 10:36 PM UTC
    Code Coverage
    2 updates · show timeline
    • identified · Apr 27, 2026, 05:51 PM UTC

      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)

    • resolved · Apr 28, 2026, 01:14 AM UTC

      Status: Resolved This incident has been resolved. Affected components Code Coverage (Operational)

    Latest: Status: Resolved This incident has been resolved. Affected components Code Coverage (Operational)

See the full Qlty Software outage history

16 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 9 incidents
  • Degraded Code Coverage Processing (GitHub Upstream Incident) Resolved
    Started Apr 27, 2026, 10:36 PM UTC · Resolved Apr 27, 2026, 10:36 PM UTC · —
  • Security Status Report: Trivy v0.69.4 Resolved
    Started Apr 22, 2026, 02:46 PM UTC · Resolved Apr 22, 2026, 02:46 PM UTC · —
  • Delayed Commit Statuses Resolved
    Started Apr 21, 2026, 09:35 PM UTC · Resolved Apr 21, 2026, 09:35 PM UTC · —
  • Delayed Commit Statuses Resolved
    Started Apr 21, 2026, 09:19 PM UTC · Resolved Apr 21, 2026, 09:35 PM UTC · 15m
  • Format builds failing Resolved
    Started Apr 15, 2026, 05:19 PM UTC · Resolved Apr 15, 2026, 05:19 PM UTC · —
  • Format builds failing Resolved
    Started Apr 02, 2026, 10:22 PM UTC · Resolved Apr 15, 2026, 05:19 PM UTC · 12d 18h
  • Coverage Queue Backup Resolved
    Started Mar 31, 2026, 10:41 PM UTC · Resolved Mar 31, 2026, 10:41 PM UTC · —
  • Coverage Queue Backup Resolved
    Started Mar 30, 2026, 02:05 PM UTC · Resolved Mar 31, 2026, 10:41 PM UTC · 1d 8h

See Qlty Software in your Pingoru dashboard

Monitor Qlty Software alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Qlty Software to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Qlty Software incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Qlty Software or see every provider at once.

Maintenance calendar

Scheduled Qlty Software maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Qlty Software status change, one inbox

Pingoru watches Qlty Software's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Qlty Software reports on 5 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Qlty Software alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Qlty Software maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Qlty Software services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Qlty Software from the same account, with per-user notification preferences for any monitor.

Get notified on Qlty Software status changes

Pingoru watches Qlty Software's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Qlty Software free

Monitor Qlty Software along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Qlty Software and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Qlty Software uptime & incident history

See 90 days of Qlty Software uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Qlty Software uptime history

Frequently asked questions

What is Qlty Software's uptime?
Over the last 90 days, Qlty Software reported 96.00% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.qlty.sh — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Qlty Software's uptime history rolling forward in real time.
Has Qlty Software had outages in 2026?
Yes — Qlty Software has had 17 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Qlty Software outage?
The most recent Qlty Software incident was "Degraded Code Coverage Processing (GitHub Upstream Incident)", which started on April 27, 2026 and was resolved on April 27, 2026. Pingoru captured this directly from https://status.qlty.sh. See the full incident card above for affected components and the update timeline.
How often does Qlty Software have outages?
Based on the last 90 days, Qlty Software averages 5.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Qlty Software's status page?
Qlty Software's official status page is https://status.qlty.sh. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Qlty Software down right now?
Qlty Software is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Qlty Software reports a change. Current status is based on 5 tracked services.
How does Pingoru know if Qlty Software is down?
We read https://status.qlty.sh directly, using Qlty Software's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Qlty Software has an outage?
Create a free Pingoru account and add Qlty Software as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Qlty Software's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Qlty Software incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Qlty Software issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Qlty Software status?
We use Qlty Software's own status page at https://status.qlty.sh. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Qlty Software components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Qlty Software's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Qlty Software free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →