Delayed Coverage Calculations for Some Users

What to do

• Check whether you use Coveralls Coveralls.io Web, Coveralls.io API. 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 12h 38m it lasted.

  Anything that failed between 2025-06-03 15:33 UTC and 2025-06-04 04: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 3

1. monitoringJun 3, 2025, 3:33 PM UTC

   We are continuing to clear a backlog of background processing jobs for builds submitted in the past 18-24 hrs. While all systems are operational, there will continue to be latency on build times until we clear all background job queues, which are FIFO. Current estimate: 1-hour. We will post updates here until build times return to normal.

   provider

2. monitoringJun 3, 2025, 5:34 PM UTC

   We took the following action to more quickly restore normal build times for all _new_ builds today: - We moved all unfinished background jobs from yesterday (Jun 2) into holding queues in order to restore normal build times for new builds from today (Jun 3). - We scaled resources to more quickly drain the existing queues of jobs from new builds from today (Jun 3). We will monitor progress on all new builds and provide updates here until we're fully caught up (zero (0) background jobs in queue). Thanks for your patience in the meantime as we restore the best possible performance to the service.

   provider

3. resolvedJun 4, 2025, 4:11 AM UTC

   All builds from today (Jun 3) have been processed. As background job queues cleared, build times returned to normal. We will continue monitoring.

   provider

Corrections

None so far.

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