Elevated Latency

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 3h 14m it lasted.

  Anything that failed between 2025-04-30 17:19 UTC and 2025-04-30 20:33 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 5

1. investigatingApr 30, 2025, 5:19 PM UTC

   We are currently investigating this issue.

   provider

2. identifiedApr 30, 2025, 6:35 PM UTC

   The issue has been identified and a fix is being implemented.

   provider

3. monitoringApr 30, 2025, 7:19 PM UTC

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

   provider

4. monitoringApr 30, 2025, 7:51 PM UTC

   We are continuing to monitor for any further issues.

   provider

5. resolvedApr 30, 2025, 8:33 PM UTC

   This incident is resolved. Performance normal for all new builds is normal. All jobs in backed up queues have been cleared with the exception of secondary and tertiary queues for outlier repos. We will be clearing those manually over the next several hours as traffic allows.

   provider

Corrections

None so far.

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