Is Coveralls Down?

# Update: Major Performance Optimization Released for Heavy Repo Builds Triggered by this latest incident, we've released a major optimization to our code that processes large \(aka. “heavy”\) repos \(>=5K source files\). Tests over the weekend of Fri, Oct 9-Sun, Oct 11 show a near 20x improvement in performance per average heavy repo build at lower, weekend volumes. While we expect the optimization to continue to drastically improve build times for these repos \(and reduce incidents of increased latency for them\), we won’t know what the aggregate improvement is until we are at full volume this week. We are monitoring to get a sense of where the performance improvement lands, but are hopeful we’ve crossed a significant milestone in how efficiently these builds are processed given the unique challenges they pose. --- [2026-09-30T13:11:32.060-07:00] (resolved) This incident has been resolved. --- [2026-09-30T09:25:29.418-07:00] (monitoring) The root cause of issues with large repos has been fully addressed. We are continuing to clear some backlogged background jobs. We will continue to monitor and report updates here. --- [2026-09-30T11:30:49.714-07:00] (monitoring) Users in Europe and US east coast with large repos (5k+ repos) experienced slow build completion, starting around 2am PST / 5am EST. Behavior: PRs opened between 2am-6am PST may have slow or missing Coveralls PR comments or status checks. We have identified the issue and allocated resources to clear a backlog of background jobs. Jobs should clear and builds should complete in the next ~1hr.

### 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. --- [2026-09-28T10:21:30.300-07:00] (resolved) This incident has been resolved. --- [2026-09-28T10:02:57.110-07:00] (monitoring) We are continuing to monitor for any further issues. --- [2026-09-28T09:14:43.819-07:00] (monitoring) Operational in all regions. We are continuing to monitor for any further issues. --- [2026-09-28T09:13:57.368-07:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-28T09:11:45.170-07:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-28T09:03:25.682-07:00] (investigating) We are currently investigating this issue.