Services not accessible
Dec 5, 09:01 UTCDec 5, 09:36 UTC
Duration
35m
Impact
Major
Root cause
Not disclosed
Render, 90 days
15 incidents
Affected
Not listed by the vendor.
Final update
From 08:47 to 09:11 UTC, all incoming web traffic in every region failed to reach services and returned 500 errors instead. Our dashboard and API were down too. Background workers, private services, and cron jobs were not affected. The upstream provider has recovered now, and we’re no longer seeing any issues on our side.
Timeline
- Resolved · Dec 5, 09:36 UTC
From 08:47 to 09:11 UTC, all incoming web traffic in every region failed to reach services and returned 500 errors instead. Our dashboard and API were down too. Background workers, private services, and cron jobs were not affected. The upstream provider has recovered now, and we’re no longer seeing any issues on our side.
More from Render
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2423:36 UTC | Key Value service restarts | minor | 0m |
| 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 |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.