Between 12:37 UTC and 12:50 UTC, an overload in the connection proxying system resulted in instability for a subset of databases.
The root cause was identified as a misconfiguration in the routing rules, which caused certain requests to experience timeouts during the initial phase of a gradual deployment. Upon detection, the deployment was immediately rolled back, restoring normal service.
We are reviewing our deployment and configuration validation processes to prevent similar issues in the future.