Render lists these components: Render Dashboard, Render Platform API, Render REST API.

When did the incident start and end?

It started at 2026-11-11 13:17 UTC and ended at 2026-11-11 13:35 UTC. It lasted 18 min.

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. A language model writes the summary from those updates.

RenderIncident ·

API Performance Issues

Q: What happened?

Render reported "API Performance Issues" on its status page at 2026-11-11 13:17 UTC. Render reported degraded performance on the Render Dashboard, the Render Platform API, and the Render REST API. Render monitored the return to normal performance and then resolved the incident. The incident lasted 18 minutes.

ResolvedOfficial update

Render reported degraded performance on the Render Dashboard, the Render Platform API, and the Render REST API. Render monitored the return to normal performance and then resolved the incident. The incident lasted 18 minutes.

State

Resolved

Started

Lasted

18 min

Worst impact

Degraded

Timeline

3 updates

13:1713:2213:2613:3113:35

DegradedUpdate postedTimes in UTC

Investigating

10 min 54%

Monitoring

8 min 46%

Updates

Times in UTC

As posted by Render

Resolved

This incident has been resolved.

Monitoring

API performance is returning to normal levels. We are continuing to monitor.

Investigating

We are currently investigating issues related to API performance. The dashboard and API requests are affected.

Affected components

Render DashboardRender Platform APIRender REST API

Render in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 32 min

This incident

80% 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·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