DownForAI

AI Incidents Archive

Public archive of significant incidents detected across 800+ AI services. Automated probes run every 2–5 minutes from multiple locations. Updated hourly. See our methodology.

252
Total incidents
248
Resolved
4
Currently open
64
Services affected
45h 41m
Avg duration

Browse by month

June 2026
5 incidents
Top: Robin AI, Babbel, Outranking
May 2026
79 incidents
Top: Robin AI, Sizzle, Babbel
April 2026
122 incidents
Top: Sizzle, Trae, Babbel
March 2026
45 incidents
Top: Google Gemini, Builder.ai, Camel AI
February 2026
1 incident
Top: OpenAI

Latest incidents (252 total)

MajorResolved

Sizzle

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

Started: May 6, 2026, 04:00 UTCResolved: May 9, 2026, 03:00 UTCDuration: 71hView service →
MajorResolved

Trae

On 2026-05-06 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: May 6, 2026, 03:12 UTCResolved: May 9, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Babbel

On 2026-05-06 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: May 6, 2026, 03:12 UTCResolved: May 9, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

NannyML

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

Started: May 6, 2026, 03:06 UTCResolved: May 8, 2026, 16:24 UTCDuration: 61h 18mView service →
MajorResolved

OpenAI Sora

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

Started: May 5, 2026, 06:42 UTCResolved: May 8, 2026, 03:00 UTCDuration: 68h 18mView service →
MajorResolved

Knowji

On 2026-05-05 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: May 5, 2026, 03:12 UTCResolved: May 8, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Holoworld

On 2026-05-05 at 01:12 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. 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: May 5, 2026, 01:12 UTCResolved: May 5, 2026, 01:42 UTCDuration: 30mView service →
MajorResolved

Creatie

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

Started: May 5, 2026, 00:18 UTCResolved: May 5, 2026, 20:00 UTCDuration: 19h 42mView service →
MajorResolved

Holoworld

On 2026-05-04 at 20:12 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. 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: May 4, 2026, 20:12 UTCResolved: May 4, 2026, 21:12 UTCDuration: 1hView service →
MajorResolved

PearAI

On 2026-05-04 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting PearAI. 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: May 4, 2026, 03:18 UTCResolved: May 4, 2026, 03:48 UTCDuration: 30mView service →
MajorResolved

Figgs AI

On 2026-05-04 at 03:12 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: May 4, 2026, 03:12 UTCResolved: May 7, 2026, 03:00 UTCDuration: 71h 47mView service →
MajorResolved

SillyTavern

On 2026-05-04 at 03:12 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: May 4, 2026, 03:12 UTCResolved: May 7, 2026, 03:00 UTCDuration: 71h 47mView service →
MajorResolved

Robin AI

On 2026-05-04 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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: May 4, 2026, 03:06 UTCResolved: May 7, 2026, 03:00 UTCDuration: 71h 53mView service →
MajorResolved

NannyML

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

Started: May 3, 2026, 03:18 UTCResolved: May 6, 2026, 03:00 UTCDuration: 71h 41mView service →
MajorResolved

Sizzle

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

Trae

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

Babbel

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

Creatie

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

Started: May 2, 2026, 04:36 UTCResolved: May 4, 2026, 01:24 UTCDuration: 44h 48mView service →
MajorResolved

Knowji

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

Started: May 2, 2026, 03:18 UTCResolved: May 5, 2026, 03:00 UTCDuration: 71h 41mView service →
MajorResolved

Krea AI

On 2026-05-01 at 15:30 UTC, DownForAI monitoring detected a significant service issue affecting Krea 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: May 1, 2026, 15:30 UTCResolved: May 1, 2026, 15:54 UTCDuration: 24mView service →