- Level
- confirmed
- Worst impact
- Degraded
- Components
- Coveralls.io Web, Coveralls.io API
- Down Index
- 26of 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 5h 13m it lasted.
Anything that failed between 2025-10-13 18:02 UTC and 2025-10-13 23:15 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 2
- monitoring
We have received some reports of 504 errors this morning. We are monitoring to avoid further occurrences. We are looking into any gaps in our new monitoring regime, which has drastically reduced occurrences, to see where we can further improve.
provider
- resolved
We have received no further reports of 504 timeout errors on coverage report uploads today, but we continue to monitor and will continue trying to improve our mitigations.
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-2bf6693502
Is Coveralls still down?
No, this incident was resolved 2025-10-13 23:15 UTC. For Coveralls's live state, see https://down.guide/coveralls.
How long did it last?
5h 13m, from 2025-10-13 18:02 UTC to 2025-10-13 23:15 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.