New Multi-region uptime checks and custom-domain status pages

Groove Outage History

Daily provider-status observations and published incident history for Groove.

Operational

Groove is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Groove for future changes.

100% of 37 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

3 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

May 2026
SMTP - Mail delivery issues
major Source not attested
Last archived state: resolved
View archived record details
investigating
We're investigating an issue with an upstream SMTP provider causing issue with mail delivery
Web application and API outage
major Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue.
Web application and API outage
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
We are currently investigating elevated error rates and intermittent timeouts affecting parts of the platform. The issue appears related to instability within our Kubernetes infrastructure, which caused a large number of application instances to temporarily fail health checks and be removed from service rotation. We have stabilized the affected services and are continuing to monitor the cluster closely. At this time, core services are recovering and request success rates are improving, thou...
identified
The issue has been identified.