GitHub git clone 403 errors

What to do

• Check whether you use Render Builds and Deploys in eu. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 5h 36m it lasted.

  Anything that failed between 2026-07-19 03:44 UTC and 2026-07-19 09:20 UTC may need a replay.

• Subscribe to Render's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=render works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Render 6

1. investigatingJul 19, 2026, 3:44 AM UTC

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

   provider

2. identifiedJul 19, 2026, 3:55 AM UTC

   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.

   provider

3. identifiedJul 19, 2026, 5:57 AM UTC

   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.

   provider

4. identifiedJul 19, 2026, 8:29 AM UTC

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

   provider

5. monitoringJul 19, 2026, 9:10 AM UTC

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

   provider

6. resolvedJul 19, 2026, 9:20 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.