Render: Issues affecting connections to a subset of Postgres Databases

What to do

Check whether you use Render PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 3h 44m it lasted.
Anything that failed between 2026-11-05 20:12 UTC and 2026-11-05 23:56 UTC may need a replay.
Subscribe to Render's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=render works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

identifiedNov 5, 2026, 8:12 PM UTC
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.
provider
resolvedNov 5, 2026, 11:56 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Render still down?

No, this incident was resolved 2026-11-05 23:56 UTC. For Render's live state, see https://down.guide/render.

How long did it last?

3h 44m, from 2026-11-05 20:12 UTC to 2026-11-05 23:56 UTC, by the times Render posted.

What was affected?

Render named PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL.

What caused it?

Render hasn't published a root cause. If it does, it shows here.

Where does this come from?

Render's official status page, https://status.render.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.