Render incident: Queued deploys stuck

Affected components

• Builds and Deploys

1. resolvedJun 11, 2026, 18:12 UTC

   This incident has been resolved.

2. identifiedJun 11, 2026, 16:44 UTC

   We are continuing to work on a fix for this issue. In the meantime, stuck deploys can be cleared with these steps: * 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"

3. identifiedJun 11, 2026, 16:01 UTC

   The earlier "Platform latency" incident has affected queued deploys. We are implementing a fix

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Render's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• DigitalOcean: DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"Major · Jun 11, 2026, 14:24 UTC
• Akamai: Edge Delivery - HTTP Content Delivery in EuropeMinor · Jun 5, 2026, 16:36 UTC
• LaunchDarkly: Delays in event ingestionMinor · Jun 9, 2026, 12:08 UTC
• Akamai: Bot Manager Premier IssuesMinor · Jun 10, 2026, 18:38 UTC
• Contentful: Issues with content editing and publishing for some EU customersMinor · Jun 11, 2026, 12:29 UTC
• LiveKit: Intermittent errors for Google Gemini models via InferenceMinor · Jun 11, 2026, 17:52 UTC

How often does Render have incidents?

Render reported 16 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 1h 31m. See Render's uptime and incident history