On May 22, 2026, between 18:24 and 20:06 UTC, customers in the following regions were unable to load or view apps and pages:
Root cause
During a routine update, a transient connectivity issue occurred as the update was being distributed across back-end components. This caused one component to lose sync and isolate itself to protect data integrity. Under normal circumstances, requests would automatically redirect to a healthy component. A gap in our health monitoring configuration meant this isolated state wasn't recognized as requiring a redirect. This meant requests continued routing to the isolated component rather than being redirected to a healthy component. This temporarily prevented apps and pages from loading.
Recovery
Our engineering team identified the issue and took immediate action to restore access. We restarted the affected component and redirected all traffic to healthy components. This quickly began restoring app and page access. We then completed a full data sync to confirm our environment was fully consistent and healthy. By 20:06 UTC, the issue was fully resolved for all customers.
Corrective and preventative actions
We're implementing the following improvements to prevent similar disruptions:
We're auditing and stress testing our traffic redirect mechanisms to confirm they trigger automatically during component isolation events. This ensures customers can access their apps and pages even when connectivity issues occur between components.
We're enhancing our alerting to reduce the time between detecting a connection failure and our engineering team responding. This means we can identify and address similar issues earlier, before they affect customers.
We're updating our deployment procedures to include additional connectivity checks during platform updates. This ensures our engineering team catches potential connection issues during deployment before they affect customers.
Closing
We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact our Support team.