DownForAI

Holoworld Incident History

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

Major• Unresolved — service still offline

Holoworld

On 2026-11-06 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident is currently being investigated. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Nov 6, 2026, 05:00 UTCStill offline after 62h 42mView service →
Major• Resolved

Holoworld

On 2026-11-04 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Nov 4, 2026, 03:00 UTCResolved: Nov 6, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-11-01 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Nov 1, 2026, 05:00 UTCResolved: Nov 4, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-10-30 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 30, 2026, 03:00 UTCResolved: Nov 1, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-10-27 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 27, 2026, 05:00 UTCResolved: Oct 30, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-10-25 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 25, 2026, 03:00 UTCResolved: Oct 27, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-10-22 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 22, 2026, 05:00 UTCResolved: Oct 25, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-10-20 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 20, 2026, 03:00 UTCResolved: Oct 22, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-10-17 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 17, 2026, 05:00 UTCResolved: Oct 20, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-10-15 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 15, 2026, 03:00 UTCResolved: Oct 17, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-10-12 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 12, 2026, 05:00 UTCResolved: Oct 15, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-10-10 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 10, 2026, 03:00 UTCResolved: Oct 12, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-10-07 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 7, 2026, 05:00 UTCResolved: Oct 10, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-10-05 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 5, 2026, 03:00 UTCResolved: Oct 7, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-10-02 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Oct 2, 2026, 05:00 UTCResolved: Oct 5, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-09-30 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Sep 30, 2026, 03:00 UTCResolved: Oct 2, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-09-27 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Sep 27, 2026, 05:00 UTCResolved: Sep 30, 2026, 03:00 UTCDuration: 70hView service →
Major• Resolved

Holoworld

On 2026-09-25 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Sep 25, 2026, 03:00 UTCResolved: Sep 27, 2026, 03:00 UTCDuration: 48hView service →
Major• Resolved

Holoworld

On 2026-09-22 at 20:00 UTC, DownForAI monitoring detected a significant service issue affecting Holoworld. The incident has been resolved after approximately 55h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Sep 22, 2026, 20:00 UTCResolved: Sep 25, 2026, 03:00 UTCDuration: 55hView service →
← Back to all incidents