Groups.io Outage History

Groups.io is up right now

Groups.io had 3 outages in the last 2 years totaling 1h 17m of downtime — averaging 0.1 incidents per month.

There were 3 Groups.io outages since May 14, 2025 totaling 1h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.groups.io

Notice August 28, 2026

Main Database

Detected by Pingoru
Aug 28, 2026, 12:54 PM UTC
Resolved
Aug 28, 2026, 01:20 PM UTC
Duration
26m
Affected: WebEmailAPI ServerMessage SearchGroup SearchFiles SearchDatabase SearchWiki Search
Timeline · 2 updates
  1. investigating Aug 28, 2026, 12:54 PM UTC

    The main database machine has frozen.

  2. resolved Aug 28, 2026, 01:20 PM UTC

    We have rebooted the machine and the site is back online.

Read the full incident report →

Notice November 14, 2025

High rate of errors

Detected by Pingoru
Nov 14, 2025, 02:44 PM UTC
Resolved
Nov 14, 2025, 03:23 PM UTC
Duration
38m
Affected: WebEmailAPI ServerMessage SearchGroup SearchFiles SearchDatabase SearchWiki Search
Timeline · 4 updates
  1. investigating Nov 14, 2025, 02:44 PM UTC

    We're seeing high rates of errors on the service.

  2. identified Nov 14, 2025, 02:46 PM UTC

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

  3. identified Nov 14, 2025, 03:03 PM UTC

    We have identified the issue and are working on a fix.

  4. resolved Nov 14, 2025, 03:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 14, 2025

Unscheduled Downtime

Detected by Pingoru
May 14, 2025, 10:07 PM UTC
Resolved
May 14, 2025, 10:19 PM UTC
Duration
12m
Affected: WebEmailAPI ServerMessage SearchGroup SearchFiles SearchDatabase SearchWiki Search
Timeline · 3 updates
  1. investigating May 14, 2025, 10:07 PM UTC

    The main database machine froze up. We are in the process of rebooting it now.

  2. investigating May 14, 2025, 10:08 PM UTC

    We are continuing to investigate this issue.

  3. resolved May 14, 2025, 10:19 PM UTC

    The main database machine has been rebooted.

Read the full incident report →