Groove Outage History

Groove is up right now

Groove had 3 outages in the last 2 years totaling 7h 29m of downtime — averaging 0.1 incidents per month.

There were 3 Groove outages since June 2, 2025 totaling 7h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.groovehq.com

Major May 12, 2026

Web application and API outage

Detected by Pingoru
May 12, 2026, 12:55 PM UTC
Resolved
May 12, 2026, 04:23 PM UTC
Duration
3h 28m
Affected: Web AppInbox API
Timeline · 2 updates
  1. investigating May 12, 2026, 12:55 PM UTC

    We are currently investigating this issue.

  2. resolved May 12, 2026, 04:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 11, 2026

Audit system errors causing degraded performance

Detected by Pingoru
Apr 11, 2026, 04:38 PM UTC
Resolved
Apr 11, 2026, 06:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 11, 2026, 04:38 PM UTC

    Some operations including logins, ticket creation, contact updates, and email ingestion experienced intermittent failures. We identified and resolved an issue with an internal database table that had reached a storage capacity limit, which caused these operations to fail. The issue has been mitigated and services are returning to normal. Incoming emails are continuing to catch back up as we monitor the recovery.

Read the full incident report →

Major June 2, 2025

Degraded service on Groove inbox (Delayed mail fetching, collision detection, realtime updates, sending mail)

Detected by Pingoru
Jun 02, 2025, 02:13 PM UTC
Resolved
Jun 02, 2025, 06:15 PM UTC
Duration
4h 1m
Affected: EmailWeb AppInbox API
Timeline · 3 updates
  1. identified Jun 02, 2025, 02:13 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jun 02, 2025, 05:23 PM UTC

    A fix has been implemented and we are monitoring the results - backlog is currently clearing over the next 30-60 minutes. Expected delays for incoming mails, outgoing mails being sent, rule processing, realtime, and other features during this time.

  3. resolved Jun 02, 2025, 06:15 PM UTC

    This incident has been resolved.

Read the full incident report →