Elevated latency for some new services when using the onrender.com address
Feb 4, 17:13 UTCFeb 4, 18:42 UTC
Duration
1h 30m
Impact
Major
Root cause
Not disclosed
Render, 90 days
15 incidents
Affected
Web ServicesStatic SitesWeb Services - Free TierOregon - Web ServicesOregon - Web Services - Free TierFrankfurt - Web ServicesFrankfurt - Web Services - Free TierOhio - Web ServicesOhio - Web Services - Free TierSingapore - Web ServicesSingapore - Web Services - Free TierVirginia - Web ServicesVirginia - Web Services - Free Tier
Final update
Latency has returned to expected levels. Affected services were those created between 2026-02-04T16:30Z and 2026-02-04T18:17Z. Services created outside that period were not affected.
Timeline
- Resolved · Feb 4, 18:42 UTC
Latency has returned to expected levels. Affected services were those created between 2026-02-04T16:30Z and 2026-02-04T18:17Z. Services created outside that period were not affected.
- Identified · Feb 4, 17:29 UTC
We have determined that services are reachable through their onrender.com address. Requests will be successful but may take longer. We are continuing to work on a fix.
- Identified · Feb 4, 17:21 UTC
The issue has been identified and a fix is being implemented.
- Investigating · Feb 4, 17:13 UTC
We are currently investigating this issue.
More from Render
Full historyIssues affecting connections to a subset of Postgres Databaseslasted 3h 44mPlatform 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 45m