Retool Database unavailable for some Retool Cloud organizations
minor- Started
- Nov 13, 7:50 PM EST
- Resolved
- Nov 18, 11:49 PM EST
- Duration
- 123h 59m
Retool's updates (4)
- identified · Nov 13, 7:50 PM EST
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.
- identified · Nov 17, 7:06 PM EST
We are currently planning a data migration that will restore access to all affected databases. Some have already been migrated. Until that process finishes, apps and workflows in affected organizations that query Retool Database will continue to return errors.
- monitoring · Nov 17, 9:18 PM EST
The majority of affected databases have been successfully migrated and relevant organizations have had their access restored. App and workflow queries should now execute as expected. External connections via raw connection string will need to be updated.
- resolved · Nov 18, 11:49 PM EST
All affected databases have been migrated. App and workflow queries should now execute as expected. External connections via raw connection string will need to be updated.
What our checks recorded
We checked Retool 575 times from Retool's start time to its resolution, once every five minutes. Every one of them reached Retool's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 120 ms, against 151 ms over the 24 hours before. Retool posted the incident at Nov 13, 7:50 PM EST.
Updates are Retool's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗