DownForAI

Holoworld Incident History

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

MajorResolved

Holoworld

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.

Started: May 17, 2026, 18:15 UTCResolved: May 17, 2026, 22:30 UTCDuration: 4h 15mView service →
MajorResolved

Holoworld

On 2026-05-06 at 22:24 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 30 minutes. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 6, 2026, 22:24 UTCResolved: May 6, 2026, 22:54 UTCDuration: 30mView service →
MajorResolved

Holoworld

On 2026-05-06 at 19:54 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. 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.

Started: May 6, 2026, 19:54 UTCResolved: May 6, 2026, 20:54 UTCDuration: 1hView service →
MajorResolved

Holoworld

On 2026-05-05 at 01:12 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 30 minutes. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 5, 2026, 01:12 UTCResolved: May 5, 2026, 01:42 UTCDuration: 30mView service →
MajorResolved

Holoworld

On 2026-05-04 at 20:12 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. 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.

Started: May 4, 2026, 20:12 UTCResolved: May 4, 2026, 21:12 UTCDuration: 1hView service →
MajorResolved

Holoworld

On 2026-04-28 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 44h 12m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 28, 2026, 03:06 UTCResolved: Apr 29, 2026, 23:18 UTCDuration: 44h 12mView service →
MajorResolved

Holoworld

On 2026-04-25 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. 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 25, 2026, 03:00 UTCResolved: Apr 28, 2026, 03:00 UTCDuration: 72hView service →
MajorResolved

Holoworld

On 2026-04-22 at 04:54 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 6m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 22, 2026, 04:54 UTCResolved: Apr 25, 2026, 03:00 UTCDuration: 70h 6mView service →
MajorResolved

Holoworld

On 2026-04-20 at 14:42 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 30 minutes. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 20, 2026, 14:42 UTCResolved: Apr 20, 2026, 15:12 UTCDuration: 30mView service →
← Back to all incidents