79 major incidents detected across AI services in May 2026.
On 2026-05-30 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 71h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-30 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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.
On 2026-05-29 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-27 at 08:45 UTC, DownForAI monitoring detected a significant service issue affecting OVHcloud AI. The incident has been resolved after approximately 9h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-27 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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.
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 probes running every 2-5 minutes from multiple locations.
On 2026-05-26 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-26 at 02:30 UTC, DownForAI monitoring detected a significant service issue affecting Deep Dream Generator. The incident has been resolved after approximately 3h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-25 at 07:00 UTC, DownForAI monitoring detected a significant service issue affecting CodeMate 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.
On 2026-05-24 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 71h 1m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-24 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 31m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-23 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 31m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-22 at 20:00 UTC, DownForAI monitoring detected a significant service issue affecting LM Studio. The incident has been resolved after approximately 28h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-21 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 31m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
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 probes running every 2-5 minutes from multiple locations.
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 probes running every 2-5 minutes from multiple locations.
On 2026-05-19 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. The incident has been resolved after approximately 26h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-19 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. The incident has been resolved after approximately 26h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-18 at 07:00 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 68h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-18 at 06:45 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 48h 15m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-18 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-18 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-17 at 18:15 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 4h 15m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
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.
On 2026-05-16 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. 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.
On 2026-05-16 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. 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.
On 2026-05-15 at 06:45 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 68h 15m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-15 at 06:30 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 68h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-15 at 05:45 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 69h 15m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-15 at 05:30 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 69h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.