DownForAI

AI Incidents — May 2026

79 major incidents detected across AI services in May 2026.

MajorResolved

SillyTavern

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

Figgs AI

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

Robin AI

On 2026-05-12 at 06:15 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 68h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 12, 2026, 06:15 UTCResolved: May 15, 2026, 03:00 UTCDuration: 68h 45mView service →
MajorResolved

Sizzle

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

Started: May 12, 2026, 06:00 UTCResolved: May 15, 2026, 03:00 UTCDuration: 69hView service →
MajorResolved

Babbel

On 2026-05-12 at 05:15 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 69h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 12, 2026, 05:15 UTCResolved: May 15, 2026, 03:00 UTCDuration: 69h 45mView service →
MajorResolved

Trae

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

Started: May 12, 2026, 05:00 UTCResolved: May 15, 2026, 03:00 UTCDuration: 70hView service →
MajorResolved

Knowji

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

Started: May 11, 2026, 03:00 UTCResolved: May 12, 2026, 01:00 UTCDuration: 22hView service →
MajorResolved

Knewton Alta

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

Started: May 11, 2026, 01:48 UTCResolved: May 11, 2026, 03:48 UTCDuration: 2hView service →
MajorResolved

Knewton Alta

On 2026-05-10 at 19:42 UTC, DownForAI monitoring detected a significant service issue affecting Knewton Alta. 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 10, 2026, 19:42 UTCResolved: May 10, 2026, 20:06 UTCDuration: 24mView service →
MajorResolved

Knewton Alta

On 2026-05-10 at 12:54 UTC, DownForAI monitoring detected a significant service issue affecting Knewton Alta. 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 10, 2026, 12:54 UTCResolved: May 10, 2026, 13:18 UTCDuration: 24mView service →
MajorResolved

Parloa

On 2026-05-10 at 07:48 UTC, DownForAI monitoring detected a significant service issue affecting Parloa. 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 10, 2026, 07:48 UTCResolved: May 10, 2026, 08:12 UTCDuration: 24mView service →
MajorResolved

Salad

On 2026-05-10 at 07:36 UTC, DownForAI monitoring detected a significant service issue affecting Salad. 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 10, 2026, 07:36 UTCResolved: May 10, 2026, 08:00 UTCDuration: 24mView service →
MajorResolved

AI Dungeon

On 2026-05-10 at 07:24 UTC, DownForAI monitoring detected a significant service issue affecting AI Dungeon. The incident has been resolved after approximately 1h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 10, 2026, 07:24 UTCResolved: May 10, 2026, 08:24 UTCDuration: 1hView service →
MajorResolved

Figgs AI

On 2026-05-10 at 03:24 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. 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: May 10, 2026, 03:24 UTCResolved: May 13, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

SillyTavern

On 2026-05-10 at 03:24 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. 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: May 10, 2026, 03:24 UTCResolved: May 13, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

Robin AI

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

Started: May 10, 2026, 03:00 UTCResolved: May 12, 2026, 03:00 UTCDuration: 48hView service →
MajorResolved

Sizzle

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

Started: May 9, 2026, 03:42 UTCResolved: May 12, 2026, 03:00 UTCDuration: 71h 18mView service →
MajorResolved

Trae

On 2026-05-09 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Trae. 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: May 9, 2026, 03:18 UTCResolved: May 12, 2026, 03:00 UTCDuration: 71h 42mView service →
MajorResolved

Babbel

On 2026-05-09 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. 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: May 9, 2026, 03:18 UTCResolved: May 12, 2026, 03:00 UTCDuration: 71h 42mView service →
MajorResolved

Knowji

On 2026-05-08 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. 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: May 8, 2026, 03:18 UTCResolved: May 11, 2026, 03:00 UTCDuration: 71h 42mView service →
MajorResolved

SillyTavern

On 2026-05-07 at 03:24 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. 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: May 7, 2026, 03:24 UTCResolved: May 10, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

Figgs AI

On 2026-05-07 at 03:24 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. 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: May 7, 2026, 03:24 UTCResolved: May 10, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

Robin AI

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

Holoworld

On 2026-05-06 at 22:24 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. 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 6, 2026, 22:24 UTCResolved: May 6, 2026, 22:54 UTCDuration: 30mView service →
MajorResolved

Holoworld

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

Started: May 6, 2026, 19:54 UTCResolved: May 6, 2026, 20:54 UTCDuration: 1hView service →
MajorResolved

Sizzle

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

Started: May 6, 2026, 04:00 UTCResolved: May 9, 2026, 03:00 UTCDuration: 71hView service →
MajorResolved

Trae

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

Babbel

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

NannyML

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

Started: May 6, 2026, 03:06 UTCResolved: May 8, 2026, 16:24 UTCDuration: 61h 18mView service →
MajorResolved

OpenAI Sora

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

Started: May 5, 2026, 06:42 UTCResolved: May 8, 2026, 03:00 UTCDuration: 68h 18mView service →
← Back to all incidents