GitHub Service Outage: Git Operations Failed Due to Expired TLS Certificate
By
wilhelmklopp
A respectable bake. You'd come back tomorrow for another.
Summary
GitHub experienced a service outage from November 18, 2025, 20:30 UTC to 21:34 UTC affecting all Git operations including SSH and HTTP client interactions, as well as raw file access. The incident also impacted products relying on Git operations. The root cause was an expired TLS certificate used for internal service-to-service communication. The issue was resolved by replacing the expired certificate and restarting impacted services, leading to full recovery.
Key quotes
· 4 pulledFrom Nov 18, 2025 20:30 UTC to Nov 18, 2025 21:34 UTC we experienced failures on all Git operations, including both SSH and HTTP Git client interactions, as well as raw file access.
The root cause was an expired TLS certificate used for internal service-to-service communication.
We mitigated the incident by replacing the expired certificate and restarting impacted services.
Once those services were restarted we saw a full recovery.
You might also wanna read
GitHub Actions suffers three-hour outage with false 'account suspended' error
GitHub Actions experienced a major outage lasting over three hours, during which users saw an alarming but incorrect error message stating "
GitHub Implements Post-Quantum Secure SSH Key Exchange for Enhanced Git Data Protection
GitHub is introducing post-quantum secure SSH key exchange algorithms (sntrup761x25519-sha512) to enhance security for Git data access. This
