React App Builder Sandbox Installs May Fail to Install Dependencies
This incident is resolved. Images with the fix are out: 4.0.12-stable 4.43.0-edge Our minimum release age for React app builder dependencies is 5 days, so this incident will self-resolve for any self-hosted deployments that don't upgrade on August 24th, by 7am PST. All currently affected self-hosted versions: stable: 4.0.0 - 4.0.11 edge: 4.1, 4.9, 4.16, 4.19, 4.23, 4.27, 4.31, 4.35, 4.40
The latest update from Retool.
State
Resolved
Started
Lasted
5 h 54 min
Worst impact
Partial outage
Timeline
5 updatesInvestigating
4 min 1%
Identified
3 h 38 min 62%
Monitoring
2 h 12 min 37%
Updates
Times in UTCAs posted by Retool
This incident is resolved. Images with the fix are out: 4.0.12-stable 4.43.0-edge Our minimum release age for React app builder dependencies is 5 days, so this incident will self-resolve for any self-hosted deployments that don't upgrade on August 24th, by 7am PST. All currently affected self-hosted versions: stable: 4.0.0 - 4.0.11 edge: 4.1, 4.9, 4.16, 4.19, 4.23, 4.27, 4.31, 4.35, 4.40
Images with the fix are out: 4.0.12-stable 4.43.0-edge Our minimum release age for React app builder dependencies is 5 days, so this incident will self-resolve for any self-hosted deployments that don't upgrade on August 24th, by 7am PST. All currently affected self-hosted versions: stable: 4.0.0 - 4.0.11 edge: 4.1, 4.9, 4.16, 4.19, 4.23, 4.27, 4.31, 4.35, 4.40
This issue affects Retool version 4.0.0+ (stable and edge), specifically for 1) newly-created React apps, 2) new publishes of existing React apps, and 3) cold starts of sandboxes when editing existing React apps. Existing published apps that do not get published after August 19th are unaffected. Self-hosted customers can update to 4.43.0-edge to get an immediate fix. A patch to our stable release channel is coming soon.
This issue no longer affects the React App Builder on Retool Cloud. We have identified the issue for self-hosted, and are working on releasing images with a fix
Retool's app builder may fail to install and connect to a sandbox due to downstream dependency issues. This affects both Cloud and Self-Hosted Retool instances.
Affected components
2Retool in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
17
Median duration
3 h 26 min
This incident
1.7× the median
Other Retool incidents
All incidentsRetool·Source Control Deployments Stalled
This incident has been resolved.
Retool·Elevated Latency on Query Execution (Retool Cloud)
Query performance is back to normal and the incident is 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.
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