Qlty Software incident
Degraded Code Coverage Processing (GitHub Upstream Incident)
Affected components
Update 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 27, 2026, 10:36 PM UTC
Status: Resolved This incident has been resolved. Affected components Code Coverage (Operational)
Looking to track Qlty Software downtime and outages?
Pingoru polls Qlty Software's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Qlty Software reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Qlty Software alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required