- Level
- confirmed
- Worst impact
- Degraded
- Components
- Coveralls.io Web, Coveralls.io API
- Regions
- us
- Down Index
- 28of 100
What to do
Check whether you use Coveralls Coveralls.io Web, Coveralls.io API in us. 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 5d it lasted.
Anything that failed between 2026-07-15 17:28 UTC and 2026-07-20 17:32 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 6
- monitoring
All systems fully functional. We have identified increased latency for large repos again and have proactively arrested sources of excess requests. We expect to restore normal latency within the hour.
provider
- monitoring
We have reduced traffic in affected queues by 75%. We still expect to clear the queue within about 1 hr. We will post updates here. If you think you may have been paused as a user with a large repo (>=5K source files) that has uploaded 3-10x normal daily uploads, please reach out to us at support@coveralls.io and we'll confirm and give you some next steps to avoid further pauses (see Usage Add-Ons at https://coveralls.io/pricing).
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We are continuing to proactively monitor and clear the large repo queues. We are working on a longer term solution over the weekend and will post about it in the postmortem for this issue when complete. We will keep this incident open as long as we have large repo queues with above-average latency.
provider
- monitoring
Latency remains elevated by about 30% for large repos. We are continuing to monitor and do what we can to mitigate until we can implement a longer-term solution.
provider
- resolved
This issue was resolved over the weekend. We will continue to monitor for elevated latency in the modified queues.
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-4d3802c6d0
Is Coveralls still down?
No, this incident was resolved 2026-07-20 17:32 UTC. For Coveralls's live state, see https://down.guide/coveralls.
How long did it last?
5d, from 2026-07-15 17:28 UTC to 2026-07-20 17:32 UTC, by the times Coveralls posted.
What was affected?
Coveralls named Coveralls.io Web, Coveralls.io API in us.
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.