65 recorded Render incidents since November 2025, with official updates, affected components, duration and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some web services in Oregon were unavailable between 19:20 and 19:30 UTC.
We are investigating service instability affecting some web services in our Singapore region. Customers may experience unexpected service restarts or intermittent availability. Our team is actively investigating and working to restore normal operation. We will provide an update as more information becomes available.
We've observed that deploys are primarily affected by this.
Inbound traffic to Singapore services is impacted. Free service spin-ups (from idle) in Singapore have been temporarily disabled while we continue to investigate.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
An issue has been identified with our upstream provider, Google Cloud. Free Web Services: Builds/deploys and spin-up have been temporarily disabled while we work to mitigate the issue.
We are observing recovery for builds and deploys in all regions. Builds, deploys, and spin-up for free web services have been re-enabled. Some customers may continue to see elevated latency while recovery progresses. We are continuing to monitor.
We have observed full recovery. We are continuing to monitor for any further issues.
This incident has been resolved.
Requests through the dashboard may be slower than usual. We're currently investigating the issue.
We are continuing to investigate this issue.
The REST API is also experiencing degraded performance. As a result, requests to it may experience timeouts and you may need to retry your request. We are continuing to investigate.
We've implemented a fix and are monitoring the results. Deploy failure reasons will be temporarily unavailable. Deploy failure events will still be generated. We will provide an update once deploy failure reasons are re-enabled.
No further issues have been observed since our fixes. The Dashboard and REST API remain fully operational. Deploy failure reasons are still disabled. We will update this incident once they are re-enabled. There are no further updates expected for today (2026-07-27, UTC-7).
We've continued to observe no further issues and deploy failure reasons have been re-enabled.
We are investigating an infrastructure issue affecting services hosted in our Oregon region. Some services may be unreachable or experience failed requests. Our engineering team is actively working to identify the cause and restore normal operation.
We've observed recovery across all services and are now monitoring the situation.
We believe the issue was caused by an upstream provider. We're continuing to monitor the situation.
This incident has now been resolved.
We are currently investigating this issue.
GitHub continues to report an outage, https://www.githubstatus.com. This is causing authentication failures when trying to deploy from a GitHub repository.
We are now seeing a recovery in our build failure rate. We are continuing to monitor the issue.
Builds failure rates have recovered. Resolving.
We have received an elevated number of reports about git clone failures resulting in a 403 error, aborting the deployment. We are investigating.
Services failing to deploy are those deployed in Frankfurt. Running services are not affected, only the deploy process is failing. We are still working to determine the cause of this error for those services.
Users with services hosted in Frankfurt that rely on GitHub repositories for deployments continue to see 403 errors in their logs causing the deployment to fail. We are continuing to work on this issue within our own systems and have reached out to GitHub.
We are continuing to work towards mitigating this issue, while also working with GitHub to resolve these deployment failures.
Deployments have been consistently completing since approximately 08:40, and are returning to normal levels. We are monitoring for any other impacts.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
GitHub has updated its status page to report degraded REST API availability: https://www.githubstatus.com/incidents/gxycch3076xk
GitHub reports that they have mitigated their incident and are monitoring to ensure stability.
This incident has been resolved.
Some users enrolled in 2FA report login loops when attempting to access the Render dashboard. We're investigating.
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.
We are currently investigating an issue with the availability of the Render Dashboard.
We have identified the root cause of this issue and have made a change to resolve it. Our dashboard is back online. We are now monitoring the issue to ensure it is fully resolved.
This issue has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to an ongoing LetsEncrypt incident, wildcard certificates may be slow to issue/renew. We are actively monitoring the situation.
Issuance has returned to expected performance and we've observed no further impact.
We are currently investigating this issue.
We have rolled out a fix for this issue and are now monitoring it before confirming the resolution.
We are continuing to monitor for any further issues.
This has now been resolved. Customers will have seen an impact from Jun 22, 2026, at 11:50 UTC.
We are seeing slow or failing issuance of wildcard certificates due to an ongoing incident with the LetsEncrypt certificate authority. We are actively monitoring the situation on our end.
We are no longer observing any impact from the LetsEncrypt incident. We continue to monitor.
We have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.
We are currently investigating the problem. Try this work-around to get deploys going again: * Go into Workspace Settings * Change the Overlapping Deploy Policy to "Override" * Initiate a new deploy (which will then cancel the stuck deploy) * Change the Deploy Policy back to "Wait"
A fix has been implemented and we are monitoring the results.
This incident has been resolved. If you still have a stuck queued deploy, follow the instructions below under "Investigating" to clear the queue. It should then work again as expected going forward.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The earlier "Platform latency" incident has affected queued deploys. We are implementing a fix
We are continuing to work on a fix for this issue. In the meantime, stuck deploys can be cleared with these steps: * Go into Workspace Settings * Change the Overlapping Deploy Policy to "Override" * Initiate a new deploy (which will then cancel the stuck deploy) * Change the Deploy Policy back to "Wait"
This incident has been resolved.
We are currently investigating delays across the platform affecting builds, deploys, and webhooks.
A fix has been implemented, and we are continuing to monitor. Auto-deploys would have been affected/missed by these delays and will need to be retriggered.
This incident has been resolved.
We are currently investigating this issue.
We're seeing evidence of recovery and are continuing to monitor the situation.
This incident has been resolved.