Render Status · History · Incident #4541
RESOLVEDStuck queued deploys
Minor · Started Jun 11, 2026 · 7:42 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Render Status · History · Incident #4541
RESOLVEDMinor · Started Jun 11, 2026 · 7:42 PM
Duration
49m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved. If you still have a stuck queued deploy, follow the instructions below under "Investigating" to clear the queue. It should then work again as expected going forward.
Started
Jun 11, 2026 · 7:42 PM
Resolved
Jun 11, 2026 · 8:32 PM
Duration
49m
Severity
Minor
Event timeline
Investigating
Jun 11 · 7:42 PM RenderWe are currently investigating the problem. Try this work-around to get deploys going again: * Go into Workspace Settings * Change the Overlapping Deploy Policy to "Override" * Initiate a new deploy (which will then cancel the stuck deploy) * Change the Deploy Policy back to "Wait"
Monitoring
Jun 11 · 7:59 PM RenderA fix has been implemented and we are monitoring the results.
Resolved
Jun 11 · 8:32 PM RenderThis incident has been resolved. If you still have a stuck queued deploy, follow the instructions below under "Investigating" to clear the queue. It should then work again as expected going forward.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026