New Cloud signups are temporarily paused
Retool paused new Cloud signups. The provider reports the issue as identified. Retool stopped new Cloud account creation while it investigates suspected abuse. Retool expects to remove this restriction early next week.
State
Identified
Started
Ongoing for
5 h 52 min
Worst impact
Degraded
Timeline
1 updateIdentified
5 h 52 min 100%
Updates
Times in UTCAs posted by Retool
We are temporarily preventing the creation of new Cloud accounts while we investigate suspected abuse. We expect to lift this restriction early next week.
Retool in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
20
Median duration
3 h 35 min
This incident
1.6× the median
Other Retool incidents
All incidentsRetool·Retool Database unavailable for some Retool Cloud organizations
Retool Database is unavailable for a very small subset of Retool Cloud organizations on legacy database infrastructure. Apps and workflows in those organizations return errors when they query Retool Database. Retool has identified the issue.
Retool·Some antivirus products are blocking retool.app
Some antivirus products blocked retool.app and stopped the New app builder from loading. Retool services operated normally. Norton, AVG and Avast users saw warnings clear. The incident is resolved and lasted about 72 hours.
Retool·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.
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