# Service Disruption due to "Invalid SSL Certificate"

- Provider: [Coveralls](https://down.guide/coveralls)
- Level: confirmed
- Impact: Major outage
- lasted 30m
- started 2025-01-22 15:08 UTC
- Coveralls.io Web, Coveralls.io API
- id: DWN-c9862482f2
- Official page: https://stspg.io/kx2z31k0y2tm

## Updates from Coveralls
### 2025-01-22 15:08 UTC: investigating
We are currently investigating this issue.

### 2025-01-22 15:27 UTC: identified
The issue has been identified and a fix is being implemented.

### 2025-01-22 15:33 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2025-01-22 15:37 UTC: resolved
This incident has been resolved.

### 2025-01-22 18:09 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).