Major impactResolvedCloud

Render outage: Elevated latency for some new services when using the onrender.com address

Render reported this major-impact incident on its official status page on Feb 4, 2026, 17:13 UTC. It was resolved after 1h 30m.

Right now Render is operational. Live Render status →

🔔 Get alerted when Render has issuesFree · email alerts · no credit card
Feb 4, 2026, 17:13 UTC
started
Feb 4, 2026, 18:42 UTC
resolved
1h 30m
duration
Major
impact

Affected components

  • Static Sites
  • Web Services
  • Web Services - Free Tier
  1. resolvedFeb 4, 2026, 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.

  2. identifiedFeb 4, 2026, 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.

  3. identifiedFeb 4, 2026, 17:21 UTC

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

  4. investigatingFeb 4, 2026, 17:13 UTC

    We are currently investigating this issue.

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 31m. See Render's uptime and incident history

Render outage on Feb 4, 2026: Elevated latency for some new services when using the onrender.com address · APIStatus.watch