Retool had 43 outages in the last 2 years totaling 503h 26m of downtime — averaging 1.8 incidents per month.
There were 43 Retool outages since May 31, 2024 totaling 503h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating an issue with our MotherDuck integration for Cloud orgs
MotherDuck is fully operational again. We identified and fixed a caching issue that required us to temporarily disable the integration. Access has been restored as of May 11, 2026. We apologize for the disruption.
We are currently investigating issues with the Motherduck resource and are disabling it as the investigation is ongoing.
MotherDuck is fully operational again. We identified and fixed a caching issue that required us to temporarily disable the integration. Access has been restored as of May 8, 2026. We apologize for the disruption.
We are investigating an issue where workflows using custom npm libraries are failing to execute. This affects both Retool Cloud and self-hosted customers. A fix has been identified and is currently being deployed to Cloud. Self-hosted patch releases are in progress.
A fix has been deployed to Retool Cloud. Self-hosted customers should upgrade to 3.300.28-stable or 3.334.12-stable, which has the fix. We are monitoring to confirm full resolution.
This incident has been resolved. Self-hosted customers should update to 3.300.28-stable or 3.334.12-stable for the fix.
We are reopening an investigation into an issue where Google Sheets resources are intermittently failing with a "premature close" error. This is affecting a subset of users on Retool Cloud. Our team is actively investigating the root cause and working on a mitigation.
We are still investigating this issue.
We've identified the issue and a fix is being prepared
We've deployed a fix and are monitoring the results.
We are still investigating this issue.
We've deployed another attempted fix and are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue causing PostgreSQL and REST API queries to fail. This also affects users' ability to use RetoolDB.
We have identified the potential root cause of this issue and are implementing a fix
A fix has been implemented and we are monitoring the results.
Following the fix we are seeing error rates of the affected services return to normal. With that in mind, we are considering this issue resolved.
We are looking into an issue that is preventing Cloud customers with Custom Domains from completing the OAuth2 Resource Authentication flow. Affected customers can work around this behavior by authenticating said resources via their base (.retool.com) domain.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Unfortunately this issue has not been fully resolved as previously indicated, and we are continuing to work on a fix. We apologise for the continued disruption.
This incident has been resolved.
We're aware that some users are encountering unexpected rate‑limiting when using AI-powered features. We are actively investigating the root cause and working to restore full functionality as quickly as possible.
We believe the issue has been resolved after coordination with our AI providers. We are actively monitoring the situation and will notify you if any further problems arise. Thank you for your patience.
This incident has been resolved.
We’re experiencing elevated error rates on our Google Sheets, MySQL, and PostgreSQL integrations. The root cause has been identified and is under active monitoring by our engineering team. All query operations continue to function as expected. We’ll keep you posted with any new developments. Thank you for your patience.
We are continuing to monitor for any further issues.
We've confirmed that the resources affected are operational and have resolved this incident.
Between 12:00pm and 12:08pm, there was a partial outage across many of Retool's product surfaces. There should be no impact outside of that timeframe.
We are aware of an issue where RetoolDB is unavailable for new Retool organizations. We are working with our vendor to get this back online ASAP. This only affects new cloud organizations; organizations pre-incident are not affected.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently looking into reports of users being unable to navigate between apps, whether it be via HTML hyperlink or Retools built in utils (openApp/openUrl)
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results. If you were affected by this behavior, please clear your browser's cache and refresh the page before trying to navigate across apps.
This incident has been resolved. If you were affected by this behavior, please clear your browser's cache and refresh the page before trying to navigate across apps.
We have identified an issue where OAuth requests to Snowflake with any value being passed via the prompt parameter are being rejected. We are actively working on implementing a fix. In the meantime, the current workaround is to remove the prompt parameter entirely from your OAuth requests to Snowflake.
The issue has been fixed on Retool Cloud and all systems are operating normally. Self-hosted customers can remove the `prompt` parameter as a workaround until the patch is available.
An infra routing changed caused elevated backend errors that may have caused resource queries to timeout or fail
GitHub is currently experiencing service issues that may affect Retool users who use GitHub as their source control provider.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have determined that this is related to an issue with one of our external partners. We are awaiting updates on their end and will update here once this is resolved.
Our external partner has pushed out a fix and we are continuing to monitor Retool services.
We have observed stable and healthy performance since 14:43 UTC and are now considering this incident resolved.
We are currently investigating reports of increased latency and intermittent failures while deploying source controlled elements on Retool Cloud.
A potential fix has been implemented and we are monitoring the results
This incident has been resolved.
We are currently investigating reports of users hitting errors with Retool AI actions
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating the source of failures in web calls and latency. Observed a spike of issues around 12:15 but have since recovered.
we've identified minor network instability that caused the failures. Continuing to monitor the situation in case of new regressions
we've identified minor network instability that caused the failures. Continuing to monitor the situation in case of new regressions (typo below)
No additional instability was witnessed over the weekend, this incident is being marked resolved.
Elevated 500 errors on a back-end endpoint preventing some apps from loading
We are currently investigating reports of users being unable to access Retool from various regions outside of the US.
The reported latency looks to have subsided. We are monitoring for any follow-up issues.
This incident has been resolved.
Platform features relying on email sending (invites, password reset etc) will be degraded until the outage is resolved Data connectors using the Retool Email resource type are NOT affected at this time. They should continue to be fully functional.
Provider has fully recovered.
Retool occasionally incorrectly returns a self-signed TLS certificate on a small subset of HTTP requests. This can manifest on any request, affecting normal usage as well as Workflow runs that run resource queries. Our team has identified the issue and is working on a resolution. To address this, the Retool team has intentionally degraded the functionality to create a new custom domain. When creating a custom domain, certificate creation will take longer than usual while this incident is active. Your custom domain creation will progress automatically once this issue is resolved.
We've implemented a stopgap to prevent this issue from reoccurring while we wait to execute a permanent resolution. You may continue to very rarely see this self-signed cert issue.
We've confirmed that the issue has stabilized. We're monitoring for unexpected spikes in errors, but please anticipate a very low rate of errors until a permanent fix has been executed.
We've rolled out the fix and verified that customers should no longer be seeing self-signed TLS certificate errors and that custom-domain provisioning capability has been restored.