Render reported "Render Maintenance Period" on its status page at 2026-11-18 02:00 UTC.

When did the maintenance start and end?

It started at 2026-11-18 02:00 UTC. This page shows the end time when Render marks it resolved.

How do I get alerts for Render?

Subscribe to the Render live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Render. outages.live reads it every few minutes and keeps every update.

RenderMaintenance ·

Render Maintenance Period

Q: What is affected?

Render lists these components: Render Dashboard, Render Platform API, Render REST API, One-Off Jobs.

MaintenanceOfficial update

We will be upgrading critical infrastructure on November 17th at 6:00 pm PST (November 18th 0200 UTC). For up to 30 minutes, you will be unable to view, edit, create or deploy services and databases. The REST API and one-off jobs will also be unavailable. There will be no interruptions to deployed services and databases. If you need help, please get in touch at support@render.com or talk to us on our community forum, https://community.render.com

The latest update from Render.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Render

Scheduled

Affected components

Render DashboardRender Platform APIRender REST APIOne-Off Jobs

Render in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 35 min

This incident

Not comparable

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

3 h 53 min

median 1 h 35 min

90 days agoToday

Other Render incidents

All incidents

Render·Issues affecting connections to a subset of Postgres Databases

Render reports connection failures for some Postgres databases that route traffic through a self managed PgBouncer instance. The affected regions are Oregon, Frankfurt, Ohio, and Singapore. Render states that the incident is resolved, and it lasted about 3 hours and 44 minutes. Updating the self managed PgBouncer to use scram-sha-256 encryption can remediate the failures, and Render support can also take corrective action.

Resolved

Render·Platform emails not being sent

This incident has been resolved.

Resolved

Render·Degraded network performance

This incident has been resolved.

Resolved

Render·Deploying from GitLab may intermittently fail

This incident has been resolved.

Resolved

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

This incident has been resolved.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane