DownForAI

AI Incidents — April 2026

122 major incidents detected across AI services in April 2026.

MajorResolved

NannyML

On 2026-04-30 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting NannyML. 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 30, 2026, 03:12 UTCResolved: May 3, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Trae

On 2026-04-30 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 30, 2026, 03:06 UTCResolved: May 3, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Sizzle

On 2026-04-30 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 30, 2026, 03:06 UTCResolved: May 3, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Babbel

On 2026-04-30 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 30, 2026, 03:06 UTCResolved: May 3, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

WellSaid Labs

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

Started: Apr 29, 2026, 07:54 UTCResolved: Apr 29, 2026, 10:00 UTCDuration: 2h 6mView service →
MajorResolved

WellSaid Labs

On 2026-04-29 at 05:54 UTC, DownForAI monitoring detected a significant service issue affecting WellSaid Labs. 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: Apr 29, 2026, 05:54 UTCResolved: Apr 29, 2026, 06:54 UTCDuration: 1hView service →
MajorResolved

Knowji

On 2026-04-29 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. 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 29, 2026, 03:12 UTCResolved: May 2, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Stockimg.ai

On 2026-04-28 at 15:24 UTC, DownForAI monitoring detected a significant service issue affecting Stockimg.ai. 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: Apr 28, 2026, 15:24 UTCResolved: Apr 28, 2026, 16:24 UTCDuration: 1hView service →
MajorResolved

Robin AI

On 2026-04-28 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 28, 2026, 03:06 UTCResolved: May 1, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

SillyTavern

On 2026-04-28 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 28, 2026, 03:06 UTCResolved: May 1, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Holoworld

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

Started: Apr 28, 2026, 03:06 UTCResolved: Apr 29, 2026, 23:18 UTCDuration: 44h 12mView service →
MajorResolved

Figgs AI

On 2026-04-28 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 28, 2026, 03:06 UTCResolved: May 1, 2026, 03:00 UTCDuration: 71h 54mView service →
MajorResolved

Creatie

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

Started: Apr 28, 2026, 03:00 UTCResolved: Apr 30, 2026, 05:06 UTCDuration: 50h 6mView service →
MajorResolved

Warp AI

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

NannyML

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

Started: Apr 27, 2026, 18:30 UTCResolved: Apr 30, 2026, 03:00 UTCDuration: 56h 30mView service →
MajorResolved

Trae

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

Babbel

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

Sizzle

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

Knowji

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

Timescale Vector

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

Started: Apr 25, 2026, 13:30 UTCResolved: Apr 27, 2026, 21:30 UTCDuration: 56hView service →
MajorResolved

Creatie

On 2026-04-25 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Creatie. 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 25, 2026, 03:18 UTCResolved: Apr 28, 2026, 03:00 UTCDuration: 71h 42mView service →
MajorResolved

Figgs AI

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

Robin AI

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

SillyTavern

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

Holoworld

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

SciSpace

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

Started: Apr 25, 2026, 02:24 UTCResolved: Apr 27, 2026, 03:00 UTCDuration: 48h 36mView service →
MajorResolved

SeaArt AI

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

Dante AI

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

Started: Apr 24, 2026, 18:49 UTCResolved: Apr 24, 2026, 19:12 UTCDuration: 23mView service →
MajorResolved

Dante AI

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

Sizzle

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

Started: Apr 24, 2026, 03:36 UTCResolved: Apr 27, 2026, 03:00 UTCDuration: 71h 24mView service →
← Back to all incidents