outages.live
Live

Render

Render is operational

Checked 23 s ago Operational

History

90 days agoToday

Incidents in 90 days

12

Days with an incident

13

Median duration

1 h 32 min

Longest incident

3 h 53 min

Components

57
Render Dashboard Operational
90 days ago2 days with an incidentToday
Render Website Operational
90 days agoNo incidentsToday
Render Platform API Operational
90 days agoNo incidentsToday
Render REST API Operational
90 days agoNo incidentsToday
Static Sites Operational
90 days ago1 day with an incidentToday
Custom Domains Operational
90 days agoNo incidentsToday
One-Off Jobs Operational
90 days agoNo incidentsToday

Oregon

Web Services Operational
90 days ago1 day with an incidentToday
Cron Jobs Operational
90 days ago1 day with an incidentToday
Background Workers Operational
90 days ago1 day with an incidentToday
Builds and Deploys Operational
90 days ago7 days with an incidentToday
PostgreSQL Operational
90 days ago1 day with an incidentToday
Redis Operational
90 days ago1 day with an incidentToday
Web Services - Free Tier Operational
90 days ago1 day with an incidentToday
Autoscaling Operational
90 days ago1 day with an incidentToday
Metrics/Logs Operational
90 days agoNo incidentsToday
Workflows Operational
90 days ago2 days with an incidentToday

Frankfurt

Web Services Operational
90 days agoNo incidentsToday
Cron Jobs Operational
90 days agoNo incidentsToday
Background Workers Operational
90 days agoNo incidentsToday
Builds and Deploys Operational
90 days ago3 days with an incidentToday
PostgreSQL Operational
90 days agoNo incidentsToday
Redis Operational
90 days agoNo incidentsToday
Web Services - Free Tier Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 24, 2026

Duration30 min07:11 to 07:41Platform emails not being sentNotice

This incident has been resolved.

Oct 23, 2026

Duration1 h 28 min16:05 to 17:34Degraded network performanceDegraded

This incident has been resolved.

Oct 20, 2026

Duration3 h 41 min20:48 to 00:29Deploying from GitLab may intermittently failDegraded

This incident has been resolved.

Oct 15, 2026

Duration1 h 35 min20:58 to 22:33Dashboard not updating in real time; Some Workflows SDK requests timing outDegraded

This incident has been resolved.

Oct 14, 2026

Duration2 h 45 min19:32 to 22:18Builds, deploys, and queued deploys are not starting in all regionsPartial outage

### 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

Oct 3, 2026

Duration46 min19:35 to 20:21Degraded Dashboard Performance; Degraded builds & deploys in OregonDegraded

This incident has been resolved.

Sep 27, 2026

Duration1 h 37 min01:24 to 03:01Observing service instability from our upstream provider AWS in Oregon regionDegraded

This incident has been resolved.

Sep 25, 2026

Duration12 min18:26 to 18:38Build and deploy failures in OregonPartial outage

Builds and deploys failed for a subset of services in Oregon. Services using a prebuilt Docker image and static sites were unaffected.

Sep 9, 2026

Duration12 min21:26 to 21:38Elevated Build and Deploy Times in the Oregon RegionDegraded

This incident has been resolved.

Sep 2, 2026

Duration21 min17:19 to 17:40Degraded builds/deploysPartial outage

This incident has been resolved.

Aug 31, 2026

Duration2 h 22 min15:47 to 18:09Service instability in SingaporePartial outage

This incident has been resolved.

Aug 20, 2026

Duration3 h 53 min15:47 to 19:40Deployment IssuesPartial outage

This incident has been resolved.

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.live/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.live/feed.xml?providers=render
Slack
/feed subscribe https://outages.live/feed.xml?providers=render

Go from tracking outages to fixing production issues with Polylane.

Try Polylane