Increased latency for Large Repos (5k+ source files)

What to do

• Check whether you use Coveralls Coveralls.io Web, Coveralls.io API in eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 6h 52m it lasted.

  Anything that failed between 2026-09-30 13:19 UTC and 2026-09-30 20:11 UTC may need a replay.

• Subscribe to Coveralls's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=coveralls works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Coveralls 4

1. monitoringSep 30, 2026, 1:19 PM UTC

   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.

   provider

2. monitoringSep 30, 2026, 4:25 PM UTC

   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.

   provider

3. resolvedSep 30, 2026, 8:11 PM UTC

   This incident has been resolved.

   provider

4. postmortemOct 11, 2026, 6:55 PM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.