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
14 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 history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 921:26 UTC | Elevated Build and Deploy Times in the Oregon Region | minor | 12m |
| Sep 217:19 UTC | Degraded builds/deploys | major | 21m |
| Aug 3120:24 UTC | Some Web services in Oregon unavailable | minor | 0m |
| Aug 3115:47 UTC | Service instability in Singapore | major | 2h 22m |
| Aug 2015:47 UTC | Deployment Issues | major | 3h 53m |
| Jul 2714:43 UTC | Degraded dashboard performance | minor | 28h 52m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.