DownForAI

AI Incidents — March 2026

57 major incidents detected across AI services in March 2026.

MajorResolved

Safurai

On 2026-03-26 at 08:36 UTC, DownForAI monitoring detected a significant service issue affecting Safurai. 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

Robin AI

On 2026-03-26 at 08:36 UTC, DownForAI monitoring detected a significant service issue affecting Robin 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

Visual Electric

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

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

Builder.ai

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

Started: Mar 26, 2026, 07:27 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 67h 33mView service →
MajorResolved

CSM.ai

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

Started: Mar 26, 2026, 07:27 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 67h 33mView service →
MajorResolved

Camel AI

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

Started: Mar 25, 2026, 14:24 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 17h 2mView service →
MajorResolved

Google Gemini

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

Started: Mar 25, 2026, 14:12 UTCResolved: Mar 25, 2026, 15:18 UTCDuration: 1h 6mView service →
MajorResolved

Camel AI

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

Started: Mar 25, 2026, 13:39 UTCResolved: Mar 25, 2026, 14:06 UTCDuration: 27mView service →
MajorResolved

Google Gemini

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

Started: Mar 25, 2026, 11:24 UTCResolved: Mar 25, 2026, 11:42 UTCDuration: 18mView service →
MajorResolved

Google Gemini

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

Camel AI

On 2026-03-24 at 12:27 UTC, DownForAI monitoring detected a significant service issue affecting Camel AI. The incident has been resolved after approximately 54 minutes. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 24, 2026, 12:27 UTCResolved: Mar 24, 2026, 13:21 UTCDuration: 54mView service →
MajorResolved

Milvus

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

Started: Mar 24, 2026, 03:06 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 52h 20mView service →
MajorResolved

Stable Audio

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

Started: Mar 24, 2026, 03:06 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 52h 20mView service →
MajorResolved

Censius

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

Started: Mar 24, 2026, 03:06 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 52h 20mView service →
MajorResolved

CSM.ai

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

Started: Mar 24, 2026, 03:03 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 52h 23mView service →
MajorResolved

Builder.ai

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

Started: Mar 24, 2026, 03:03 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 52h 23mView service →
MajorResolved

DeepSeek Coder

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

Started: Mar 24, 2026, 03:03 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 52h 23mView service →
MajorResolved

OctoAI

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

Started: Mar 24, 2026, 03:00 UTCResolved: Mar 26, 2026, 07:26 UTCDuration: 52h 26mView service →
MajorResolved

Paradot

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

Started: Mar 23, 2026, 18:03 UTCResolved: Mar 25, 2026, 08:27 UTCDuration: 38h 24mView service →
MajorResolved

Anima AI

On 2026-03-22 at 17:27 UTC, DownForAI monitoring detected a significant service issue affecting Anima AI. The incident has been resolved after approximately 18 minutes. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 22, 2026, 17:27 UTCResolved: Mar 22, 2026, 17:45 UTCDuration: 18mView service →
MajorResolved

CSM.ai

On 2026-03-21 at 20:35 UTC, DownForAI monitoring detected a significant service issue affecting CSM.ai. The incident has been resolved after approximately 54h 25m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 21, 2026, 20:35 UTCResolved: Mar 24, 2026, 03:00 UTCDuration: 54h 25mView service →
MajorResolved

Builder.ai

On 2026-03-21 at 20:35 UTC, DownForAI monitoring detected a significant service issue affecting Builder.ai. The incident has been resolved after approximately 54h 25m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 21, 2026, 20:35 UTCResolved: Mar 24, 2026, 03:00 UTCDuration: 54h 25mView service →
MajorResolved

OctoAI

On 2026-03-21 at 20:25 UTC, DownForAI monitoring detected a significant service issue affecting OctoAI. The incident has been resolved after approximately 54h 35m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 21, 2026, 20:25 UTCResolved: Mar 24, 2026, 03:00 UTCDuration: 54h 35mView service →
MajorResolved

Milvus

On 2026-03-21 at 20:15 UTC, DownForAI monitoring detected a significant service issue affecting Milvus. The incident has been resolved after approximately 54h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 21, 2026, 20:15 UTCResolved: Mar 24, 2026, 03:00 UTCDuration: 54h 45mView service →
MajorResolved

Censius

On 2026-03-21 at 20:10 UTC, DownForAI monitoring detected a significant service issue affecting Censius. The incident has been resolved after approximately 54h 50m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Mar 21, 2026, 20:10 UTCResolved: Mar 24, 2026, 03:00 UTCDuration: 54h 50mView service →
MajorResolved

Stable Audio

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

Started: Mar 21, 2026, 20:05 UTCResolved: Mar 24, 2026, 03:00 UTCDuration: 54h 55mView service →
MajorResolved

DeepSeek Coder

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

Started: Mar 21, 2026, 19:55 UTCResolved: Mar 24, 2026, 03:00 UTCDuration: 55h 5mView service →
← Back to all incidents