Minor impactResolvedCloud

Render incident: Delayed deployment for new services in Oregon region

Render reported this minor-impact incident on its official status page on Apr 23, 2026, 16:51 UTC. It was resolved after 30 min.

Right now Render is operational. Live Render status →

🔔 Get alerted when Render has issuesFree · email alerts · no credit card
Apr 23, 2026, 16:51 UTC
started
Apr 23, 2026, 17:21 UTC
resolved
30 min
duration
Minor
impact

Affected components

  • Web Services

Timeline

updates from Render's status page ↗
  1. resolvedApr 23, 2026, 17:21 UTC

    This incident has been resolved.

  2. monitoringApr 23, 2026, 17:06 UTC

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

  3. identifiedApr 23, 2026, 16:59 UTC

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

  4. investigatingApr 23, 2026, 16:51 UTC

    We are investigating an issue where new services created in the Oregon region are taking longer than usual to deploy.

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 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

← Previous: Some web services and databases in Oregon are unresponsive (Apr 16, 2026)Next: HA Postgres Unavailability (May 7, 2026) →
Render incident on Apr 23, 2026: Delayed deployment for new services in Oregon region · APIStatus.watch