Outage on Golive

Critical · Started Mar 10, 2026 · 8:04 PM

Duration

1h 22m
Severity

Critical
Detection lead

—
User reports

—

Summary

Outage on Golive

We have identified and resolved the root cause of the issue. One of our nodes was unable to perform DNS resolution due to routing errors. The routing issues have now been fixed, and DNS resolution is working correctly. We apologize for the inconvenience caused.

Started

Mar 10, 2026 · 8:04 PM
Resolved

Mar 10, 2026 · 9:27 PM
Duration

1h 22m
Severity

Critical

Event timeline

How this incident unfolded

◐

Investigating
Mar 10 · 8:04 PM Apwide

We are currently investigating the issue.
◐

Investigating
Mar 10 · 8:32 PM Apwide

We identified a DNS resolution issue on one of our production nodes. The Golive service has been moved to another node and is now available again. We are currently working with our cloud provider to determine the root cause of the issue and implement a fix.
✓

Resolved
Mar 10 · 9:27 PM Apwide

We have identified and resolved the root cause of the issue. One of our nodes was unable to perform DNS resolution due to routing errors. The routing issues have now been fixed, and DNS resolution is working correctly. We apologize for the inconvenience caused.