- Level
- confirmed
- Worst impact
- Degraded
- Components
- Coveralls.io Web, Coveralls.io API
- Down Index
- 25of 100
What to do
Check whether you use Coveralls Coveralls.io Web, Coveralls.io API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 31m it lasted.
Anything that failed between 2025-04-24 19:35 UTC and 2025-04-24 23:06 UTC may need a replay.Subscribe to Coveralls's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=coveralls works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Coveralls 9
- investigating
We are investigating elevated latency in our background jobs system. Some users have also reported receiving Timeout errors while trying to load web pages.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We believe the issue is resolved. We are scaling infrastructure to clear any delayed background jobs, and monitoring to ensure latency stays within normal range.
provider
- monitoring
Monitoring for further issues. Performance for new builds is normal. Waiting for dequeue metrics to fall below 50% normal before we lift "degraded performance" rating.
provider
- monitoring
Performance has been restored to standard, and site is fully operational, but we will continue to clear any previously blocked (or retry) jobs we discover in background job queues and monitor performance stats as they clear.
provider
- monitoring
The site remains fully operational, and performance for all new builds is normal. We’re continuing to monitor request and query times closely to identify any long-running queries that may have contributed to recent job processing delays or latency spikes.
provider
- resolved
We’re now closing this incident, several hours after restoring full system stability. Over the past 4 hours, we’ve continued to monitor key requests and queries closely. During that time, we identified a number of previously long-running queries that we’ve either: - Optimized immediately, based on new platform characteristics; or - Added to a short-term optimization backlog for tuning over the next few days. These efforts are part of our ongoing work to adapt all app queries to the updated infrastructure context.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-0151c68f04
Is Coveralls still down?
No, this incident was resolved 2025-04-24 23:06 UTC. For Coveralls's live state, see https://down.guide/coveralls.
How long did it last?
3h 31m, from 2025-04-24 19:35 UTC to 2025-04-24 23:06 UTC, by the times Coveralls posted.
What was affected?
Coveralls named Coveralls.io Web, Coveralls.io API.
What caused it?
Coveralls hasn't published a root cause. If it does, it shows here.
Where does this come from?
Coveralls's official status page, https://status.coveralls.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.