Resolved after 1 hour 18 minutes, affecting Coveralls.io Web and Coveralls.io API, on September 28, 2026.
### Resolved: elevated error rates, Monday September 28, 08:00 to 09:15 PT **Timeline**: Between about 08:00 and 09:12 PST on September 28, some requests to Coveralls returned HTTP 500 errors. Coverage uploads, GitHub webhook events, badges, and coverage pages were affected. Failures were intermittent at first and peaked toward the end of the window. Service was fully restored at 09:12 PST. **Cause**: a capacity issue with our primary database. We have have added capacity, enabled automatic scaling, and changed our monitoring triggers to be alerted well before this kind of issue can recur. **What to do**: If you were affected: re-run any CI job that uploaded coverage to Coveralls between 08:00 and 09:15 PT on September 28, or simply push a new commit. No data was lost or corrupted; those uploads simply did not land. We are sorry for the disruption.
Affected components
Update timeline
- investigating Sep 28, 2026, 04:03 PM UTC
We are currently investigating this issue.
- identified Sep 28, 2026, 04:11 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 28, 2026, 04:13 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Sep 28, 2026, 04:14 PM UTC
Operational in all regions. We are continuing to monitor for any further issues.
- monitoring Sep 28, 2026, 05:02 PM UTC
We are continuing to monitor for any further issues.
- resolved Sep 28, 2026, 05:21 PM UTC
This incident has been resolved.
- postmortem Sep 28, 2026, 06:47 PM UTC
### Resolved: elevated error rates, Monday September 28, 08:00 to 09:15 PT **Timeline**: Between about 08:00 and 09:12 PST on September 28, some requests to Coveralls returned HTTP 500 errors. Coverage uploads, GitHub webhook events, badges, and coverage pages were affected. Failures were intermittent at first and peaked toward the end of the window. Service was fully restored at 09:12 PST. **Cause**: a capacity issue with our primary database. We have have added capacity, enabled automatic scaling, and changed our monitoring triggers to be alerted well before this kind of issue can recur. **What to do**: If you were affected: re-run any CI job that uploaded coverage to Coveralls between 08:00 and 09:15 PT on September 28, or simply push a new commit. No data was lost or corrupted; those uploads simply did not land. We are sorry for the disruption.
Your product runs on more than Coveralls
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services