Render Outage History

Render is up right now

Pingoru has recorded 82 incidents for Render: 79 in the last 12 months and 15 in the last 90 days.

Source: status.render.com

82incidents recorded
79last 12 months
15last 90 days
3 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct2%
Pingoru began tracking Render in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026816 of 720 (2%)
May 202664 of 744 (1%)
June 20261012 of 720 (2%)
July 2026943 of 744 (6%)
August 202636 of 744 (1%)
September 202652 of 720 (0%)
October 2026611 of 585 (2%)

Incidents, newest first

Minor October 30, 2025 Failure to spin free web services back up after inactivity –

Started Oct 30, 2025, 05:00 PM UTC· resolved Oct 30, 2025, 05:00 PM UTC

  1. resolved Oct 30, 2025, 07:08 PM UTC

    Between 2025-10-28 at 17:00 UTC and 2025-10-30 at 17:22 UTC, a change was active that caused some free web services to fail to spin back up after inactivity. Most free web services were unaffected. While the change was reverted, any services that remain impacted should redeploy to resolve.

Read the full incident report →

Minor October 28, 2025 Degraded builds and deploys in Virginia 51m Builds and Deploys

Started Oct 28, 2025, 05:08 PM UTC· resolved Oct 28, 2025, 05:59 PM UTC

  1. investigating Oct 28, 2025, 05:08 PM UTC

    Builds and deploys may be slower than usual. We are currently investigating this issue.

  2. identified Oct 28, 2025, 05:34 PM UTC

    An upstream provider is experiencing issues provisioning infrastructure. We continue to monitor the situation. Paid services are experiencing less delay than free services.

  3. resolved Oct 28, 2025, 05:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 23, 2025 Pre-deploys are failing in some regions 1h 47m Web Services, Builds and Deploys

Started Oct 23, 2025, 04:27 PM UTC· resolved Oct 23, 2025, 06:15 PM UTC

  1. investigating Oct 23, 2025, 04:27 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 23, 2025, 04:29 PM UTC

    We think some pre-deploys are failing in Oregon and Frankfurt. We haven’t found any other affected regions so far, but we’re actively checking.

  3. investigating Oct 23, 2025, 04:47 PM UTC

    Some pre-deploys in Singapore are also affected.

  4. identified Oct 23, 2025, 04:56 PM UTC

    We’ve found the root cause and are rolling out a fix.

  5. monitoring Oct 23, 2025, 05:22 PM UTC

    A fix has been rolled out, and a re-deploy should now work as expected. We’re still keeping an eye on how the fix performs though.

  6. resolved Oct 23, 2025, 06:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025 An upstream provider is experiencing some issues that are affecting parts of our platform (Virginia) 13h 18m Web Services, Cron Jobs, Background Workers, Builds and Deploys and 5 more

Started Oct 20, 2025, 09:58 AM UTC· resolved Oct 20, 2025, 11:16 PM UTC

  1. monitoring Oct 20, 2025, 09:58 AM UTC

    We started seeing increased errors in our infrastructure around 08:00 UTC. Parts of our platform were affected by an outage with an upstream provider. We know that new database creation and backup creation were impacted, but we’re still assessing if there’s any broader impact. We’re seeing signs of recovery now, but we’re continuing to monitor.

  2. monitoring Oct 20, 2025, 10:13 AM UTC

    Several of our tools were also affected during that time, including support tools, so responses may have been delayed or missed between 08:00 and 09:30 UTC. We’re working through the requests as quickly as we can.

  3. monitoring Oct 20, 2025, 12:43 PM UTC

    We’re seeing steady recovery and keeping an eye on all components to make sure everything’s fully caught up. The upstream provider is still going through its own recovery process too.

  4. monitoring Oct 20, 2025, 12:46 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Oct 20, 2025, 02:15 PM UTC

    We’re no longer seeing any issues related to Postgres databases from this incident on our platform.

  6. monitoring Oct 20, 2025, 03:58 PM UTC

    We’re seeing some issues again with a few components. Database creation might be slow in Virginia or appears stuck during the creation process.

  7. identified Oct 20, 2025, 04:17 PM UTC

    Requests routed to Web Services have begun experiencing issues.

  8. identified Oct 20, 2025, 05:10 PM UTC

    The upstream provider has not yet recovered. We are still seeing request latency for Web Services and Static Sites in Virginia, and some users are unable to create new databases or backups.

  9. identified Oct 20, 2025, 05:54 PM UTC

    Web Services (paid and free) and Static Site request latencies have returned to normal levels. Issues involving PostgreSQL database creation and inability to create backups persist.

  10. monitoring Oct 20, 2025, 09:10 PM UTC

    All Render services have recovered, our upstream provider is continuing to recover. We are continuing to monitor impact.

  11. resolved Oct 20, 2025, 11:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 10, 2025 Incorrect IP allowlists configured for new Environments created via REST API 1h 43m Render REST API

Started Oct 10, 2025, 07:34 PM UTC· resolved Oct 10, 2025, 09:17 PM UTC

  1. identified Oct 10, 2025, 07:34 PM UTC

    We have identified and are working to fix Environments recently created via the REST API to ensure default IP allowlists are configured correctly. Until then, new Services created in these Environments may be responding to requests with unexpected errors.

  2. resolved Oct 10, 2025, 09:17 PM UTC

    Changes were deployed to fix the issue with new Environments created via the REST API. All affected Environments have been updated to be their default Allow-All if not otherwise specified in the API call's parameters. This issue has been resolved.

Read the full incident report →