Render Outage History
Render is up right nowPingoru has recorded 82 incidents for Render: 79 in the last 12 months and 15 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 8 | 16 of 720 (2%) |
| May 2026 | 6 | 4 of 744 (1%) |
| June 2026 | 10 | 12 of 720 (2%) |
| July 2026 | 9 | 43 of 744 (6%) |
| August 2026 | 3 | 6 of 744 (1%) |
| September 2026 | 5 | 2 of 720 (0%) |
| October 2026 | 6 | 11 of 583 (2%) |
Incidents, newest first
Major March 3, 2026 Ohio Services with Disks, Data Persistence failing 19m Web Services, Background Workers, PostgreSQL, Redis
Started Mar 03, 2026, 12:41 AM UTC· resolved Mar 03, 2026, 01:00 AM UTC
- identified Mar 03, 2026, 12:41 AM 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.
- identified Mar 03, 2026, 12:59 AM UTC
Many services have recovered with healthy disks on new hosts, however this issue remains open as some services are still impaired.
- resolved Mar 03, 2026, 01:00 AM UTC
All affected services have been migrated to new hosts and are running at this time. This incident has been resolved.
Major February 11, 2026 Some deploys may be slow or hanging 3h 8m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Feb 11, 2026, 04:16 PM UTC· resolved Feb 11, 2026, 07:25 PM UTC
- investigating Feb 11, 2026, 04:16 PM UTC
We are currently investigating this issue.
- monitoring Feb 11, 2026, 04:39 PM UTC
We have implemented a mitigation and are currently observing positive results. We are continuing to monitor deploy health across the platform.
- identified Feb 11, 2026, 06:24 PM UTC
Deploy delays and failures continue to remain elevated. We are continuing to work on this issue.
- monitoring Feb 11, 2026, 07:15 PM UTC
Deploy times have decreased and failures have dropped to baseline levels. We are monitoring for other impacts or other issues.
- resolved Feb 11, 2026, 07:25 PM UTC
This incident has been resolved.
Major February 4, 2026 Elevated latency for some new services when using the onrender.com address 1h 29m Web Services, Web Services, Web Services, Web Services and 7 more
Started Feb 04, 2026, 05:13 PM UTC· resolved Feb 04, 2026, 06:42 PM UTC
- investigating Feb 04, 2026, 05:13 PM UTC
We are currently investigating this issue.
- identified Feb 04, 2026, 05:21 PM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 04, 2026, 05:29 PM 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.
- resolved Feb 04, 2026, 06:42 PM 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.
Minor February 3, 2026 Degraded deploys in Ohio and Virginia 2d 7h Builds and Deploys, Builds and Deploys
Started Feb 03, 2026, 03:30 PM UTC· resolved Feb 05, 2026, 10:36 PM UTC
- investigating Feb 03, 2026, 11:05 PM UTC
Deploys are experiencing degraded performance and may take longer to complete.
- monitoring Feb 03, 2026, 11:58 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Feb 04, 2026, 07:04 PM UTC
We are observing improved deploy performance and continue to monitor for any further issues.
- monitoring Feb 04, 2026, 09:34 PM UTC
We are continuing to monitor for any further issues.
- resolved Feb 05, 2026, 10:36 PM UTC
We implemented updates to builds and deploys to improve handling of slow updates. As a result of these changes, build and deploy performance has recovered.
Minor February 3, 2026 Degraded Deploys in Singapore Region 36m Builds and Deploys
Started Feb 03, 2026, 10:32 AM UTC· resolved Feb 03, 2026, 11:09 AM UTC
- investigating Feb 03, 2026, 10:32 AM UTC
We are currently investigating this issue.
- monitoring Feb 03, 2026, 10:49 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 03, 2026, 11:09 AM UTC
This incident has been resolved.
Minor February 2, 2026 Degraded deploys in all regions 49m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Feb 02, 2026, 10:04 PM UTC· resolved Feb 02, 2026, 10:54 PM UTC
- investigating Feb 02, 2026, 10:04 PM UTC
We are currently investigating this issue.
- monitoring Feb 02, 2026, 10:40 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 02, 2026, 10:54 PM UTC
This incident has been resolved.
Major January 30, 2026 External connectivity issues with Postgres databases hosted in Singapore 57m PostgreSQL
Started Jan 30, 2026, 11:28 AM UTC· resolved Jan 30, 2026, 12:25 PM UTC
- investigating Jan 30, 2026, 11:28 AM UTC
We are currently investigating this issue.
- identified Jan 30, 2026, 12:09 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 30, 2026, 12:20 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 30, 2026, 12:25 PM UTC
This incident has been resolved. Please reach out to [email protected] for any follow-up questions.
Minor January 23, 2026 Metrics impacted for some services in Oregon 56m Metrics/Logs
Started Jan 23, 2026, 12:49 AM UTC· resolved Jan 23, 2026, 01:46 AM UTC
- investigating Jan 23, 2026, 01:12 AM UTC
Metrics for some services in Oregon are currently impacted and may not be displaying.
- identified Jan 23, 2026, 01:16 AM UTC
The issue has been identified and a remediation is being implemented
- monitoring Jan 23, 2026, 01:30 AM UTC
Metrics for impacted services in Oregon are now being displayed. Metrics will be missing from impacted services from 2026-01-23 00:50 to 2026-01-23 01:10 UTC
- resolved Jan 23, 2026, 01:46 AM UTC
This incident has been resolved.
Minor January 17, 2026 Delays in starting instances on services 12m Web Services, Cron Jobs, Background Workers, PostgreSQL and 2 more
Started Jan 17, 2026, 02:29 AM UTC· resolved Jan 17, 2026, 02:41 AM UTC
- identified Jan 17, 2026, 02:29 AM UTC
High demand for new instances has created a backlog for some services in the Oregon region. Services attempting to add new instances including those for new deploys, instance scale ups, restarts, etc. may see delays doing so.
- resolved Jan 17, 2026, 02:41 AM UTC
Instance creation times have been restored to expected timerames. This issue has been resolved.
Minor January 12, 2026 Some application and build logs are missing on the dashboard 5h 11m Metrics/Logs, Metrics/Logs, Metrics/Logs, Metrics/Logs and 1 more
Started Jan 12, 2026, 02:45 PM UTC· resolved Jan 12, 2026, 07:56 PM UTC
- investigating Jan 12, 2026, 02:45 PM UTC
Some logs, especially build and application logs, may be temporarily missing. We’re actively investigating this and will work to fix it as soon as possible. Builds can still complete successfully even if the logs aren’t showing up.
- investigating Jan 12, 2026, 03:31 PM UTC
We believe we’ve identified the root cause of the issue, and we’re currently doing some additional investigation to make sure it’s resolved properly.
- identified Jan 12, 2026, 05:16 PM UTC
We’ve identified the issue and are now in recovery. Recovery may be slow due to the large volume of logs involved.
- monitoring Jan 12, 2026, 06:04 PM UTC
We’re seeing steady recovery now, and logs should be showing again. We are still monitoring to confirm the longer-term recovery.
- resolved Jan 12, 2026, 07:56 PM UTC
This incident has been resolved.
Minor January 8, 2026 Deploy delays in Oregon 2h 1m Builds and Deploys
Started Jan 08, 2026, 04:47 PM UTC· resolved Jan 08, 2026, 06:48 PM UTC
- investigating Jan 08, 2026, 04:47 PM UTC
Some users may experience slower build times for services deployed in Oregon.
- monitoring Jan 08, 2026, 06:26 PM UTC
We have implemented a fix and are monitoring for further issues.
- resolved Jan 08, 2026, 06:48 PM UTC
This incident has been resolved.
Major December 10, 2025 Unable to view service events 6m Render Dashboard
Started Dec 10, 2025, 09:50 PM UTC· resolved Dec 10, 2025, 09:57 PM UTC
- investigating Dec 10, 2025, 09:50 PM UTC
When viewing service events, an error is returned. We are currently investigating the issue.
- resolved Dec 10, 2025, 09:57 PM UTC
This incident has been resolved.
Minor December 10, 2025 Deploy delays in Virginia 1d 3h Builds and Deploys
Started Dec 10, 2025, 08:58 PM UTC· resolved Dec 12, 2025, 12:05 AM UTC
- investigating Dec 10, 2025, 08:58 PM UTC
We are currently investigating this issue.
- monitoring Dec 10, 2025, 10:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 12, 2025, 12:05 AM UTC
Deploy performance has returned to expected levels.
Minor December 5, 2025 Elevated Latency for Requests to Web Services and Static Sites in Frankfurt 49m Web Services, Static Sites
Started Dec 05, 2025, 11:03 PM UTC· resolved Dec 05, 2025, 11:52 PM UTC
- investigating Dec 05, 2025, 11:03 PM UTC
We are currently investigating this issue.
- investigating Dec 05, 2025, 11:19 PM UTC
Latency has normalized. We continue to investigate with our upstream vendor to identify the cause.
- monitoring Dec 05, 2025, 11:29 PM UTC
Latency has remained stable. We continue to monitor the situation.
- resolved Dec 05, 2025, 11:52 PM UTC
This incident has been resolved.
Major December 5, 2025 Services not accessible 35m Render Dashboard, Render Website, Render Platform API, Render REST API and 1 more
Started Dec 05, 2025, 09:01 AM UTC· resolved Dec 05, 2025, 09:36 AM UTC
- investigating Dec 05, 2025, 09:01 AM UTC
We're investigating services not being accessible
- identified Dec 05, 2025, 09:07 AM UTC
We're experiencing issues with an upstream provider.
- monitoring Dec 05, 2025, 09:20 AM UTC
Access to services is now recovering, and we are continuing to monitor.
- monitoring Dec 05, 2025, 09:20 AM UTC
The upstream provider is recovering, and we’re seeing recovery on our side too.
- resolved Dec 05, 2025, 09:36 AM UTC
From 08:47 to 09:11 UTC, all incoming web traffic in every region failed to reach services and returned 500 errors instead. Our dashboard and API were down too. Background workers, private services, and cron jobs were not affected. The upstream provider has recovered now, and we’re no longer seeing any issues on our side.
Minor December 2, 2025 Increased Latency in Updates to Oregon Services 1h 37m Web Services, Static Sites, Web Services - Free Tier
Started Dec 02, 2025, 08:48 PM UTC· resolved Dec 02, 2025, 10:26 PM UTC
- investigating Dec 02, 2025, 09:08 PM UTC
Creation of services or changes to existing services hosted in our Oregon region are experiencing increased latency. We are currently investigating.
- monitoring Dec 02, 2025, 09:12 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 02, 2025, 10:26 PM UTC
This incident has been resolved.
Minor December 2, 2025 Custom Domains: New certificates stuck on pending 1h 27m Custom Domains
Started Dec 02, 2025, 02:32 PM UTC· resolved Dec 02, 2025, 04:00 PM UTC
- investigating Dec 02, 2025, 02:32 PM UTC
You may see certificates stuck on 'Pending' after adding a custom domain. We’ve located an issue with a provider and are looking into it right now.
- identified Dec 02, 2025, 03:30 PM UTC
The provider is actively working on the issue and we’re seeing some progress on certificate issuance. We’re still waiting on full confirmation that the fix is complete.
- resolved Dec 02, 2025, 04:00 PM UTC
We understand the issue is resolved now. If you're still seeing issues, please reach out.
Major November 25, 2025 Web services (Oregon) and static sites availability disruption 13m Web Services, Static Sites, Web Services - Free Tier
Started Nov 25, 2025, 08:13 PM UTC· resolved Nov 25, 2025, 08:26 PM UTC
- investigating Nov 25, 2025, 08:13 PM UTC
We are currently investigating an issue impacting web service and static site availability.
- monitoring Nov 25, 2025, 08:26 PM UTC
A fix has been implemented and we are monitoring the results. Impact resulted in intermittent latency, timeouts, and errors for some services for ~6 minutes (11:46-11:52 PST).
- resolved Nov 25, 2025, 08:26 PM UTC
This incident has been resolved.
Minor November 20, 2025 Increased slowness in Dashboard 7h 29m Render Dashboard
Started Nov 20, 2025, 05:53 PM UTC· resolved Nov 21, 2025, 01:23 AM UTC
- investigating Nov 20, 2025, 05:53 PM UTC
We are currently investigating this issue.
- investigating Nov 20, 2025, 06:29 PM UTC
Dashboard performance has recovered. We are continuing to investigate the root cause.
- monitoring Nov 20, 2025, 08:23 PM UTC
Dashboard performance remains healthy and we continue to monitor.
- resolved Nov 21, 2025, 01:23 AM UTC
The incident has been resolved.
Major November 20, 2025 Elevated rates of deploy failures 2h 3m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Nov 20, 2025, 05:28 PM UTC· resolved Nov 20, 2025, 07:31 PM UTC
- investigating Nov 20, 2025, 05:28 PM UTC
We are currently investigating this issue.
- investigating Nov 20, 2025, 06:21 PM UTC
We are continuing to investigate this issue.
- identified Nov 20, 2025, 06:52 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Nov 20, 2025, 07:31 PM UTC
This incident has been resolved.
Major November 18, 2025 GitHub-backed services failing to build in all regions 56m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Nov 18, 2025, 09:00 PM UTC· resolved Nov 18, 2025, 09:56 PM UTC
- investigating Nov 18, 2025, 09:00 PM UTC
We are currently investigating this issue.
- identified Nov 18, 2025, 09:09 PM UTC
An upstream provider is experiencing an outage. We are monitoring the situation.
- monitoring Nov 18, 2025, 09:39 PM UTC
The upstream provider has implemented a fix and recovery is ongoing. We are continuing to monitor the situation.
- resolved Nov 18, 2025, 09:56 PM UTC
This incident has been resolved.
Major November 18, 2025 An upstream provider major incident is affecting some Render services 6h 26m Web Services, Web Services, Web Services, Web Services and 1 more
Started Nov 18, 2025, 12:10 PM UTC· resolved Nov 18, 2025, 06:37 PM UTC
- investigating Nov 18, 2025, 12:10 PM UTC
We’re aware of a major incident with an upstream provider that’s impacting some services on Render. You might see some 500s until it’s resolved upstream. We’re also investigating on our side.
- identified Nov 18, 2025, 01:57 PM UTC
The upstream provider is still suffering from the incident, and we are still waiting for further mitigations from them.
- monitoring Nov 18, 2025, 03:02 PM UTC
The upstream provider has resolved the issue. We’re still checking to see if there’s any remaining impact on our side.
- resolved Nov 18, 2025, 06:37 PM UTC
We have observed no further impact and the upstream provider has affirmed full resolution.
Minor November 14, 2025 Metrics/Logs missing for Oregon services 23m Metrics/Logs
Started Nov 14, 2025, 08:55 PM UTC· resolved Nov 14, 2025, 09:18 PM UTC
- identified Nov 14, 2025, 08:55 PM UTC
Metrics and Logs for services hosted in Oregon are missing due to a platform incident. We are working to resolve this issue now.
- resolved Nov 14, 2025, 09:18 PM UTC
This incident has been resolved.
Minor November 13, 2025 Cron Job runs cannot be cancelled from our dashboard or the API 7h 20m Cron Jobs, Cron Jobs, Cron Jobs, Cron Jobs and 1 more
Started Nov 13, 2025, 03:40 PM UTC· resolved Nov 13, 2025, 11:00 PM UTC
- investigating Nov 13, 2025, 03:40 PM UTC
We’re looking into why this is happening. The cancel button on a run doesn’t actually stop it right now. The current workaround is to suspend and then unsuspend the cron to force-cancel the run. If that doesn’t do the trick, please reach out to our support team.
- resolved Nov 13, 2025, 11:00 PM UTC
This incident has been resolved.
Major November 5, 2025 Increased 404s in Oregon (Web Services) and Static Sites 2h 33m Web Services, Static Sites
Started Nov 05, 2025, 07:19 PM UTC· resolved Nov 05, 2025, 09:52 PM UTC
- investigating Nov 05, 2025, 07:19 PM UTC
We are currently investigating the issue.
- identified Nov 05, 2025, 07:24 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Nov 05, 2025, 07:58 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Nov 05, 2025, 08:08 PM UTC
We have identified continuing issues in Oregon. A fix is being worked on.
- identified Nov 05, 2025, 08:21 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Nov 05, 2025, 08:48 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Nov 05, 2025, 09:03 PM UTC
We are continuing to monitor for any further issues.
- resolved Nov 05, 2025, 09:52 PM UTC
This incident has been resolved.
- postmortem Nov 18, 2025, 06:48 PM UTC
# Summary As an infrastructure provider, providing a reliable platform that allows our customers to build and scale their applications with confidence is our highest obligation. We invest heavily to ensure our platform is highly reliable and secure, including in our routing layer that handles billions of HTTP requests every day. On November 5, 2025, we inadvertently rolled back a performance improvement that was gated behind a feature flag. This led to disruption in the form of intermittent 404s for some web services and static sites deployed to the Oregon region. We have fully identified the sequence of events that led to this outage and are in the process of taking steps to prevent it from recurring. # Impact There were two periods where some customers hosting web services and static sites in the Oregon region experienced a partial outage with intermittent 404s. The first period occurred between 10:39 AM PST and 11:25 AM PST . At this time, two Render clusters had slightly degraded service. One cluster returned a negligible number of 404 responses, and the other cluster returned 404 responses for approximately 10% of requests. The second period occurred between 11:59 AM PST to 12:34 AM PST and saw more significant service degradation. During this period, about 50% of all requests to services in the affected cluster received a 404 response. All newly created services in these clusters were affected and received 404 responses during the incident. Updates to existing services were also slow to propagate. Free tier services that were recently deployed or waking from sleep were also affected. # Root Cause Render's routing service depends on a metadata service to receive information about the user services it routes traffic to. When the routing service first starts and upon occasional reconnection, it will request and receive a large volume of data from the metadata service. Earlier in 2025, we successfully deployed a memory optimization related to data transfer between the metadata and routing services using a feature flag. In late October, we removed the flag from code and redeployed, but we didn't redeploy the metadata service, which still depended on the flag. On November 5th, we cleaned up unreferenced feature flags from our system. This caused the metadata service to revert to its less efficient data transfer method, leading to memory exhaustion and crashes. Our routing service is designed to handle metadata service outages and continue serving traffic based on its last known state. However, newly created instances that could not load their initial state were incorrectly sent requests, resulting in 404 errors. During the first period of impact, the metadata service was crashing in two of our clusters, and only a small fraction of routing service instances were impacted. During the second period of impact, we saw a large increase in HTTP requests for services in the affected cluster. This triggered scale-ups of the routing service, all of which returned 404 errors. # Mitigations ## Completed * Increased memory available to the metadata service \(this has since been reverted\) * Temporarily re-enabled the feature flag to support more efficient data transfer between the routing and metadata services \(this has since been removed\) * Deployed the metadata service to no longer rely on the feature flag * Enhanced our monitoring of the metadata service to alert us of this particular failure mode ## Planned * Improve our feature flag hygiene practice to prevent the removal of a feature flag while it is still being evaluated * Prevent the routing service from receiving traffic if it never successfully loaded state from the metadata service