Builds, deploys, and queued deploys are not starting in all regions

Timeline

1. 19:32 UTC Render status page · Reported Builds, deploys, and queued deploys are not starting in all regions
2. 19:32 UTC Render status page · Investigating We are currently investigating this issue.
3. 19:39 UTC Render status page · Identified The issue has been identified and a fix is being implemented.
4. 19:45 UTC Render status page · Monitoring A fix has been implemented and we are monitoring the results.
5. 19:47 UTC Render status page · Monitoring We are continuing to monitor for any further issues.
6. 20:41 UTC Render status page · Monitoring We are temporarily pausing deploys to free services.
7. 20:55 UTC Render status page · Identified The issue has been identified and a fix is being implemented.
8. 20:57 UTC Render status page · Identified Builds are failing to start again across all regions, and our team is still working to address the root cause. Deploys for free services remain paused. We'll share another update as soon as we have more information.
9. 21:43 UTC Render status page · Monitoring A fix has been implemented, and we are monitoring the results. Deploys and builds for services running on free instances continue to be paused.
10. 22:18 UTC Render status page · Resolved This incident has been resolved.
11. 17:58 UTC Render status page · Postmortem ### Summary On October 14, 2026, between 12:12 and 15:08 PDT \(19:12 - 22:08 UTC\), builds and deploys across all regions failed to start, stalled, or were significantly delayed during two periods of impact totaling about 2 hours and 20 minutes. The cause was a database schema migration run as part of a planned version upgrade of our internal job scheduler that coordinates builds, deploys, and other critical platform operations. The migration led to high load and a longer-than-expected recovery time of this system’s database. We will change how we perform upgrades and modifications of this…