Elevated Latency on Query Execution (Retool Cloud)
Query performance is back to normal and the incident is resolved.
The latest update from Retool.
State
Resolved
Started
Lasted
7 days
Worst impact
Degraded
Timeline
11 updatesInvestigating
43 h 4 min 25%
Monitoring
5 days 75%
Updates
Times in UTCAs posted by Retool
Query performance is back to normal and the incident is resolved.
We have not seen the same query latency issues since the fix was applied. We’re continuing to monitor closely and will share another update if anything changes.
A fix has been implemented and we are monitoring the results.
Additional changes have been deployed as part of a more permanent fix, alongside the temporary fix already in place. We'll monitor through tomorrow morning's peak traffic to confirm their impact and will share another update then.
This morning we again saw high query latency. We were able to mitigate it temporarily, and our investigation into the root cause is ongoing. We'll share another update as we learn more.
A fix has been implemented and we are monitoring the results.
The temporary mitigation we applied earlier is still in place, and some users have reported significantly improved query latency. We're still investigating the root cause and will share another update as we learn more.
We are seeing intermittent spikes in query latency, as we saw earlier. A temporary mitigation is in place, and we're continuing to investigate the root cause. We'll share an update as soon as we have more information.
Some changes have been deployed, and we are monitoring the results
Some users may see improved query latency, but we are continuing to investigate.
Some customers may experience slower than normal query load times. We're actively investigating and will provide updates as we learn more.
Affected components
1Retool in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
17
Median duration
3 h 26 min
This incident
51× the median
Other Retool incidents
All incidentsRetool·Source Control Deployments Stalled
This incident has been resolved.
Retool·Elevated Latency on Query Execution (Retool Cloud)
This incident has been resolved.
Retool·Retool MCP connection errors
This incident has been resolved.
Retool·Retool MCP connection failures
This incident has been resolved.
Retool·Errors running generic JDBC resource type queries
This incident has been resolved.
Follow Retool
Your coding agent knows when Retool is down, and tells you when a failure is theirs, not yours. You can also get Retool incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "retool" and tell me if Retool has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=retool/feed subscribe https://outages.live/feed.xml?providers=retoolFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane