Increased 404s in Oregon (Web Services) and Static Sites
Affected: Web ServicesStatic Sites
Render Outage History
Render is up right nowRender had 64 outages in the last 2 years totaling 97h 12m of downtime — averaging 2.6 incidents per month.
There were 64 Render outages since September 17, 2025 totaling 97h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.
Failure to spin free web services back up after inactivity
Timeline · 1 update
- 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.
Degraded builds and deploys in Virginia
Affected: Builds and Deploys
Timeline · 3 updates
- investigating Oct 28, 2025, 05:08 PM UTC
Builds and deploys may be slower than usual. We are currently investigating this issue.
- 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.
- resolved Oct 28, 2025, 05:59 PM UTC
This incident has been resolved.
Pre-deploys are failing in some regions
Affected: Web ServicesBuilds and Deploys
Timeline · 6 updates
- investigating Oct 23, 2025, 04:27 PM UTC
We are currently investigating this issue.
- 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.
- investigating Oct 23, 2025, 04:47 PM UTC
Some pre-deploys in Singapore are also affected.
- identified Oct 23, 2025, 04:56 PM UTC
We’ve found the root cause and are rolling out a fix.
- 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.
- resolved Oct 23, 2025, 06:15 PM UTC
This incident has been resolved.
An upstream provider is experiencing some issues that are affecting parts of our platform (Virginia)
Affected: Web ServicesCron JobsBackground WorkersBuilds and DeploysPostgreSQLRedisWeb Services - Free TierAutoscalingMetrics/Logs
Timeline · 11 updates
Incorrect IP allowlists configured for new Environments created via REST API
Affected: Render REST API
Timeline · 2 updates
- 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.
- 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.
Increased latency in Oregon region
Affected: Render DashboardWeb ServicesRender WebsiteRender Platform APIRender REST APIStatic SitesWeb Services - Free Tier
Timeline · 3 updates
- investigating Oct 07, 2025, 04:57 PM UTC
We are currently investigating increased latency in our Oregon region
- monitoring Oct 07, 2025, 05:06 PM UTC
Peak impact occurred between 16:20 and 16:40 UTC. We are currently monitoring.
- resolved Oct 07, 2025, 05:38 PM UTC
Latency has returned to baseline levels since 16:40 UTC and no further impact has been observed.
Unable to create Postgres services or update their instance type in Oregon
Affected: PostgreSQL
Timeline · 3 updates
- investigating Oct 01, 2025, 08:15 PM UTC
We are currently investigating this issue.
- monitoring Oct 01, 2025, 08:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 01, 2025, 10:42 PM UTC
This incident has now been resolved. A subset of customers in Oregon, but not all, were impacted. Affected customers were unable to create Postgres services or update the instance type of Postgres services between 19:14 and 20:15 UTC.
Partial degradation of service creation and deploys in Oregon
Affected: Builds and Deploys
Timeline · 3 updates
- investigating Oct 01, 2025, 02:08 PM UTC
We are currently investigating this issue.
- monitoring Oct 01, 2025, 02:24 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 01, 2025, 02:57 PM UTC
This incident has been resolved.
Image-based deploys failing due to upstream provider
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 3 updates
- identified Sep 25, 2025, 12:02 AM UTC
Due to an outage from an upstream provider, users with image-based services are seeing failed deploys with reports of 401 errors.
- monitoring Sep 25, 2025, 01:14 AM UTC
The upstream provider has rolled out a fix and are monitoring the issue. We are monitoring our systems as well.
- resolved Sep 25, 2025, 01:31 AM UTC
This incident has been resolved.
Dashboard operations degraded or failing
Timeline · 1 update
- resolved Sep 23, 2025, 08:57 PM UTC
Dashboard operations were degraded for ~30 minutes, and within that period operations were mostly failing for ~5 mins.
Small number of users impacted by stuck builds
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 4 updates
- investigating Sep 23, 2025, 06:30 PM UTC
We are aware of an issue resulting in stuck builds impacting a small minority of users with the "Wait" setting for their Overlapping Deploy Policy.
- identified Sep 24, 2025, 10:41 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 25, 2025, 11:43 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 26, 2025, 06:19 PM UTC
This incident has been resolved.
Some Postgres databases can’t be created in Frankfurt
Affected: PostgreSQL
Timeline · 4 updates
- investigating Sep 22, 2025, 02:31 PM UTC
This doesn’t impact Postgres databases that are already running. It only partially affects Frankfurt. Any affected database that gets created will show a status of 'unknown'.
- identified Sep 22, 2025, 03:13 PM UTC
We’ve identified the issue, but we’re still investigating.
- identified Sep 22, 2025, 03:40 PM UTC
We are continuing to work on the issue.
- resolved Sep 22, 2025, 05:49 PM UTC
This incident has been resolved.
Issues with deploys and spinning down free services in Virginia
Timeline · 1 update
- resolved Sep 17, 2025, 09:43 PM UTC
Between 20:35 UTC and 20:53 UTC today, a process was unavailable that is responsible for handling port detection and deploys that were waiting due to a workspace's overlapping deploy policy. Queued deploys will proceed as expected in most cases. Additionally, free services may not have spun down on idle during that period.