outages.live
Live
RetoolIncident ·

Retool Database unavailable for some Retool Cloud organizations

DegradedOfficial update
0

Retool Database is unavailable for a very small subset of Retool Cloud organizations on legacy database infrastructure. Apps and workflows in those organizations return errors when they query Retool Database. Retool has identified the issue.

State

Identified

Started

Ongoing for

6 h 3 min

Worst impact

Degraded

Timeline

1 update
00:5002:2103:5105:2206:53
DegradedUpdate postedTimes in UTC

Identified

6 h 3 min 100%

Updates

Times in UTC

As posted by Retool

Identified

In order to protect customer data from a recently disclosed security vulnerability, we've taken Retool Database offline for a very small subset of Retool Cloud organizations hosted on some legacy database infrastructure. Apps and workflows in those organizations that query Retool Database will return errors until it's restored.

Affected components

1
RetoolDB

Retool in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

20

Median duration

3 h 35 min

This incident

1.7× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 3 h 35 min
90 days agoToday

Other Retool incidents

All incidents

Retool·Some antivirus products are blocking retool.app

Some antivirus products blocked retool.app and stopped the New app builder from loading. Retool services operated normally. Norton, AVG and Avast users saw warnings clear. The incident is resolved and lasted about 72 hours.

Resolved

Retool·Source Control Deployments Stalled

This incident has been resolved.

Resolved

Retool·Elevated Latency on Query Execution (Retool Cloud)

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

Resolved

Retool·Elevated Latency on Query Execution (Retool Cloud)

This incident has been resolved.

Resolved

Retool·Retool MCP connection errors

This incident has been resolved.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane