DownForAI

AI Incidents — April 2026

105 major incidents detected across AI services in April 2026.

MajorOngoing

Knowji

On 2026-04-20 at 05:06 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 20, 2026, 05:06 UTCDuration: ongoingView 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 →
MajorUnresolved — service still offline

SillyTavern

On 2026-04-19 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 19, 2026, 03:06 UTCStill offline after 33h 24mView service →
MajorUnresolved — service still offline

Moemate

On 2026-04-19 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Moemate. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 19, 2026, 03:06 UTCStill offline after 33h 24mView service →
MajorUnresolved — service still offline

Figgs AI

On 2026-04-19 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 19, 2026, 03:06 UTCStill offline after 33h 24mView service →
MajorUnresolved — service still offline

Robin AI

On 2026-04-19 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 19, 2026, 03:00 UTCStill offline after 33h 30mView service →
MajorUnresolved — service still offline

Trae

On 2026-04-18 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 18, 2026, 03:18 UTCStill offline after 57h 12mView service →
MajorUnresolved — service still offline

Visual Electric

On 2026-04-18 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Visual Electric. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 18, 2026, 03:18 UTCStill offline after 57h 12mView service →
MajorUnresolved — service still offline

Safurai

On 2026-04-18 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Safurai. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 18, 2026, 03:18 UTCStill offline after 57h 12mView service →
MajorUnresolved — service still offline

Play.ht

On 2026-04-17 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Play.ht. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 17, 2026, 03:18 UTCStill offline after 81h 13mView service →
MajorUnresolved — service still offline

Sizzle

On 2026-04-17 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 17, 2026, 03:12 UTCStill offline after 81h 19mView service →
MajorUnresolved — service still offline

Babbel

On 2026-04-17 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 17, 2026, 03:12 UTCStill offline after 81h 19mView 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

Moemate

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

Visual Electric

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

Safurai

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

Smartwriter

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

Started: Apr 15, 2026, 00:48 UTCResolved: Apr 15, 2026, 03:12 UTCDuration: 2h 24mView service →
MajorResolved

Smartwriter

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

Spellbook

On 2026-04-14 at 14:30 UTC, DownForAI monitoring detected a significant service issue affecting Spellbook. 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 14, 2026, 14:30 UTCResolved: Apr 14, 2026, 16:30 UTCDuration: 2hView service →
MajorResolved

Google Gemini

On 2026-04-14 at 13:00 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 14, 2026, 13:00 UTCResolved: Apr 14, 2026, 17:24 UTCDuration: 4h 24mView service →
MajorResolved

Play.ht

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

Babbel

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

Google Gemini

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

Started: Apr 13, 2026, 12:24 UTCResolved: Apr 13, 2026, 18:48 UTCDuration: 6h 24mView 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 →
← Back to all incidents