DownForAI

Sizzle Incident History

9 major incidents detected for Sizzle. View live status dashboard →

MajorUnresolved — service still offline

Sizzle

On 2026-04-17 at 03:12 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.

Started: Apr 17, 2026, 03:12 UTCStill offline after 81h 19mView service →
MajorResolved

Sizzle

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.

Started: Apr 15, 2026, 03:00 UTCResolved: Apr 17, 2026, 03:00 UTCDuration: 48hView service →
MajorResolved

Sizzle

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.

Started: Apr 12, 2026, 03:00 UTCResolved: Apr 15, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Sizzle

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.

Started: Apr 9, 2026, 03:24 UTCResolved: Apr 12, 2026, 03:00 UTCDuration: 71h 36mView service →
MajorResolved

Sizzle

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.

Started: Apr 6, 2026, 03:09 UTCResolved: Apr 9, 2026, 03:00 UTCDuration: 71h 50mView service →
MajorResolved

Sizzle

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.

Started: Apr 3, 2026, 03:12 UTCResolved: Apr 6, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Sizzle

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.

Started: Apr 1, 2026, 03:00 UTCResolved: Apr 3, 2026, 03:00 UTCDuration: 48hView service →
MajorResolved

Sizzle

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.

Started: Mar 29, 2026, 03:07 UTCResolved: Apr 1, 2026, 03:00 UTCDuration: 71h 53mView service →
MajorResolved

Sizzle

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.

Started: Mar 26, 2026, 09:12 UTCResolved: Mar 29, 2026, 03:00 UTCDuration: 65h 48mView service →
← Back to all incidents