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-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.
On 2026-05-13 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting SillyTavern. The incident has been resolved after approximately 72h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-13 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Figgs AI. The incident has been resolved after approximately 72h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-12 at 06:15 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 68h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-12 at 06:00 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 69h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-12 at 05:15 UTC, DownForAI monitoring detected a significant service issue affecting Babbel. The incident has been resolved after approximately 69h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.