outages.live
Live
RenderIncident · 2026-09-02 17:19 UTC

Degraded builds/deploys

ResolvedOfficial update

This incident has been resolved.

The latest update from Render.

State

Resolved

Started

60 d ago

2026-09-02 17:19 UTC

Lasted

21 min

until 2026-09-02 17:40 UTC

Worst impact

Partial outage

Timeline

3 updates
17:1917:2517:3017:3517:40
Partial outageUpdate postedTimes in UTC

Investigating

10 min 50%

Monitoring

10 min 50%

Updates

Times in UTC

As posted by Render

Resolved2026-09-02 17:40 UTC

This incident has been resolved.

Monitoring2026-09-02 17:30 UTC

A fix has been implemented and we are monitoring the results.

Investigating2026-09-02 17:19 UTC

We are currently investigating this issue.

Affected components

6
Builds and DeploysOregon - Builds and DeploysFrankfurt - Builds and DeploysOhio - Builds and DeploysSingapore - Builds and DeploysVirginia - Builds and Deploys

Render in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

12

Days with an incident

13

Median duration

1 h 32 min

This incident

77% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 53 min
median 1 h 32 min
90 days agoToday

Other Render incidents

All incidents

Render·Platform emails not being sent

This incident has been resolved.

Resolvedresolved 8 d ago

Render·Degraded network performance

This incident has been resolved.

Resolvedresolved 9 d ago

Render·Deploying from GitLab may intermittently fail

This incident has been resolved.

Resolvedresolved 11 d ago

Render·Dashboard not updating in real time; Some Workflows SDK requests timing out

This incident has been resolved.

Resolvedresolved 16 d ago

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

### 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 system in a highly available fashion in the future so that a similar change cannot cause an outage again. ### Impact There were two periods of impact. During this time, live user services were not affected, but builds and deploys across all regions failed to start, failed to finish, or were significantly delayed. **Period 1: 12:12 - 12:40 PDT \(19:12 - 19:40 UTC\), about 28 minutes** * New builds and

Resolvedresolved 17 d ago

Follow Render

Your coding agent knows when Render is down, and tells you when a failure is theirs, not yours. You can also get Render incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "render" and tell me if Render has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=render
Slack
/feed subscribe https://outages.cc/feed.xml?providers=render

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane