DownForAI

AI Incidents — March 2026

57 major incidents detected across AI services in March 2026.

MajorResolved

Play.ht

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

Started: Mar 31, 2026, 19:24 UTCResolved: Apr 3, 2026, 03:00 UTCDuration: 55h 36mView service →
MajorResolved

Masterpiece Studio

On 2026-03-31 at 15:39 UTC, DownForAI monitoring detected a significant service issue affecting Masterpiece Studio. The incident has been resolved after approximately 51h 9m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 31, 2026, 15:39 UTCResolved: Apr 2, 2026, 18:48 UTCDuration: 51h 9mView service →
MajorResolved

Google Gemini

On 2026-03-31 at 14:33 UTC, DownForAI monitoring detected a significant service issue affecting Google Gemini. 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: Mar 31, 2026, 14:33 UTCResolved: Mar 31, 2026, 15:33 UTCDuration: 1hView service →
MajorResolved

MongoDB Atlas Vector

On 2026-03-31 at 07:33 UTC, DownForAI monitoring detected a significant service issue affecting MongoDB Atlas Vector. 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: Mar 31, 2026, 07:33 UTCResolved: Mar 31, 2026, 07:45 UTCDuration: 12mView service →
MajorResolved

Nous Hermes

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

Started: Mar 30, 2026, 19:27 UTCResolved: Mar 30, 2026, 22:27 UTCDuration: 3hView service →
MajorResolved

Google Gemini

On 2026-03-30 at 12:52 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: Mar 30, 2026, 12:52 UTCResolved: Mar 30, 2026, 15:28 UTCDuration: 2h 36mView service →
MajorResolved

Nous Hermes

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

Started: Mar 30, 2026, 12:43 UTCResolved: Mar 30, 2026, 17:27 UTCDuration: 4h 44mView service →
MajorResolved

Descript

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

Descript Video

On 2026-03-30 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting Descript Video. 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: Mar 30, 2026, 04:00 UTCResolved: Mar 30, 2026, 07:13 UTCDuration: 3h 12mView service →
MajorResolved

Google Gemini

On 2026-03-29 at 14:01 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: Mar 29, 2026, 14:01 UTCResolved: Mar 29, 2026, 14:13 UTCDuration: 12mView service →
MajorResolved

Figgs AI

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

Started: Mar 29, 2026, 03:13 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 47mView service →
MajorResolved

SillyTavern

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

Started: Mar 29, 2026, 03:13 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 47mView service →
MajorResolved

Moemate

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

Started: Mar 29, 2026, 03:13 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 47mView service →
MajorResolved

Robin AI

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

Writesmith

On 2026-03-29 at 03:10 UTC, DownForAI monitoring detected a significant service issue affecting Writesmith. 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: Mar 29, 2026, 03:10 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 50mView service →
MajorResolved

Sizzle

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

Started: Mar 29, 2026, 03:07 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 53mView service →
MajorResolved

Babbel

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

Started: Mar 29, 2026, 03:07 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 53mView service →
MajorResolved

Visual Electric

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

Started: Mar 29, 2026, 03:04 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 56mView service →
MajorResolved

Safurai

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

Started: Mar 29, 2026, 03:04 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 56mView service →
MajorResolved

Trae

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

Started: Mar 29, 2026, 03:04 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 56mView service →
MajorResolved

Wave.video AI

On 2026-03-28 at 19:21 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: Mar 28, 2026, 19:21 UTCResolved: Mar 28, 2026, 19:46 UTCDuration: 24mView service →
MajorResolved

Civitai

On 2026-03-27 at 17:21 UTC, DownForAI monitoring detected a significant service issue affecting Civitai. 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: Mar 27, 2026, 17:21 UTCResolved: Mar 27, 2026, 17:33 UTCDuration: 12mView service →
MajorResolved

Context.ai

On 2026-03-27 at 12:48 UTC, DownForAI monitoring detected a significant service issue affecting Context.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: Mar 27, 2026, 12:48 UTCResolved: Mar 27, 2026, 13:48 UTCDuration: 1hView service →
MajorResolved

Sizzle

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

Started: Mar 26, 2026, 09:12 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 65h 48mView service →
MajorResolved

Babbel

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

Started: Mar 26, 2026, 08:36 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 66h 24mView service →
MajorResolved

Figgs AI

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

Started: Mar 26, 2026, 08:36 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 66h 24mView service →
MajorResolved

Writesmith

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

Started: Mar 26, 2026, 08:36 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 66h 24mView service →
MajorResolved

SillyTavern

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

Started: Mar 26, 2026, 08:36 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 66h 24mView service →
MajorResolved

Moemate

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

Started: Mar 26, 2026, 08:36 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 66h 24mView service →
MajorResolved

Trae

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

Started: Mar 26, 2026, 08:36 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 66h 24mView service →
← Back to all incidents