The root cause of the incident has been identified as one of our database migration services. We've since turned it off and are looking into how to prevent the latency from happening again.

We are continuing to monitor for any further issues.

We are currently investigating elevated latency across Retool APIs.