MEE6 Outage History

MEE6 is up right now

MEE6 had 3 outages in the last 2 years totaling 5h 22m of downtime — averaging 0.1 incidents per month.

There were 3 MEE6 outages since October 1, 2025 totaling 5h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://mee6.statuspage.io

Minor May 23, 2026

Twitch Alerts Are not Sent on All Servers

Detected by Pingoru
May 23, 2026, 08:39 AM UTC
Resolved
May 23, 2026, 09:47 AM UTC
Duration
1h 7m
Affected: MEE6 BotCustom Bot
Timeline · 3 updates
  1. investigating May 23, 2026, 08:39 AM UTC

    We are currently investigating this issue.

  2. investigating May 23, 2026, 08:40 AM UTC

    We are continuing to investigate this issue.

  3. resolved May 23, 2026, 09:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 22, 2026

MEE6 Offline/Not working on some servers

Detected by Pingoru
May 22, 2026, 10:24 AM UTC
Resolved
May 22, 2026, 02:10 PM UTC
Duration
3h 45m
Affected: DashboardMEE6 BotWebsiteCustom Bot
Timeline · 2 updates
  1. monitoring May 22, 2026, 10:24 AM UTC

    MEE6 is not working partially, MEE6 dashboard might not be available for some servers. The issue was caused by the power outage in one of datacenters, which is now resolved. MEE6 is recovering, and will be online for everyone as soon as possible. Please accept our apologies for the inconvenience.

  2. resolved May 22, 2026, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 1, 2025

MEE6 Offline/Not working

Detected by Pingoru
Oct 01, 2025, 11:51 AM UTC
Resolved
Oct 01, 2025, 12:20 PM UTC
Duration
29m
Affected: DashboardMEE6 BotCustom Bot
Timeline · 3 updates
  1. investigating Oct 01, 2025, 11:51 AM UTC

    MEE6 is offline or not working on some servers, MEE6 dashboard might not be available for some servers. The issue comes from one of the 3d parties that provide services to MEE6. Both regular MEE6 and custom bots might be affected. We're looking into it, please accept our apologies for the inconvenience.

  2. identified Oct 01, 2025, 11:57 AM UTC

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

  3. resolved Oct 01, 2025, 12:20 PM UTC

    This incident has been resolved.

Read the full incident report →