Coveralls status history
Current state: operational — “All Systems Operational” per https://status.coveralls.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Coveralls incidents last?
From 22 incidents with a vendor-posted start and resolve time. Longest on record: Elevated 504 Timeout Errors — 21.3 days (2025-09-03 18:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (22)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-11 19:02 UTC | "Website under heavy load" warning | resolved | none | 2 h 07 min |
| 2026-07-15 17:28 UTC | Increased latency for large repos | resolved | none | 5 d 0 h |
| 2026-07-10 15:00 UTC | Increased latency for large repos | resolved | none | 2 d 23 h |
| 2026-07-07 16:43 UTC | Increased latency for large repos | resolved | none | 11 h 56 min |
| 2026-05-18 16:41 UTC | Increased latency for large projects | resolved | none | 9 d 23 h |
| 2026-05-10 14:44 UTC | Unschedule maintenance | resolved | none | 27 min |
| 2026-02-24 22:52 UTC | Service outage (RESTORED, MONITORING) | postmortem | none | 2 d 23 h |
| 2026-02-02 17:33 UTC | All Systems Operational | resolved | none | 0 min |
| 2025-12-19 14:34 UTC | Elevated Latency in APAC and EU | resolved | none | 49 min |
| 2025-12-18 14:51 UTC | Elevated Latency in APAC and EU | resolved | none | 2 h 07 min |
| 2025-11-17 16:35 UTC | Elevated Latency | resolved | none | 3 h 08 min |
| 2025-11-10 16:14 UTC | Elevated Latency | resolved | minor | 2 h 41 min |
| 2025-10-24 18:35 UTC | 504 Gateway Timeouts (Resolved) | resolved | none | 3 h 18 min |
| 2025-10-13 18:02 UTC | Some reports of 504 Timeouts | resolved | none | 5 h 13 min |
| 2025-10-10 15:23 UTC | 504 Timeouts (Resolved) | resolved | none | 3 h 37 min |
| 2025-09-26 15:28 UTC | 504 Timeout Errors on Coverage Uploads | resolved | none | 3 d 0 h |
| 2025-09-03 18:00 UTC | Elevated 504 Timeout Errors | postmortem | none | 21 d 6 h |
| 2025-08-20 15:48 UTC | More reports of “Website under heavy load” | postmortem | minor | 6 h 33 min |
| 2025-08-19 15:21 UTC | Reports of "Website under heavy load" errors | postmortem | minor | 2 h 04 min |
| 2025-08-18 19:25 UTC | Reports of "Website under heavy load" errors | postmortem | minor | 12 h 44 min |
| 2025-08-14 14:35 UTC | Service unavailable with HTML error page or 500 errors | postmortem | minor | 10 min |
| 2025-08-13 17:14 UTC | Intermittent request rejections | postmortem | minor | 2 h 09 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Coveralls with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"coveralls"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}