Coveralls is in Read Only mode while we work on updating the system. Sorry for the inconvenience.

VIGILANCE! Check this page any time you notice a problem with coveralls

Elevated errors rates

Incident Report for Coveralls

Postmortem

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.

Posted Sep 28, 2026 - 11:56 PDT

Resolved

This incident has been resolved.

Posted Sep 28, 2026 - 10:21 PDT

Update

We are continuing to monitor for any further issues.

Posted Sep 28, 2026 - 10:02 PDT

Update

Operational in all regions. We are continuing to monitor for any further issues.

Posted Sep 28, 2026 - 09:14 PDT

Monitoring

A fix has been implemented and we are monitoring the results.

Posted Sep 28, 2026 - 09:13 PDT

Identified

The issue has been identified and a fix is being implemented.

Posted Sep 28, 2026 - 09:11 PDT

Investigating

We are currently investigating this issue.

Posted Sep 28, 2026 - 09:03 PDT

This incident affected: Coveralls.io Web and Coveralls.io API.