- Level
- confirmed
- Worst impact
- Degraded
- Components
- Resource Queries
- Down Index
- 21of 100
What to do
Check whether you use Retool Resource Queries. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 35m it lasted.
Anything that failed between 2026-09-01 15:31 UTC and 2026-09-01 19:06 UTC may need a replay.Subscribe to Retool's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=retool works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Retool 2
- identified
Some customers are seeing generic JDBC resource type queries fail with an error referencing LZ4 compression. Connection tests still pass, so the error appears only when running a query or loading a resource schema. We have identified the cause and are working on a fix.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-4970234724
Is Retool still down?
No, this incident was resolved 2026-09-01 19:06 UTC. For Retool's live state, see https://down.guide/retool.
How long did it last?
3h 35m, from 2026-09-01 15:31 UTC to 2026-09-01 19:06 UTC, by the times Retool posted.
What was affected?
Retool named Resource Queries.
What caused it?
Retool hasn't published a root cause. If it does, it shows here.
Where does this come from?
Retool's official status page, https://status.retool.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.