25 major incidents detected for Sizzle. View live status dashboard →
On 2026-06-04 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: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-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-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-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-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-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-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-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-09 at 03:42 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 18m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-06 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. 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-03 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-30 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-27 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-24 at 03:36 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 24m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-21 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-17 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 95h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-15 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. 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-04-12 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. 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-04-09 at 03:24 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 36m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-06 at 03:09 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 50m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-03 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-01 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. 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-03-29 at 03:07 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 71h 53m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-03-26 at 09:12 UTC, DownForAI monitoring detected a significant service issue affecting Sizzle. The incident has been resolved after approximately 65h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.