Elevated Reports of 504 Timeout Errors

All systems operational.

Earlier today (6:45–7:45 AM PDT), we received elevated reports of 504 timeout errors. We have not been able to reproduce the issue since, but if you are still experiencing errors, please contact us at support@coveralls.io.

The affected areas may include:

- Coverage Report Uploads (/api/v1/jobs)
- Add Repos Page
- Repo Page
- Source File Page

Fixes for the Add Repos, Repo, and Source File pages are scheduled to be deployed by end of day (PDT).

All systems operational.

We have released one of two parts of a near-term solution into production resolving a minority subset of 504 errors. We are still working on releasing part two into production.

Subscribe for updates at this status page, or follow this public tracking issue for updates:
https://github.com/lemurheavy/coveralls-public/issues/1757

All systems operational.

Continuing to keep this open until we have released our short-term fix into production.

Subscribe for updates at this status page, or follow this public tracking issue for updates:
https://github.com/lemurheavy/coveralls-public/issues/1757

We are still working on a near-term fix. We will post here, and here when complete:
https://github.com/lemurheavy/coveralls-public/issues/1757

We’re currently seeing elevated reports of 504 Timeout errors affecting some customers on a subset of Coveralls pages, including:

- Source File pages
- Repo pages
- Add Repos pages

All systems and pages are generally operational; a subset of customers are experiencing these errors, sometimes intermittently.

There is a public tracking issue for the Source File timeout errors here:
https://github.com/lemurheavy/coveralls-public/issues/1757

Fix in progress:
We’re implementing a short-term fix over the next 24–48 hours, which should eliminate the timeouts.

A longer-term fix is also planned, but will roll out over several weeks, but early phases of that implementation should also reduce the request times that were originally triggering the 504 timeouts.

What you can do:
If you're currently affected, we recommend following updates here, and subscribing to the public issue: https://github.com/lemurheavy/coveralls-public/issues/1757

If your issue pattern differs from above, or you suspect a different root cause, reach out to support@coveralls.io, and we'll verify for you.