Custom domains are unable to be created
Timeline · 2 updates
- investigating Mar 09, 2026, 08:19 PM UTC
We are currently investigating this issue.
- resolved Mar 09, 2026, 08:39 PM UTC
This incident has been resolved.
Render had 64 outages in the last 2 years totaling 127h 45m of downtime — averaging 2.6 incidents per month.
There were 64 Render outages since September 17, 2025 totaling 127h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
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.
Many services have recovered with healthy disks on new hosts, however this issue remains open as some services are still impaired.
All affected services have been migrated to new hosts and are running at this time. This incident has been resolved.
We are currently investigating this issue.
We have implemented a mitigation and are currently observing positive results. We are continuing to monitor deploy health across the platform.
Deploy delays and failures continue to remain elevated. We are continuing to work on this issue.
Deploy times have decreased and failures have dropped to baseline levels. We are monitoring for other impacts or other issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
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.
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.
Deploys are experiencing degraded performance and may take longer to complete.
A fix has been implemented and we are monitoring the results.
We are observing improved deploy performance and continue to monitor for any further issues.
We are continuing to monitor for any further issues.
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.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Please reach out to [email protected] for any follow-up questions.
Metrics for some services in Oregon are currently impacted and may not be displaying.
The issue has been identified and a remediation is being implemented
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
This incident has been resolved.
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.
Instance creation times have been restored to expected timerames. This issue has been resolved.
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.
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.
We’ve identified the issue and are now in recovery. Recovery may be slow due to the large volume of logs involved.
We’re seeing steady recovery now, and logs should be showing again. We are still monitoring to confirm the longer-term recovery.
This incident has been resolved.
Some users may experience slower build times for services deployed in Oregon.
We have implemented a fix and are monitoring for further issues.
This incident has been resolved.
When viewing service events, an error is returned. We are currently investigating the issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
Deploy performance has returned to expected levels.
We are currently investigating this issue.
Latency has normalized. We continue to investigate with our upstream vendor to identify the cause.
Latency has remained stable. We continue to monitor the situation.
This incident has been resolved.
We're investigating services not being accessible
We're experiencing issues with an upstream provider.
Access to services is now recovering, and we are continuing to monitor.
The upstream provider is recovering, and we’re seeing recovery on our side too.
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.
Creation of services or changes to existing services hosted in our Oregon region are experiencing increased latency. We are currently investigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
We understand the issue is resolved now. If you're still seeing issues, please reach out.
We are currently investigating an issue impacting web service and static site availability.
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).
This incident has been resolved.
We are currently investigating this issue.
Dashboard performance has recovered. We are continuing to investigate the root cause.
Dashboard performance remains healthy and we continue to monitor.
The incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
An upstream provider is experiencing an outage. We are monitoring the situation.
The upstream provider has implemented a fix and recovery is ongoing. We are continuing to monitor the situation.
This incident has been resolved.
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.
The upstream provider is still suffering from the incident, and we are still waiting for further mitigations from them.
The upstream provider has resolved the issue. We’re still checking to see if there’s any remaining impact on our side.
We have observed no further impact and the upstream provider has affirmed full resolution.
Metrics and Logs for services hosted in Oregon are missing due to a platform incident. We are working to resolve this issue now.
This incident has been resolved.
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.
This incident has been resolved.