Coveralls Outage History
15 incidents recorded over the last 365 days, 14 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Coveralls Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 30, 2026 | Increased latency for Large Repos (5k+ source files)# Update: Major Performance Optimization Released for Heavy Repo Builds Triggered by this latest incident, we've released a major optimization to our code that processes large \(aka. “heavy”\) repos \(>=5K source… | 6h 52m | Resolved |
| Sep 28, 2026 | Elevated errors rates### Resolved: elevated error rates, Monday September 28, 08:00 to 09:15 PT **Timeline**: Between about 08:00 and 09:12 PST on September 28, some requests to Coveralls returned HTTP 500 errors. Coverage uploads… | 1h 18m | Resolved |
| Aug 11, 2026 | "Website under heavy load" warningThis incident has been resolved. | 2h 7m | Resolved |
| Jul 15, 2026 | Increased latency for large reposThis issue was resolved over the weekend. We will continue to monitor for elevated latency in the modified queues. | 120h 3m | Resolved |
| Jul 10, 2026 | Increased latency for large reposThis 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… | 71h 55m | Resolved |
| Jul 7, 2026 | Increased latency for large reposIncreased 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. | 11h 56m | Resolved |
| May 18, 2026 | Increased latency for large projectsWe are closing this incident. Our main background processing queue for larger repos has had no backups in 48 hrs. We will continue monitoring for recurrence. | 239h 12m | Resolved |
| May 10, 2026 | Unschedule maintenanceThis incident has been resolved. | 27 min | Resolved |
| Feb 25, 2026 | Service outage (RESTORED, MONITORING)# Suspended for Not Paying—While Paying _Latest update: Tuesday, Mar 24_ [This post-mortem is also available as a PDF](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/Coveralls-Pos… | 67h 1m | Resolved |
| Feb 2, 2026 | All Systems OperationalJust a note to address the gap in our Coverage Calculation Background Job Dequeue Time Graph today, MON, FEB 2 from 00:15:00 PST to 07:35:00 PST: Coveralls experienced no disruption in service at this time. Instead, a… | 0 min | Resolved |
| Jan 11, 2026 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Dec 19, 2025 | Elevated Latency in APAC and EUWe had to pause some queues to recover performance for new jobs, but will clear those as soon as we've recovered normal build times for new jobs (ETA: 15-min). If you are a user in APAC or EU, you may have had your… | 49 min | Resolved |
| Dec 18, 2025 | Elevated Latency in APAC and EUBuild times are normal for all new builds. Background queues have been cleared of 99% of backlogged jobs; the only ones that remain are for large repos (>5K source files), which should clear in the next 30-45 minutes… | 2h 7m | Resolved |
| Nov 17, 2025 | Elevated LatencyThis incident has been resolved. Build times for all new builds is normal across the board. We are still clearing a backlog of background jobs, which should be clear in the next 15-20-min. If you are having issues… | 3h 8m | Resolved |
| Nov 10, 2025 | Elevated LatencyWe have attempted to improve latency this morning for new jobs from users in EU and US time zones, which has meant offloading older jobs to specialized queues with scaled up resources, which, at this point, have already… | 2h 24m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Coveralls incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Coveralls Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Coveralls acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Coveralls outage in this window ran 9d 23h, against a mean recovery of 1d 11h. If you depend on Coveralls in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.