- Level
- confirmed
- Worst impact
- Degraded
- Components
- Coveralls.io Web, Coveralls.io API
- Down Index
- 13of 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 0m it lasted.
Anything that failed between 2025-07-28 16:30 UTC and 2025-07-28 16:30 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 1
- resolved
We experienced a period of elevated latency due to high traffic for about 4 hours on Monday Morning, Jul 28, from about 5am-9am PDT. We scaled servers to meet demand and have now resolved ongoing latency. Please allow another ~15-20 min to clear any remaining backlog.
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-c4fb5b9fe9
Is Coveralls still down?
No, this incident was resolved 2025-07-28 16:30 UTC. For Coveralls's live state, see https://down.guide/coveralls.
How long did it last?
0m, from 2025-07-28 16:30 UTC to 2025-07-28 16:30 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.