- Level
- confirmed
- Worst impact
- Major outage
- Components
- Coveralls.io Web, Coveralls.io API
- Down Index
- 43of 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 30m it lasted.
Anything that failed between 2025-01-22 15:08 UTC and 2025-01-22 15:37 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 5
- investigating
We are currently investigating this issue.
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
- resolved
This incident has been resolved.
provider
- postmortem
**Incident**: Service Disruption Due to Failed SSL Certificate Renewal * **Date**: January 22, 2025 * **Duration**: 17 minutes \(07:00-07:17 UTC\) * **Impact**: Service interruption due to SSL certificate issue **Summary**: Coveralls experienced a brief service disruption when our automated SSL certificate renewal process failed. While our SSL certificates auto-renew 30 days before expiration, one unreachable server prevented the renewal process from completing successfully. **Timeline**: * Prior to incident: Multiple automated renewal attempts unsuccessful * 07:00 UTC: Service disruption began * 07:17 UTC: Service restored after infrastructure adjustment **Root Cause**: The incident occurred when one server became unreachable during our SSL certificate auto-renewal process. While our certificates are configured to auto-renew, the renewal process requires successful deployment across our infrastructure. The unreachable server prevented this deployment, ultimately leading to an outage due to “certificate expiration.” **Resolution**: We identified and removed the problematic server from our infrastructure, allowing the SSL certificate renewal and deployment to complete successfully. **Preventive Measures**: 1. Enhanced monitoring for SSL renewal processes 2. Improved early warning system for similar infrastructure issues 3. Updated incident response procedures \(new SOP\) 4. Additional automated health checks We apologize for any disruption this caused and continue working to improve our infrastructure reliability.
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-c9862482f2
Is Coveralls still down?
No, this incident was resolved 2025-01-22 15:37 UTC. For Coveralls's live state, see https://down.guide/coveralls.
How long did it last?
30m, from 2025-01-22 15:08 UTC to 2025-01-22 15:37 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.