Incidentsby GlyphIssues affecting connections to a subset of Postgres Databases
Nov 5, 20:12 UTCNov 5, 23:56 UTC
Duration
3h 44m
Impact
Minor
Root cause
Not disclosed
Render, 90 days
15 incidents
Affected
PostgreSQLOregon - PostgreSQLFrankfurt - PostgreSQLOhio - PostgreSQLSingapore - PostgreSQL
Final update
This incident has been resolved.
Timeline
- Resolved · Nov 5, 23:56 UTC
This incident has been resolved.
- Identified · Nov 5, 20:12 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.
More from Render
Full historyPlatform emails not being sentlasted 30mDegraded network performancelasted 1h 28mDeploying from GitLab may intermittently faillasted 3h 41mDashboard not updating in real time; Some Workflows SDK requests timing outlasted 1h 35mBuilds, deploys, and queued deploys are not starting in all regionslasted 2h 45mDegraded Dashboard Performance; Degraded builds & deploys in Oregonlasted 46m