Retool outage history

We are investigating an issue with Source Control deployments being stalled in a "queued" state on Retool Cloud version 4.74.0

We've identified the issue and are working on remediation.

A fix is being deployed and we are monitoring.

The fix has been deployed and source control deployments should be working as expected -- we are monitoring.

This incident has been resolved.

Some customers may experience slower than normal query load times. We're actively investigating and will provide updates as we learn more.

Some users may see improved query latency, but we are continuing to investigate.

Some changes have been deployed, and we are monitoring the results

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.

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.

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.

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.

A fix has been implemented and we are monitoring the results.

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.

Query performance is back to normal and the incident is resolved.

Some customers may experience slower than normal query load times. We're actively investigating and will provide updates as we learn more.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're investigating an issue causing some users to experience errors when connecting to Retool's MCP server. Some connections may fail. We're working on a fix and will provide updates as we have them.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

A fix has been implemented for the issue causing intermittent "Session not found" connection failures on the Retool MCP server. We are currently monitoring the results to confirm full resolution. If you were running into this error, please retry to create a new session.

This incident has been resolved.

Some customers are seeing generic JDBC resource type queries fail with an error referencing LZ4 compression. Connection tests still pass, so the error appears only when running a query or loading a resource schema. We have identified the cause and are working on a fix.

This incident has been resolved.

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.

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

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.

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 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

Some users may have seen an error or a blank preview when opening or editing apps built with Retool's AI app builder. The issue has now been resolved.

An upstream incident with Github (https://www.githubstatus.com/incidents/zkxwbgr0cnmx) is causing issues with source control in Retool. Github has deployed a fix and we are monitoring.

Github has resolved their incident.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating reports of customers being unable to save or publish changes in React apps, with an error about system dependencies. We will share an update as soon as we know more.

A fix has been implemented, and we are monitoring the results

This incident has been resolved.

We are investigating an issue with Retool Workflows being stuck in a pending state. There is also an uptick in 429 rate limit responses for start triggers

We've identified the issue and are working on a fix.

The fix has been deployed, and we're monitoring the results. Workflows are still degraded but recovering.

We are continuing to monitor for any further issues.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The fix was verified and the breakage is now resolved.

We are investigating the disabling of retool-email.com domain due to spam. Note that this does not impact official retool emails like user invites and password resets.

Some Retool Emails failed with a "Disabled for sending spam" error due to an issue with our upstream email provider. The sending domain has since been restored, and email delivery is operating normally. We've also added safeguards to prevent recurrence. We apologize for the disruption.

We're investigating an issue affecting Apps built in the new AI app builder. Affected users may see an empty Data tab ("This app does not contain any functions") and be unable to publish, with an error that backend functions are unapproved or "not visible in the Data tab."

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're investigating an issue where some Retool Cloud Workflows are intermittently failing with timeout errors.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating an issue where queries are experiencing higher latency.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We've identified the issue and are preparing a fix

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating reports that Retool Mobile apps fail to load when opened in a web browser (the in-browser "View"/user-mode preview and the editor preview button). Editing mobile apps and running them in the native iOS/Android Retool Mobile apps are unaffected.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're investigating reports of customers experiencing sign-in issues on the Retool Mobile app for iOS and Android. Affected users may be returned to the sign-in screen after authenticating, or be unable to complete sign-in.

The issue has been identified as a change made to how mobile sessions are validated. We have rolled back that change and are working on a permanent fix. As we work on shipping that fix, please try the following: - Android: Clear the app cache. Open your Settings, go to Apps (or Applications), tap Retool Mobile, select Storage, and tap Clear cache. - iOS: Delete and reinstall the Retool Mobile app (you'll be prompted to sign in again afterward).

The issue has been identified as a change made to how mobile sessions are validated. We have rolled back that change and are monitoring the results If you are unable to log into Retool Mobile, you will have to do the following: - Android: Clear the app cache. Open your Settings, go to Apps (or Applications), tap Retool Mobile, select Storage, and tap Clear cache. - iOS: Delete and reinstall the Retool Mobile app (you'll be prompted to sign in again afterward).

This incident is resolved. If you are having issues signing in, please first try the following: - Android: Clear the app cache. Open your Settings, go to Apps (or Applications), tap Retool Mobile, select Storage, and tap Clear cache. - iOS: Delete and reinstall the Retool Mobile app (you'll be prompted to sign in again afterward). Or reach out to [email protected]