StarRez experienced a major incident on June 26, 2026 affecting Central US, lasting 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 26, 2026, 05:53 AM UTC
Customers in the Central US region are currently having a service disruption -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team
- identified Jun 26, 2026, 06:01 AM UTC
The issue has been identified and engineers are remediating to bring sites back online. -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team
- monitoring Jun 26, 2026, 06:10 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 26, 2026, 06:10 AM UTC
We are continuing to monitor for any further issues.
- resolved Jun 26, 2026, 06:13 AM UTC
This incident has been resolved.
- postmortem Jun 30, 2026, 01:51 AM UTC
**Overview** On 26 June 2026, StarRez experienced a service disruption affecting StarRez Cloud customers in the Central US region. StarRez Cloud applications were unavailable for affected customers beginning at approximately 05:47 UTC. All affected customer sites were restored to full operation by 06:06 UTC on 26 June 2026. **Root Cause** The disruption was caused by a configuration change applied to infrastructure supporting StarRez Cloud in the Central US region. The change caused affected customer environments to become temporarily unavailable while the infrastructure stabilized. **Resolution** StarRez engineers identified the issue promptly and took immediate action to restore the affected infrastructure to a healthy state. All customer sites in the Central US region were confirmed fully operational by 06:06 UTC, approximately 19 minutes after the disruption began. **Next Steps** StarRez is implementing further guardrails around configuration to cloud resources to prevent recurrence of this class of issue in the future.