Vendor Status Watch

← all vendors

Coveralls status history

Current state: operational — “All Systems Operational” per https://status.coveralls.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
4incidents, last 90 days
22incidents on record
Incidents per week, last 12 weeks:

How long do Coveralls incidents last?

3.5 hmedian incident duration22 measured
5.0 days90th percentile1 in 10 ran longer
median, major/critical onlynone posted

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)

StartedIncidentStatusImpactDuration
2026-08-11 19:02 UTC"Website under heavy load" warningresolvednone2 h 07 min
2026-07-15 17:28 UTCIncreased latency for large reposresolvednone5 d 0 h
2026-07-10 15:00 UTCIncreased latency for large reposresolvednone2 d 23 h
2026-07-07 16:43 UTCIncreased latency for large reposresolvednone11 h 56 min
2026-05-18 16:41 UTCIncreased latency for large projectsresolvednone9 d 23 h
2026-05-10 14:44 UTCUnschedule maintenanceresolvednone27 min
2026-02-24 22:52 UTCService outage (RESTORED, MONITORING)postmortemnone2 d 23 h
2026-02-02 17:33 UTCAll Systems Operationalresolvednone0 min
2025-12-19 14:34 UTCElevated Latency in APAC and EUresolvednone49 min
2025-12-18 14:51 UTCElevated Latency in APAC and EUresolvednone2 h 07 min
2025-11-17 16:35 UTCElevated Latencyresolvednone3 h 08 min
2025-11-10 16:14 UTCElevated Latencyresolvedminor2 h 41 min
2025-10-24 18:35 UTC504 Gateway Timeouts (Resolved)resolvednone3 h 18 min
2025-10-13 18:02 UTCSome reports of 504 Timeoutsresolvednone5 h 13 min
2025-10-10 15:23 UTC504 Timeouts (Resolved)resolvednone3 h 37 min
2025-09-26 15:28 UTC504 Timeout Errors on Coverage Uploadsresolvednone3 d 0 h
2025-09-03 18:00 UTCElevated 504 Timeout Errorspostmortemnone21 d 6 h
2025-08-20 15:48 UTCMore reports of “Website under heavy load”postmortemminor6 h 33 min
2025-08-19 15:21 UTCReports of "Website under heavy load" errorspostmortemminor2 h 04 min
2025-08-18 19:25 UTCReports of "Website under heavy load" errorspostmortemminor12 h 44 min
2025-08-14 14:35 UTCService unavailable with HTML error page or 500 errorspostmortemminor10 min
2025-08-13 17:14 UTCIntermittent request rejectionspostmortemminor2 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
}