Retool Outage History

Retool Mobile apps failed to load when accessed through web browser previews, including both the in-browser "View" mode and editor preview functionality. The issue affected the Web Application and APIs components while native iOS/Android mobile apps and editing capabilities remained functional. The incident was resolved after 4.1 hours following identification and implementation of a fix.

Retool Mobile app users on iOS and Android experienced sign-in issues where they were returned to the sign-in screen after authenticating or unable to complete sign-in entirely. The problem was caused by a change to mobile session validation, which was identified and rolled back after over 8 days. The incident was resolved with users needing to clear app cache on Android or reinstall the app on iOS to restore functionality.

Retool experienced elevated 504 errors that impacted cloud users for 16 minutes, affecting the web application and APIs. A fix was implemented and monitored before the incident was fully resolved.

Retool experienced an issue where some pages were returning "Page not found" errors when users attempted to load them. The incident affected the Web Application and APIs for 3.7 hours. The issue was resolved after implementing a fix and monitoring the results.

Retool experienced an issue where some pages were returning "Page not found" errors, affecting the web application and APIs. The incident lasted 2.3 hours before a fix was implemented and the service was restored to normal operation.

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.