- Level
- confirmed
- Worst impact
- Degraded
- Components
- Coveralls.io Web, Coveralls.io API
- Down Index
- 24of 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 2h 27m it lasted.
Anything that failed between 2025-02-28 15:32 UTC and 2025-02-28 17:59 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
About 45 minutes ago we started experiencing elevated latency for some repo types. We have scaled up and are monitoring as queues clear for those jobs. Coveralls remains fully operational. All builds should return to baseline in ~20-min.
provider
- resolved
This incident has been resolved.
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-9fffe166a6
Is Coveralls still down?
No, this incident was resolved 2025-02-28 17:59 UTC. For Coveralls's live state, see https://down.guide/coveralls.
How long did it last?
2h 27m, from 2025-02-28 15:32 UTC to 2025-02-28 17:59 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.