DownForAI

AI Incidents — April 2026

122 major incidents detected across AI services in April 2026.

MajorResolved

Google Gemini

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

Started: Apr 7, 2026, 13:21 UTCResolved: Apr 7, 2026, 15:57 UTCDuration: 2h 36mView service →
MajorResolved

Robin AI

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

Trae

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

SillyTavern

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

Figgs AI

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

Google Gemini

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

Started: Apr 6, 2026, 12:57 UTCResolved: Apr 6, 2026, 15:45 UTCDuration: 2h 48mView service →
MajorResolved

Babbel

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

Started: Apr 6, 2026, 03:09 UTCResolved: Apr 9, 2026, 03:00 UTCDuration: 71h 50mView service →
MajorResolved

Sizzle

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

Started: Apr 6, 2026, 03:09 UTCResolved: Apr 9, 2026, 03:00 UTCDuration: 71h 50mView service →
MajorResolved

Google Gemini

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

Started: Apr 5, 2026, 14:30 UTCResolved: Apr 5, 2026, 14:42 UTCDuration: 12mView service →
MajorResolved

Wave.video AI

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

SillyTavern

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

Figgs AI

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

Robin AI

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

Trae

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

Babbel

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

Sizzle

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

Clockwise AI

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

Jasper AI

On 2026-04-01 at 20:51 UTC, DownForAI monitoring detected a significant service issue affecting Jasper AI. The incident has been resolved after approximately 12 minutes. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 1, 2026, 20:51 UTCResolved: Apr 1, 2026, 21:03 UTCDuration: 12mView service →
MajorResolved

Deep Dream Generator

On 2026-04-01 at 18:00 UTC, DownForAI monitoring detected a significant service issue affecting Deep Dream Generator. 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 1, 2026, 18:00 UTCResolved: Apr 1, 2026, 18:24 UTCDuration: 24mView service →
MajorResolved

Google Gemini

On 2026-04-01 at 14:51 UTC, DownForAI monitoring detected a significant service issue affecting Google Gemini. 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 1, 2026, 14:51 UTCResolved: Apr 1, 2026, 15:15 UTCDuration: 24mView service →
MajorResolved

MultiOn

On 2026-04-01 at 11:06 UTC, DownForAI monitoring detected a significant service issue affecting MultiOn. 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 1, 2026, 11:06 UTCResolved: Apr 1, 2026, 11:30 UTCDuration: 24mView service →
MajorResolved

MultiOn

On 2026-04-01 at 11:06 UTC, DownForAI monitoring detected a significant service issue affecting MultiOn. 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 1, 2026, 11:06 UTCResolved: Apr 1, 2026, 11:30 UTCDuration: 24mView service →
MajorResolved

Trae

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

Paradot

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

Started: Apr 1, 2026, 03:06 UTCResolved: Apr 1, 2026, 03:18 UTCDuration: 12mView service →
MajorResolved

SillyTavern

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

Figgs AI

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

Writesmith

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

Started: Apr 1, 2026, 03:03 UTCResolved: Apr 3, 2026, 01:00 UTCDuration: 45h 57mView service →
MajorResolved

Robin AI

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

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

Sizzle

On 2026-04-01 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 1, 2026, 03:00 UTCResolved: Apr 3, 2026, 03:00 UTCDuration: 48hView service →
MajorResolved

Babbel

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