On July 1, 2026, at approximately 23:52 UTC, our monitoring systems detected a service disruption impacting customers in the me1: Cloud – Middle East and eu5: Cloud — Europe regions. During this time, affected customers were unable to log in to the platform. Service was restored at 03:21 UTC
Root cause
The disruption originated from a planned network configuration change to our internal name resolution infrastructure. A misconfiguration was introduced as part of the change that left an underlying routing conflict in place. This caused return traffic for internal name lookups to take an incorrect path during routine network activity. As a result, internal name resolution began failing for the two affected regions. This prevented the authentication flow from completing and stopped customers from logging in.
Recovery
On detection at 23:52 UTC, our engineering team and our infrastructure partner began investigating in parallel. Because internal name resolution issues can present themselves in several diverse ways, the team worked through multiple lines of inquiry before isolating the specific routing conflict responsible. Once identified, we rolled back the recent change to restore the previous known-good routing configuration. Connectivity recovered progressively as the rollback propagated, and by 03:21 UTC, authentication was fully restored for both affected regions.
Corrective and preventative actions
We are implementing the following actions to prevent a recurrence:
Closing
We apologize for the impact this disruption has had on your operations. The corrective actions above are focused on preventing a recurrence of any similar issue in the future. If you have questions or concerns, please contact Support.