Skip to main content
Retool

Source Control Degradation due to Github Outage

Degraded Lasted 3h 17m · started · Retool's page

Level
confirmed
Worst impact
Degraded
Components
Source Control
Down Index
21of 100

What to do

  • Check whether you use Retool Source Control. 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 17m it lasted.

    Anything that failed between 2026-08-17 18:32 UTC and 2026-08-17 21:49 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

  1. monitoring

    An upstream incident with Github (https://www.githubstatus.com/incidents/zkxwbgr0cnmx) is causing issues with source control in Retool. Github has deployed a fix and we are monitoring.

    provider

  2. resolved

    Github has resolved their incident.

    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-c9c1ffe8b0

Is Retool still down?

No, this incident was resolved 2026-08-17 21:49 UTC. For Retool's live state, see https://down.guide/retool.

How long did it last?

3h 17m, from 2026-08-17 18:32 UTC to 2026-08-17 21:49 UTC, by the times Retool posted.

What was affected?

Retool named Source Control.

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.