DownForAI

AI Incidents — April 2026

105 major incidents detected across AI services in April 2026.

MajorResolved

Moemate

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

Figgs AI

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

Safurai

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

Trae

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

Visual Electric

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

Robin AI

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

Fetcher

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

Started: Apr 12, 2026, 20:36 UTCResolved: Apr 13, 2026, 15:48 UTCDuration: 19h 12mView service →
MajorResolved

Google Gemini

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

Started: Apr 12, 2026, 13:36 UTCResolved: Apr 12, 2026, 16:48 UTCDuration: 3h 12mView service →
MajorResolved

Sizzle

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

Creatie

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

Started: Apr 11, 2026, 21:42 UTCResolved: Apr 14, 2026, 03:00 UTCDuration: 53h 18mView service →
MajorResolved

Play.ht

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

Babbel

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

Wave.video AI

On 2026-04-11 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Wave.video 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 11, 2026, 03:12 UTCResolved: Apr 11, 2026, 03:42 UTCDuration: 30mView service →
MajorResolved

Google Gemini

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

Started: Apr 10, 2026, 12:30 UTCResolved: Apr 10, 2026, 16:54 UTCDuration: 4h 24mView service →
MajorResolved

SillyTavern

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

Figgs AI

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

Moemate

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

Robin AI

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

Visual Electric

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

Trae

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

Safurai

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

Luminar Neo AI

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

Started: Apr 9, 2026, 17:24 UTCResolved: Apr 12, 2026, 03:00 UTCDuration: 57h 36mView service →
MajorResolved

HuggingChat

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

Started: Apr 9, 2026, 14:21 UTCResolved: Apr 9, 2026, 14:36 UTCDuration: 15mView service →
MajorResolved

Google Gemini

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

Started: Apr 9, 2026, 13:15 UTCResolved: Apr 9, 2026, 15:48 UTCDuration: 2h 33mView service →
MajorResolved

NAVER CLOVA

On 2026-04-09 at 09:51 UTC, DownForAI monitoring detected a significant service issue affecting NAVER CLOVA. 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 9, 2026, 09:51 UTCResolved: Apr 9, 2026, 10:03 UTCDuration: 12mView service →
MajorResolved

Sizzle

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

Babbel

On 2026-04-09 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 9, 2026, 03:00 UTCResolved: Apr 11, 2026, 03:00 UTCDuration: 48hView service →
MajorResolved

Google Gemini

On 2026-04-08 at 15:51 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 8, 2026, 15:51 UTCResolved: Apr 8, 2026, 16:03 UTCDuration: 12mView service →
MajorResolved

Google Gemini

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

Started: Apr 8, 2026, 13:15 UTCResolved: Apr 8, 2026, 15:45 UTCDuration: 2h 30mView service →
MajorResolved

Play.ht

On 2026-04-08 at 03:03 UTC, DownForAI monitoring detected a significant service issue affecting Play.ht. 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 8, 2026, 03:03 UTCResolved: Apr 11, 2026, 03:00 UTCDuration: 71h 57mView service →
← Back to all incidents