outages.live
Live

Retool

Retool is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Retool status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Retool since . The days before that show only what Retool published.

Incidents in 90 days

10

Days with an incident

17

Median duration

3 h 26 min

Longest incident

7 days

Components

14
New app builder Operational
90 days ago3 days with an incidentToday
Classic web app Operational
90 days agoNo incidentsToday
Infrastructure Operational
90 days agoNo incidentsToday
Workflows Operational
90 days agoNo incidentsToday
Resource Queries Operational
90 days ago10 days with an incidentToday
License server Operational
90 days agoNo incidentsToday
Email Server Operational
90 days agoNo incidentsToday
RetoolDB Operational
90 days agoNo incidentsToday
Platform APIs Operational
90 days ago2 days with an incidentToday
Retool-managed Temporal (via Temporal.io) Operational
90 days agoNo incidentsToday
Source Control Operational
90 days ago3 days with an incidentToday
Audit Trails Operational
90 days agoNo incidentsToday
Self Hosted On-Premise Operational
90 days ago1 day with an incidentToday
MCP Server Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 12, 2026

Duration1 h 33 min to Source Control Deployments StalledDegraded

This incident has been resolved.

Oct 5, 2026

Duration7 days to Elevated Latency on Query Execution (Retool Cloud)Degraded

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

Oct 2, 2026

Duration2 h 27 min to Elevated Latency on Query Execution (Retool Cloud)Degraded

This incident has been resolved.

Sep 14, 2026

Duration6 h 10 min to Retool MCP connection errorsDegraded

This incident has been resolved.

Sep 8, 2026

Duration2 h 14 min to Retool MCP connection failuresDegraded

This incident has been resolved.

Sep 1, 2026

Duration3 h 35 min to Errors running generic JDBC resource type queriesNotice

This incident has been resolved.

Aug 20, 2026

Duration5 h 54 min to React App Builder Sandbox Installs May Fail to Install DependenciesPartial outage

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

Aug 17, 2026

Duration3 h 17 min to Source Control Degradation due to Github OutageDegraded

Github has resolved their incident.

Aug 14, 2026

Duration3 h 53 min to Errors calling resources with Per-User authentication in Apps built with the New App EditorPartial outage

This incident has been resolved.

Aug 6, 2026

Duration49 min to Errors saving changes in React appsDegraded

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.

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

RSS
https://outages.live/feed.xml?providers=retool
Slack
/feed subscribe https://outages.live/feed.xml?providers=retool

Go from tracking outages to fixing production issues with Polylane.

Try Polylane