Increased latency for large projects

What to do

• Check whether you use Coveralls Coveralls.io Web in 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 9d 23h it lasted.

  Anything that failed between 2026-05-18 16:41 UTC and 2026-05-28 15:53 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 9

1. identifiedMay 18, 2026, 4:41 PM UTC

   We have received reports of increased report latency for larger projects (5K file and up). We are doing our best to clear the background job queues for these projects. If you have one of these projects, feel free to reach out and we'll check status for you.

   provider

2. monitoringMay 18, 2026, 5:37 PM UTC

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

   provider

3. monitoringMay 19, 2026, 1:36 PM UTC

   We are still receiving reports of latency for large projects and are seeing backlogs of background jobs in queues dedicated to large repos (5K+ source files). We may pause some outlier repos with excessive numbers of jobs in order to clear general traffic. If you believe you may have been paused, reach out and we'll let you know.

   provider

4. monitoringMay 20, 2026, 1:48 PM UTC

   We are keeping this incident open as we continue monitoring.

   provider

5. monitoringMay 20, 2026, 2:06 PM UTC

   We have moved all repos with more than 300 jobs in queue to dedicated queues for processing. These 7 repos were responsible for 75% traffic in our heavy repos queue. This move allows us to provide normal processing times for non-outlier repos and dedicated resources to outlier repos. Outlier repos by their job volume will still take longer to clear. If you believe you may be one of these outlier repos, please reach out and we'll confirm and give you an idea of when your jobs will be processed. If you'd like faster processing, we can also pause processing on older job, for instance, anything older than 1 hour (or 2 hours, or 3 hours) ago.

   provider

6. monitoringMay 21, 2026, 4:23 PM UTC

   We continue to monitor background processing queues for larger repos (5K+ files), as we continue offloading incoming jobs from the outlier repos whose volume led to the original backlog. If you think you may have been paused as one of these repos with outlier-level volume, please reach out to us at support@coveralls.io and we'll confirm status and get you an ETA on when your remaining jobs will be processed.

   provider

7. monitoringMay 25, 2026, 8:06 PM UTC

   We are continuing to monitor for any further issues.

   provider

8. monitoringMay 27, 2026, 10:18 PM UTC

   We've cleared the backlog of background jobs for larger projects from our heavy project queues, with the exception of nine projects whose volume continues to exceed our daily fair use thresholds. Those nine have been redirected to secondary and tertiary queues that drain only after the primary queue is clear. Most of their jobs have now been processed, but a few projects generate more jobs than a normal day + overnight cycle can drain, so some backlog remains. We're continuing to work those queues down manually. If you think one of your projects may be affected, reach out to us at support@coveralls.io and we'll check status for you.

   provider

9. resolvedMay 28, 2026, 3:53 PM UTC

   We are closing this incident. Our main background processing queue for larger repos has had no backups in 48 hrs. We will continue monitoring for recurrence.

   provider

Corrections

None so far.

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