Retool Outage History

Retool's licensing service experienced degradation that prevented workflows-worker startup for self-hosted customers using Retool-managed Temporal. The issue affected self-hosted deployments' ability to initialize workflow workers properly. The incident was resolved after 1.5 hours with a fix implementation and monitoring period.

Retool experienced an issue with their MotherDuck integration affecting Cloud organizations. The incident impacted the Web Application and APIs for approximately 5 minutes. The issue was under investigation with no resolution details provided in the available updates.

Retool experienced a major incident with their MotherDuck resource integration that required disabling the service for 13.7 hours while investigating issues. The outage was caused by a caching problem that prevented users from accessing the MotherDuck integration functionality. Retool resolved the incident by identifying and fixing the underlying caching issue, fully restoring access to the MotherDuck resource.

Retool workflows using custom npm libraries failed to execute for 5.5 hours, affecting both Cloud and self-hosted customers. The issue was resolved by deploying a fix to Retool Cloud and releasing patches for self-hosted installations (versions 3.300.28-stable and 3.334.12-stable).

Retool experienced a major outage lasting 63.7 hours where front-end assets from retool-edge.com failed to load, preventing Retool Apps from functioning for affected users. The issue was caused by certain ISPs (including Comcast Business and Optimum) blocking the retool-edge.com domain after it was misclassified by security services. The incident was resolved when Retool worked directly with the affected ISPs to remove the domain blocks, with a temporary workaround available during the outage involving switching to public DNS resolvers like Cloudflare or Google DNS.

Retool Cloud's Google Sheets integration experienced intermittent failures with "premature close" errors, affecting a subset of users for approximately 6 days. The engineering team identified the root cause, deployed multiple fixes with monitoring phases, and fully resolved the issue on April 27th.

Retool Cloud experienced intermittent failures with Google Sheets integrations, causing "premature close" errors that affected a subset of users for 13.4 hours. The issue prevented users from properly accessing or interacting with their Google Sheets resources through Retool applications. The problem was identified, a fix was implemented and monitored, and the incident was fully resolved.

Retool Cloud experienced a major incident where PostgreSQL and REST API resource queries were intermittently failing, which also prevented users from accessing RetoolDB functionality. The engineering team identified the root cause and implemented a fix, with error rates returning to normal levels. The incident was fully resolved after 2.5 hours of service disruption.

Retool Cloud experienced intermittent failures with Google Sheets integrations, causing "premature close" errors that affected a subset of users for 2.1 hours. The issue was identified as part of a larger system problem affecting PostgreSQL and REST API resource queries. The incident was resolved by addressing the underlying broader infrastructure issue.

Retool Cloud customers using custom domains experienced failures when attempting to complete OAuth2 Resource Authentication flows for 6.7 hours. Affected users could work around the issue by authenticating through their base .retool.com domain instead. The issue was identified and resolved with a fix implementation.