Live  /  Retool  /  Incident

Retool: Source Control Deployments Stalled

Retool · retool.comMinor incidentResolved2026-10-13 00:16 UTC
Public — what happened

Summary

Retool said that on Retool Cloud version 4.74.0, deployments made through its Source Control feature were getting stuck waiting in a queue, beginning at 22:44 UTC on October 12, 2026. The company said it had pinpointed the problem by 22:55 UTC but did not describe a cause, and it began rolling out a fix at 23:25 UTC. By 23:46 UTC Retool reported the fix was fully in place and deployments should be working normally again. The incident was marked resolved at 00:16 on October 13.

Affected

Source Control

As listed on Retool’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Retool against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Retool: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Retool report →

More from Retool

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Retool status & history page.

Related: Retool status & history. SquidGrid is not affiliated with Retool.