Issues affecting connections to a subset of Postgres Databases
Render reports connection failures for a subset of Postgres databases in Oregon, Frankfurt, Ohio, and Singapore. Render identified the cause as a Postgres connection setting change that affects databases using a self managed PgBouncer instance. Render states that updating self managed PgBouncer to scram-sha-256 encryption will remediate the failures.
State
Identified
Started
Ongoing for
1 h 51 min
Worst impact
Degraded
Timeline
3 updatesIdentified
1 h 51 min 100%
Updates
Times in UTCAs posted by Render
A configuration change was rolled out to a small subset of Postgres instances. The change causes connection failures for some databases that route traffic through a self managed PgBouncer instance. Updating your self managed PgBouncer to use scram-sha-256 encryption will remediate the connection failures. If you do not see any issues in your connections, no corrective action is needed. If you need help remediating, please reach out to Render support and we can take corrective action.
A configuration change to Postgres connection settings caused connection failures for a subset of databases that route traffic through a self managed PgBouncer instance. Updating your self managed PgBouncer to use scram-sha-256 encryption can help remediate the connection failures. If you need help remediating, please reach out to Render support and we can take corrective action.
A configuration change to Postgres connection settings caused connection failures for some databases that route traffic through a self managed PgBouncer instance. Updating your self managed PgBouncer to use scram-sha-256 encryption can help remediate the connection failures. If you need help remediating, please reach out to Render support and we can take corrective action.
Affected components
5Render in the last 90 days
Full historyIncidents in 90 days
13
Days with an incident
14
Median duration
1 h 32 min
This incident
1.2× the median
Other Render incidents
All incidentsRender·Platform emails not being sent
This incident has been resolved.
Render·Degraded network performance
This incident has been resolved.
Render·Deploying from GitLab may intermittently fail
This incident has been resolved.
Render·Dashboard not updating in real time; Some Workflows SDK requests timing out
This incident has been resolved.
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
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.
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.
https://outages.live/feed.xml?providers=render/feed subscribe https://outages.live/feed.xml?providers=renderFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane