Is Coveralls down?

We are currently experiencing occasional "Website under heavy load" warnings. We believe this is associated with an army of scraper bots we experienced and successfully mitigated this weekend. We believe those bots may have gotten around an initial phase of defense involving managed challenges at our edge provider. Separate from a DDoS attack, these are millions of individual requests coming from over 200K different IP addresses across 10 different countries, so our standard DDoS defense of IP quarantines at our firewall do not apply. We are implementing a second phase of defense and will report updates here.

This was the second wave of the attack we experienced this weekend, broadened and tripled in volume. We implemented a second phase of defense which appear to be working and will continue monitoring for the next hour.

This incident has been resolved.

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.

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 [email protected] and we'll confirm and give you some next steps to avoid further pauses (see Usage Add-Ons at https://coveralls.io/pricing).

We are continuing to monitor for any further issues.

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.

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.

This issue was resolved over the weekend. We will continue to monitor for elevated latency in the modified queues.

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 [email protected] 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

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.

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.

We are seeing increased latency for larger repos (5K source files and greater). While the site is fully operational, you may experience increased delays before receiving finished build pages and coverage notifications to your PRs if your repo had >=5K source files. We are monitoring and will pause any outlier repos (repos with unexplained, excessive usage) to allow general traffic in large repo queues to clear.

We've had too offload some outlier repos to let the general public of users with heavy repos to clear. There were three such repos. We will restart processing on those repos as soon as general queues have cleared. If you think you may be one of the repos with excessive traffic that was paused today, just reach out and we'll let you know: [email protected]. We expect to clear the general queues by 6pm PDT. After that we will restore processing for outlier and expect that to complete by this evening between 10p-12a PDT.

Increased latency for large repos has been resolved for the general public. We will be clearing three outlier repos overnight, which should be fully cleared by tomorrow AM.