Groove status history
Current state: operational — “All Systems Operational” per https://status.groovehq.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Groove incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: SMTP - Mail delivery issues — 4.2 h (2026-05-28 15:47 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 (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-05-28 15:47 UTC | SMTP - Mail delivery issues | resolved | major | 4 h 13 min |
| 2026-05-12 12:55 UTC | Web application and API outage | resolved | major | 3 h 28 min |
| 2026-05-11 22:05 UTC | Web application and API outage | resolved | critical | 14 min |
| 2026-04-11 06:30 UTC | Audit system errors causing degraded performance | resolved | major | 0 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 Groove with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"groove"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
