Major impactResolvedCloud

Render outage: Ohio Services with Disks, Data Persistence failing

Render reported this major-impact incident on its official status page on Mar 3, 2026, 00:41 UTC. It was resolved after 20 min.

Right now Render is operational. Live Render status →

🔔 Get alerted when Render has issuesFree · email alerts · no credit card
Mar 3, 2026, 00:41 UTC
started
Mar 3, 2026, 01:00 UTC
resolved
20 min
duration
Major
impact

Affected components

  • Background Workers
  • PostgreSQL
  • Redis
  • Web Services

Timeline

updates from Render's status page ↗
  1. resolvedMar 3, 2026, 01:00 UTC

    All affected services have been migrated to new hosts and are running at this time. This incident has been resolved.

  2. identifiedMar 3, 2026, 00:59 UTC

    Many services have recovered with healthy disks on new hosts, however this issue remains open as some services are still impaired.

  3. identifiedMar 3, 2026, 00:41 UTC

    Services located in Ohio, both application types (Web Service, Private Service, etc.) and data types (Postgres, Key Value with persistence) are failing due to disk errors. We are working on mitigations.

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.

How often does Render have incidents?

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

← Previous: Some deploys may be slow or hanging (Feb 11, 2026)Next: Custom domains are unable to be created (Mar 9, 2026) →
Render outage on Mar 3, 2026: Ohio Services with Disks, Data Persistence failing · APIStatus.watch