DownForAI

AI Incidents Archive

Public archive of significant incidents detected across 800+ AI services. DownForAI checks monitored surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. Updated hourly. See our methodology.

71
Total incidents
68
Resolved
3
Currently open
34
Services affected
32h 21m
Avg duration

Browse by month

July 2026
24 incidents
Top: Elastic AI Search, BlinqIO, Render AI
June 2026
25 incidents
Top: Outranking, Elastic AI Search, Snowflake Cortex
May 2026
5 incidents
Top: Babbel, Civitai, Sizzle
April 2026
10 incidents
Top: Google Gemini, OpenAI, HuggingChat
March 2026
6 incidents
Top: Stable Audio, Civitai, Descript
February 2026
1 incident
Top: OpenAI

Latest incidents (71 total)

MajorResolved

Linear

On 2026-06-22 at 16:45 UTC, DownForAI monitoring detected a significant service issue affecting Linear. The incident has been resolved after approximately 2h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 22, 2026, 16:45 UTCResolved: Jun 22, 2026, 18:45 UTCDuration: 2hView service →
MajorResolved

Civitai

On 2026-06-22 at 16:30 UTC, DownForAI monitoring detected a significant service issue affecting Civitai. The incident has been resolved after approximately 30 minutes. This incident was identified based on a significant volume of user reports.

Started: Jun 22, 2026, 16:30 UTCResolved: Jun 22, 2026, 17:00 UTCDuration: 30mView service →
MajorResolved

Elastic AI Search

On 2026-06-20 at 08:45 UTC, DownForAI monitoring detected a significant service issue affecting Elastic AI Search. The incident has been resolved after approximately 66h 15m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 20, 2026, 08:45 UTCResolved: Jun 23, 2026, 03:00 UTCDuration: 66h 15mView service →
MajorResolved

Civitai

On 2026-06-19 at 13:01 UTC, DownForAI monitoring detected a significant service issue affecting Civitai. The incident has been resolved after approximately 29 minutes. This incident was identified based on a significant volume of user reports.

Started: Jun 19, 2026, 13:01 UTCResolved: Jun 19, 2026, 13:30 UTCDuration: 29mView service →
MajorResolved

Outranking

On 2026-06-15 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Outranking. The incident has been resolved after approximately 71h 30m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 15, 2026, 03:30 UTCResolved: Jun 18, 2026, 03:00 UTCDuration: 71h 30mView service →
MajorResolved

Outranking

On 2026-06-12 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting Outranking. The incident has been resolved after approximately 71h 46m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 12, 2026, 03:15 UTCResolved: Jun 15, 2026, 03:00 UTCDuration: 71h 46mView service →
MajorResolved

Outranking

On 2026-06-09 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting Outranking. The incident has been resolved after approximately 71h 46m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 9, 2026, 03:15 UTCResolved: Jun 12, 2026, 03:00 UTCDuration: 71h 46mView service →
MajorResolved

Outranking

On 2026-06-06 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting Outranking. The incident has been resolved after approximately 71h 16m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 6, 2026, 03:45 UTCResolved: Jun 9, 2026, 03:00 UTCDuration: 71h 16mView service →
MajorResolved

Outranking

On 2026-06-03 at 10:15 UTC, DownForAI monitoring detected a significant service issue affecting Outranking. The incident has been resolved after approximately 64h 46m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 3, 2026, 10:15 UTCResolved: Jun 6, 2026, 03:00 UTCDuration: 64h 46mView service →
MajorResolved

Babbel

On 2026-05-27 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 71h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: May 27, 2026, 04:00 UTCResolved: May 30, 2026, 03:00 UTCDuration: 71hView service →
MajorResolved

Babbel

On 2026-05-21 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 71h 46m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: May 21, 2026, 03:15 UTCResolved: May 24, 2026, 03:00 UTCDuration: 71h 46mView service →
MajorResolved

Sizzle

On 2026-05-21 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 48h 1m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: May 21, 2026, 03:00 UTCResolved: May 23, 2026, 03:00 UTCDuration: 48h 1mView service →
MajorResolved

Civitai

On 2026-05-17 at 15:00 UTC, DownForAI monitoring detected a significant service issue affecting Civitai. The incident has been resolved after approximately 30 minutes. This incident was identified based on a significant volume of user reports.

Started: May 17, 2026, 15:00 UTCResolved: May 17, 2026, 15:30 UTCDuration: 30mView 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 probe infrastructure, which checks each monitored surface on a rotating schedule.

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

OpenAI

On 2026-04-20 at 15:00 UTC, DownForAI monitoring detected a significant service issue affecting OpenAI. The incident has been resolved after approximately 18 minutes. This incident was identified based on a significant volume of user reports.

Started: Apr 20, 2026, 15:00 UTCResolved: Apr 20, 2026, 15:18 UTCDuration: 18mView service →
MajorResolved

OpenAI

On 2026-04-20 at 14:40 UTC, DownForAI monitoring detected a significant service issue affecting OpenAI. The incident has been resolved after approximately 14 minutes. This incident was identified based on a significant volume of user reports.

Started: Apr 20, 2026, 14:40 UTCResolved: Apr 20, 2026, 14:54 UTCDuration: 14mView 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 probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Apr 19, 2026, 23:24 UTCResolved: Apr 19, 2026, 23:48 UTCDuration: 24mView 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 probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Apr 19, 2026, 23:24 UTCResolved: Apr 19, 2026, 23:54 UTCDuration: 30mView 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 probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Apr 14, 2026, 13:00 UTCResolved: Apr 14, 2026, 17:24 UTCDuration: 4h 24mView 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 probe infrastructure, which checks each monitored surface on a rotating schedule.

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