Looking for an update now? Check the current status, or follow Coveralls for future changes.
97.3%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
96.7%
30
1
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We are continuing to monitor for any further issues.
monitoring
Operational in all regions. We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Legacy Incident Archive
6 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
"Website under heavy load" warning
Source not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
We are currently experiencing occasional "Website under heavy load" warnings.
We believe this is the second wave of an attack we experienced this weekend involving an army of scraper bots which we successfully mitigated. We believe the attacker may have gotten around an initial phase of defense.
Separate from a DDoS attack, these are millions of individual requests coming from over 280K different IP addresses across 12 different countries, so our standard DDoS protection (IP quarantine) d...
July 2026
Increased latency for large repos
Source not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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.
monitoring
We are continuing to monitor for any further issues.
monitoring
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).
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.
Increased latency for large repos
Source not attested
Last archived state: resolved
View archived record details
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.
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,...
Increased latency for large repos
Source not attested
Last archived state: resolved
View archived record details
monitoring
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: support@coveralls.io.
We expect to clear the general queues by 6pm PDT. After that we will restore processing for outlier and expect that to complete by t...
investigating
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.
May 2026
Increased latency for large projects
Source not attested
Last archived state: resolved
View archived record details
monitoring
We've cleared the backlog of background jobs for larger projects from our heavy project queues, with the exception of nine projects whose volume continues to exceed our daily fair use thresholds. Those nine have been redirected to secondary and tertiary queues that drain only after the primary queue is clear. Most of their jobs have now been processed, but a few projects generate more jobs than a normal day + overnight cycle can drain, so some backlog remains. We're continuing to work those q...
monitoring
We are continuing to monitor for any further issues.
monitoring
We continue to monitor background processing queues for larger repos (5K+ files), as we continue offloading incoming jobs from the outlier repos whose volume led to the original backlog. If you think you may have been paused as one of these repos with outlier-level volume, please reach out to us at support@coveralls.io and we'll confirm status and get you an ETA on when your remaining jobs will be processed.
monitoring
We have moved all repos with more than 300 jobs in queue to dedicated queues for processing. These 7 repos were responsible for 75% traffic in our heavy repos queue. This move allows us to provide normal processing times for non-outlier repos and dedicated resources to outlier repos. Outlier repos by their job volume will still take longer to clear. If you believe you may be one of these outlier repos, please reach out and we'll confirm and give you an idea of when your jobs will be processed...
monitoring
We are keeping this incident open as we continue monitoring.
monitoring
We are still receiving reports of latency for large projects and are seeing backlogs of background jobs in queues dedicated to large repos (5K+ source files). We may pause some outlier repos with excessive numbers of jobs in order to clear general traffic. If you believe you may have been paused, reach out and we'll let you know.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have received reports of increased report latency for larger projects (5K file and up). We are doing our best to clear the background job queues for these projects. If you have one of these projects, feel free to reach out and we'll check status for you.
Unschedule maintenance
Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue with an apparently expired SSL cert. Our orchestration layer shows no issue with certs so we need to dig deeper.
