Coveralls is in Read Only mode while we work on updating the system. Sorry for the inconvenience.

VIGILANCE! Check this page any time you notice a problem with coveralls

All Systems Operational

Coveralls.io Web Operational
Coveralls.io API Operational
GitHub Operational
Travis CI API Operational
Pusher Presence channels Operational
Pusher WebSocket client API Operational
Stripe API Operational
New Relic Metric API : US Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Average Web/API Response Time
Fetching
Coverage Calculation Background Job Dequeue Time ?
Fetching
Jul 22, 2026

No incidents reported today.

Jul 21, 2026

No incidents reported.

Jul 20, 2026
Resolved - This issue was resolved over the weekend. We will continue to monitor for elevated latency in the modified queues.
Jul 20, 10:32 PDT
Update - Latency remains elevated by about 30% for large repos. We are continuing to monitor and do what we can to mitigate until we can implement a longer-term solution.
Jul 17, 08:48 PDT
Update - We are continuing to proactively monitor and clear the large repo queues.

We are working on a longer term solution over the weekend and will post about it in the postmortem for this issue when complete.

We will keep this incident open as long as we have large repo queues with above-average latency.

Jul 16, 11:25 PDT
Update - We are continuing to monitor for any further issues.
Jul 15, 17:47 PDT
Update - We have reduced traffic in affected queues by 75%. We still expect to clear the queue within about 1 hr. We will post updates here. If you think you may have been paused as a user with a large repo (>=5K source files) that has uploaded 3-10x normal daily uploads, please reach out to us at support@coveralls.io and we'll confirm and give you some next steps to avoid further pauses (see Usage Add-Ons at https://coveralls.io/pricing).
Jul 15, 11:14 PDT
Monitoring - All systems fully functional. We have identified increased latency for large repos again and have proactively arrested sources of excess requests. We expect to restore normal latency within the hour.
Jul 15, 10:28 PDT
Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

Jul 17, 2026
Jul 16, 2026
Jul 15, 2026
Jul 14, 2026

No incidents reported.

Jul 13, 2026
Resolved - This incident has been resolved but we believe it triggered a worsened incident overnight Sun night/Mon morning (US PDT) which has just been resolved. To be confirmed by full RCA, we believe a deluge of large repo uploads tied up individual web servers that handle frontline requests. Each web server is able to recover on its own, and did, but as volume increased all servers were eventually affected, only allowing short windows where requests could get through—rejecting most requests with 504 errors.

We'll post a post-mortem when we understand more about what happened and how to prevent it going forward.

Jul 13, 07:56 PDT
Monitoring - We are continuing to monitor this situation. Latency is much reduced but still elevated. We will close this incident when it's fully restored to normal.
Jul 10, 10:34 PDT
Identified - We are monitoring increased latency for larger repos (5K+ source files) due to elevated traffic in background job queues. We will pause outlier repos (more than 2x average traffic) to allow queues to clear for the general population, then restore once queues have cleared. If you think your repo may have been one of those paused, two things:

1) Reach out to us at support@coveralls.io and we'll confirm; and
2) Consider purchasing a usage add-on so that your jobs are not throttled for fair-use, or an enterprise plan with isolated infrastructure for maximum performance: https://coveralls.io/pricing

Jul 10, 08:00 PDT
Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026
Jul 9, 2026

No incidents reported.

Jul 8, 2026

No incidents reported.