Disruption with Login and Release Asset downloads
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- major
- Provider record created
- 12 Aug 2026, 21:39:05 UTC
- Provider record updated
- 25 Aug 2026, 19:58:06 UTC
- Explicit provider start
- 12 Aug 2026, 21:39:05 UTC
- Explicit provider end
- 12 Aug 2026, 22:56:39 UTC
Affected components reported by the provider
The provider explicitly listed no affected components in this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- resolved
On August 12 and 13, 2026, some anonymous (logged-out) requests to github.com experienced HTTP 5xx errors when loading pages like the sign-in page, and when downloading release assets, due to an unusual traffic pattern that repeatedly overloaded a part of our infrastructure that serves these types of requests. There were three windows of impact: (1) August 12 from 16:34 to 18:34 UTC, with an average error rate of 16.16% that peaked at 28.6%; (2) August 12 from 19:00 to 22:56 UTC, with an average error rate of 16.55% that peaked at 24.18%; and (3) August 13 from 06:19 to 08:05 UTC, with an average error rate of 2.01% that peaked at 7.49%.<br />Requests from signed-in users were unaffected.<br /><br />We mitigated the incidents by applying traffic controls at our network edge that limited any requests matching the pattern identified previously, thereby preventing overload on our systems.<br /><br />Since these incidents occurred, we have tightened our monitoring systems to alert server-side errors that affect logged-out traffic. We are also working to further strengthen our edge protections and reduce the time to detect and mitigate similar incidents.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We have identified the root cause and are working on mitigation. Errors on the login page and downloading release assets have decreased, but we are not fully mitigated. We will continue to provide updates.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating issues with Login and when downloading Release Assets. We will continue to keep users updated on progress towards mitigation.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of impacted performance for some GitHub services.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC