Render incident: Investigating Intermittent Postgres Connectivity Issues in the Oregon Region

Affected components

• PostgreSQL

1. resolvedMay 20, 2026, 18:57 UTC

   This incident has been resolved.

2. monitoringMay 20, 2026, 18:23 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedMay 20, 2026, 18:17 UTC

   The issue has been identified and a fix is being implemented.

4. investigatingMay 20, 2026, 18:01 UTC

   We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Render's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• ClickHouse Cloud: GCP us-east1 capacity constraints impacting cluster operationsMinor · May 18, 2026, 12:31 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Akamai: Configuration Deployment issues with EdgeWorkers and mPulse configuration activationsMinor · May 20, 2026, 14:29 UTC

How often does Render have incidents?

Render reported 16 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 1h 31m. See Render's uptime and incident history