Groups.io Outage History

Groups.io is up right now

Pingoru has recorded 22 incidents for Groups.io: 2 in the last 12 months and 1 in the last 90 days.

Source: status.groups.io

22incidents recorded
2last 12 months
1last 90 days
33 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Groups.io in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202610 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 107 (0%)

Incidents, newest first

Notice August 28, 2026 Main Database 26m Web, Email, API Server, Message Search and 4 more

Started Aug 28, 2026, 12:54 PM UTC· resolved Aug 28, 2026, 01:20 PM UTC

  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 38m Web, Email, API Server, Message Search and 4 more

Started Nov 14, 2025, 02:44 PM UTC· resolved Nov 14, 2025, 03:23 PM UTC

  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 12m Web, Email, API Server, Message Search and 4 more

Started May 14, 2025, 10:07 PM UTC· resolved May 14, 2025, 10:19 PM UTC

  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 →