DownForAI

AI Incidents — April 2026

122 major incidents detected across AI services in April 2026.

MajorResolved

Trae

On 2026-04-24 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: Apr 24, 2026, 03:12 UTCResolved: Apr 27, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Babbel

On 2026-04-24 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: Apr 24, 2026, 03:12 UTCResolved: Apr 27, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Knowji

On 2026-04-23 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. 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 23, 2026, 03:00 UTCResolved: Apr 26, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Holoworld

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

Started: Apr 22, 2026, 04:54 UTCResolved: Apr 25, 2026, 03:00 UTCDuration: 70h 6mView service →
MajorResolved

Creatie

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

Started: Apr 22, 2026, 04:30 UTCResolved: Apr 25, 2026, 03:00 UTCDuration: 70h 30mView service →
MajorResolved

SillyTavern

On 2026-04-22 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: Apr 22, 2026, 03:24 UTCResolved: Apr 25, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

Figgs AI

On 2026-04-22 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: Apr 22, 2026, 03:24 UTCResolved: Apr 25, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

Robin AI

On 2026-04-22 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: Apr 22, 2026, 03:00 UTCResolved: Apr 25, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Trae

On 2026-04-21 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Trae. 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 21, 2026, 03:06 UTCResolved: Apr 24, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Babbel

On 2026-04-21 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. 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 21, 2026, 03:06 UTCResolved: Apr 24, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Sizzle

On 2026-04-21 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. 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 21, 2026, 03:06 UTCResolved: Apr 24, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Suno

On 2026-04-20 at 19:36 UTC, DownForAI monitoring detected a significant service issue affecting Suno. 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: Apr 20, 2026, 19:36 UTCResolved: Apr 20, 2026, 20:00 UTCDuration: 24mView service →
MajorResolved

OpenAI

On 2026-04-20 at 15:00 UTC, DownForAI monitoring detected a significant service issue affecting OpenAI. The incident has been resolved after approximately 18 minutes. This incident was identified based on a significant volume of user reports.

Started: Apr 20, 2026, 15:00 UTCResolved: Apr 20, 2026, 15:18 UTCDuration: 18mView service →
MajorResolved

Holoworld

On 2026-04-20 at 14:42 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: Apr 20, 2026, 14:42 UTCResolved: Apr 20, 2026, 15:12 UTCDuration: 30mView service →
MajorResolved

OpenAI

On 2026-04-20 at 14:40 UTC, DownForAI monitoring detected a significant service issue affecting OpenAI. The incident has been resolved after approximately 14 minutes. This incident was identified based on a significant volume of user reports.

Started: Apr 20, 2026, 14:40 UTCResolved: Apr 20, 2026, 14:54 UTCDuration: 14mView service →
MajorResolved

Knowji

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

Started: Apr 20, 2026, 05:06 UTCResolved: Apr 23, 2026, 03:00 UTCDuration: 69h 54mView service →
MajorResolved

Stable Video Diffusion

On 2026-04-19 at 23:24 UTC, DownForAI monitoring detected a significant service issue affecting Stable Video Diffusion. 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: Apr 19, 2026, 23:24 UTCResolved: Apr 19, 2026, 23:54 UTCDuration: 30mView service →
MajorResolved

Stability AI

On 2026-04-19 at 23:24 UTC, DownForAI monitoring detected a significant service issue affecting Stability 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: Apr 19, 2026, 23:24 UTCResolved: Apr 19, 2026, 23:48 UTCDuration: 24mView service →
MajorResolved

Figgs AI

On 2026-04-19 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. 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 19, 2026, 03:06 UTCResolved: Apr 22, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

SillyTavern

On 2026-04-19 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. 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 19, 2026, 03:06 UTCResolved: Apr 22, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Robin AI

On 2026-04-19 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: Apr 19, 2026, 03:00 UTCResolved: Apr 22, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Trae

On 2026-04-18 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: Apr 18, 2026, 03:18 UTCResolved: Apr 21, 2026, 03:00 UTCDuration: 71h 42mView service →
MajorResolved

Sizzle

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

Started: Apr 17, 2026, 03:12 UTCResolved: Apr 21, 2026, 03:00 UTCDuration: 95h 48mView service →
MajorResolved

Babbel

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

Started: Apr 17, 2026, 03:12 UTCResolved: Apr 21, 2026, 03:00 UTCDuration: 95h 48mView service →
MajorResolved

Figgs AI

On 2026-04-16 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. 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

SillyTavern

On 2026-04-16 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. 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

Robin AI

On 2026-04-16 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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 16, 2026, 03:06 UTCResolved: Apr 19, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Trae

On 2026-04-16 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Trae. 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: Apr 16, 2026, 03:00 UTCResolved: Apr 18, 2026, 03:00 UTCDuration: 48hView service →
MajorResolved

TutorAI

On 2026-04-15 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting TutorAI. 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: Apr 15, 2026, 03:18 UTCResolved: Apr 15, 2026, 05:18 UTCDuration: 2hView service →
MajorResolved

Sizzle

On 2026-04-15 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. 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: Apr 15, 2026, 03:00 UTCResolved: Apr 17, 2026, 03:00 UTCDuration: 48hView service →
← Back to all incidents