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.
On 2026-06-03 at 10:15 UTC, DownForAI monitoring detected a significant service issue affecting Outranking. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-06-03 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-06-02 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-06-01 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-06-01 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-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.