← Back to Render History
critical✓ Resolved
GitHub git clone 403 errors
Status
resolved
Duration
5h 41m
Updates
5
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedSun, Jul 19, 2026, 09:25 AM
This incident has been resolved.
monitoringSun, Jul 19, 2026, 09:10 AM
Deployments have been consistently completing since approximately 08:40, and are returning to normal levels. We are monitoring for any other impacts.
identifiedSun, Jul 19, 2026, 08:29 AM
We are continuing to work towards mitigating this issue, while also working with GitHub to resolve these deployment failures.
identifiedSun, Jul 19, 2026, 05:57 AM
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.
identifiedSun, Jul 19, 2026, 03:55 AM
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.
investigatingSun, Jul 19, 2026, 03:44 AM
We have received an elevated number of reports about git clone failures resulting in a 403 error, aborting the deployment. We are investigating.
📊 TECHNICAL DETAILS
Internal ID
df48b3e5-6f05-4cdc-9c0a-dd10830a8db6
External ID
wtznflqd1jsp
🕐 Started
Sun, Jul 19, 2026, 03:44 AM
🔄 Last Updated
Sun, Jul 19, 2026, 09:25 AM
✓ Resolved
Sun, Jul 19, 2026, 09:25 AM
CRITICAL
Impact Level
5h 41m
Total Duration
5
Status Updates
Affected Components
Builds and Deploys
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed