mediumResolvedRender

Render: Issues affecting connections to a subset of Postgres Databases

Investigating(done)
Trending(skipped)
Workaround available(skipped)
Resolved(current)

Executive summary

A configuration change rolled out to a subset of Render Postgres instances caused connection failures for databases routing traffic through self-managed PgBouncer instances. The incident has been resolved.

Workaround available

Updating your self managed PgBouncer to use scram-sha-256 encryption will remediate the connection failures.

Reported inStatusevidence [1]

Official fix

Technical root cause

A configuration change rolled out to a small subset of Postgres instances caused connection failures for databases routing traffic through self-managed PgBouncer instances.

Evidence

1 report · 1 StatusShow

[1]
Status First report2 days ago
Issues affecting connections to a subset of Postgres Databases(opens official status page in a new tab)
Identified: 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…
by render status

Timeline

First report on status pageNov 5, 23:56 UTC
Issues affecting connections to a subset of Postgres Databases
Source
Official statementNov 5, 23:56 UTC
Identified: A configuration change was rolled out to a small subset of Postgres instances.
Source
Workaround discoveredNov 5, 23:56 UTC
Workaround reported: Updating your self managed PgBouncer to use scram-sha-256 encryption will remediate the connection failures.
Source
Status changedNov 5, 23:56 UTC
Status changed: new → resolved (official status page reports resolution).