Skip to main content
Retool

New Retool Organizations cannot provision RetoolDB

Degraded Lasted 9h 37m · started · Retool's page

Level
confirmed
Worst impact
Degraded
Components
RetoolDB
Down Index
23of 100

What to do

  • Check whether you use Retool RetoolDB. 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 9h 37m it lasted.

    Anything that failed between 2026-02-03 13:30 UTC and 2026-02-03 23:07 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 3

  1. identified

    We are aware of an issue where RetoolDB is unavailable for new Retool organizations. We are working with our vendor to get this back online ASAP. This only affects new cloud organizations; organizations pre-incident are not affected.

    provider

  2. identified

    We are continuing to work on a fix for this issue.

    provider

  3. 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-3bd20a731f

Is Retool still down?

No, this incident was resolved 2026-02-03 23:07 UTC. For Retool's live state, see https://down.guide/retool.

How long did it last?

9h 37m, from 2026-02-03 13:30 UTC to 2026-02-03 23:07 UTC, by the times Retool posted.

What was affected?

Retool named RetoolDB.

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.