Coveralls Status Page

Sep 30, 2026 · resolved Sep 30

# 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.

Sep 28, 2026 · resolved Sep 28

### 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.

Aug 11, 2026 · resolved Aug 11

This incident has been resolved.

Jul 15, 2026 · resolved Jul 20

This issue was resolved over the weekend. We will continue to monitor for elevated latency in the modified queues.

Jul 10, 2026 · resolved Jul 13

This incident has been resolved but we believe it triggered a worsened incident overnight Sun night/Mon morning (US PDT) which has just been resolved. To be confirmed by full RCA, we believe a deluge of large repo uploads tied up individual web servers that handle frontline requests. Each web server is able to recover on its own, and did, but as volume increased all servers were eventually affected, only allowing short windows where requests could get through—rejecting most requests with 504 errors. We'll post a post-mortem when we understand more about what happened and how to prevent it going forward.

Is Coveralls down right now?

No — Coveralls is up. All systems operational as of Oct 12, 5:46 PM UTC.

What is Coveralls's current status?

Coveralls: All Systems Operational. Alert24 checks Coveralls's status page continuously and can notify you the moment it changes.

How do I get alerted when Coveralls goes down?

Alert24 monitors Coveralls and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.