DownForAI

Moemate Incident History

9 major incidents detected for Moemate. View live status dashboard →

MajorUnresolved — service still offline

Moemate

On 2026-04-19 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 19, 2026, 03:06 UTCStill offline after 33h 24mView service →
MajorResolved

Moemate

On 2026-04-16 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 71h 42m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 16, 2026, 03:18 UTCResolved: Apr 19, 2026, 03:00 UTCDuration: 71h 42mView service →
MajorResolved

Moemate

On 2026-04-13 at 03:24 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 71h 36m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 13, 2026, 03:24 UTCResolved: Apr 16, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

Moemate

On 2026-04-10 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 10, 2026, 03:12 UTCResolved: Apr 13, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Moemate

On 2026-04-07 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 72h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 7, 2026, 03:00 UTCResolved: Apr 10, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Moemate

On 2026-04-04 at 03:09 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 71h 51m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 4, 2026, 03:09 UTCResolved: Apr 7, 2026, 03:00 UTCDuration: 71h 51mView service →
MajorResolved

Moemate

On 2026-04-01 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 1, 2026, 03:06 UTCResolved: Apr 4, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Moemate

On 2026-03-29 at 03:13 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 71h 47m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 29, 2026, 03:13 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 47mView service →
MajorResolved

Moemate

On 2026-03-26 at 08:36 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident has been resolved after approximately 66h 24m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 26, 2026, 08:36 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 66h 24mView service →
← Back to all incidents