DownForAI

AI Incidents — May 2026

22 major incidents detected across AI services in May 2026.

MajorResolved

PearAI

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

Started: May 4, 2026, 03:18 UTCResolved: May 4, 2026, 03:48 UTCDuration: 30mView service →
MajorOngoing

Predibase

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

Started: May 4, 2026, 03:18 UTCDuration: ongoingView service →
MajorOngoing

Moemate

On 2026-05-04 at 03:12 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: May 4, 2026, 03:12 UTCDuration: ongoingView service →
MajorOngoing

SillyTavern

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

Started: May 4, 2026, 03:12 UTCDuration: ongoingView service →
MajorOngoing

Figgs AI

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

Started: May 4, 2026, 03:12 UTCDuration: ongoingView service →
MajorOngoing

Robin AI

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

Started: May 4, 2026, 03:06 UTCDuration: ongoingView service →
MajorUnresolved — service still offline

NannyML

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

Started: May 3, 2026, 03:18 UTCStill offline after 32h 46mView service →
MajorUnresolved — service still offline

Play.ht

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

Started: May 3, 2026, 03:18 UTCStill offline after 32h 46mView service →
MajorUnresolved — service still offline

Visual Electric

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

Started: May 3, 2026, 03:12 UTCStill offline after 32h 53mView service →
MajorUnresolved — service still offline

Babbel

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

Started: May 3, 2026, 03:12 UTCStill offline after 32h 53mView service →
MajorUnresolved — service still offline

Trae

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

Started: May 3, 2026, 03:12 UTCStill offline after 32h 53mView service →
MajorUnresolved — service still offline

Safurai

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

Started: May 3, 2026, 03:12 UTCStill offline after 32h 53mView service →
MajorUnresolved — service still offline

Sizzle

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

Started: May 3, 2026, 03:12 UTCStill offline after 32h 53mView service →
MajorResolved

Creatie

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

Started: May 2, 2026, 04:36 UTCResolved: May 4, 2026, 01:24 UTCDuration: 44h 48mView service →
MajorUnresolved — service still offline

Knowji

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

Started: May 2, 2026, 03:18 UTCStill offline after 56h 47mView service →
MajorResolved

Krea AI

On 2026-05-01 at 15:30 UTC, DownForAI monitoring detected a significant service issue affecting Krea AI. The incident has been resolved after approximately 24 minutes. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 1, 2026, 15:30 UTCResolved: May 1, 2026, 15:54 UTCDuration: 24mView service →
MajorResolved

Predibase

On 2026-05-01 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Predibase. 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: May 1, 2026, 03:12 UTCResolved: May 4, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

SillyTavern

On 2026-05-01 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. 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: May 1, 2026, 03:00 UTCResolved: May 4, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Figgs AI

On 2026-05-01 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. 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: May 1, 2026, 03:00 UTCResolved: May 4, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Moemate

On 2026-05-01 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: May 1, 2026, 03:00 UTCResolved: May 4, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Robin AI

On 2026-05-01 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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: May 1, 2026, 03:00 UTCResolved: May 4, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Writecream

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

Started: May 1, 2026, 00:42 UTCResolved: May 1, 2026, 02:36 UTCDuration: 1h 54mView service →
← Back to all incidents