Render

We've continued to observe no further issues and deploy failure reasons have been 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 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.

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 are continuing to investigate this issue.

We are continuing to investigate this issue.

Requests through the dashboard may be slower than usual. We're currently investigating the issue.

This incident has now been resolved.

We believe the issue was caused by an upstream provider. We're continuing to monitor the situation.

We've observed recovery across all services and are now monitoring the situation.

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.

Builds failure rates have recovered. Resolving.

We are now seeing a recovery in our build failure rate. We are continuing to monitor the 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 currently investigating this issue.

This incident has been resolved.

Deployments have been consistently completing since approximately 08:40, and are returning to normal levels. We are monitoring for any other impacts.

We are continuing to work towards mitigating this issue, while also working with GitHub to resolve these deployment failures.

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.

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.

We have received an elevated number of reports about git clone failures resulting in a 403 error, aborting the deployment. We are investigating.

This incident has been resolved.

GitHub reports that they have mitigated their incident and are monitoring to ensure stability.

GitHub has updated its status page to report degraded REST API availability: https://www.githubstatus.com/incidents/gxycch3076xk

We are continuing to investigate this issue.

We are currently investigating this issue.