Skip to main content
Coveralls

Elevated Latency for some users

Degraded Lasted 14h 3m · started · Coveralls's page

Level
confirmed
Worst impact
Degraded
Components
Coveralls.io Web, Coveralls.io API

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

    Anything that failed between 2025-06-17 13:34 UTC and 2025-06-18 03:37 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. identified

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

    provider

  2. monitoring

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

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-f417e7a56f

Is Coveralls still down?

No, this incident was resolved 2025-06-18 03:37 UTC. For Coveralls's live state, see https://down.guide/coveralls.

How long did it last?

14h 3m, from 2025-06-17 13:34 UTC to 2025-06-18 03:37 UTC, by the times Coveralls posted.

What was affected?

Coveralls named Coveralls.io Web, Coveralls.io API.

What caused it?

Coveralls hasn't published a root cause. If it does, it shows here.

Where does this come from?

Coveralls's official status page, https://status.coveralls.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.