Is GitHub Down?

All Systems Operational

GitHub outage history and incident tracker. 126 incidents analyzed.

Reliability Score10.6
PoorUptime: 94.105%

Total Incidents

126

Uptime

94.105%

Avg Resolution

2h 9m

Top Cause

api

GitHub Outage Timeline

Outages by Year

Incident Severity

Recent GitHub Incidents

View all →

Copilot model Anthropic Fable experiencing elevated errors

GitHub·Copilot·Jul 30, 2026·1h 5m

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

api
low

Incident with Copilot AI Model Providers

GitHub·Copilot·Jul 29, 2026·1h 44m

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

api
low

Test Incident Posted in Error – No Customer Impact (Will Be Removed)

GitHub·Jul 27, 2026·6m

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

api
low

Incident with GraphQL API Requests

GitHub·API·Jul 27, 2026·16m

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

api
low

Actions run failures and delays

GitHub·Actions·Jul 25, 2026·42m

Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8

computeapi
critical

Several GPT models degraded

GitHub·Copilot·Jul 25, 2026·29m

On July 25, 2026, between 09:07 and 10:04 UTC, the GPT-5.2, GPT-5.3-Codex, GPT-5.4, GPT-5.4 Mini, GPT-5.6 Sol, GPT-5.6 Terra and GPT-5.6 Luna models experienced degraded availability in GitHub Copilot products and IDE surfaces. Requests to these models had an average failure rate of 5.6%. Other Copilot models remained available as alternatives.<br /><br />The degradation was caused by an issue with an upstream model provider. Success rates returned to normal after the upstream issue was mitigate

api
high

Incident With Blocked GitHub.com Traffic

GitHub·Jul 24, 2026·-297m

Between July 23, 2026 at 18:45 UTC and July 24, 2026 at 11:19 UTC, an abuse mitigation update caused some legitimate customers whose traffic was routed through our Central Europe and South America edge locations to be incorrectly blocked from GitHub.com. We estimate that approximately 0.25% of GitHub.com requests were affected during this period. This was caused by an abuse mitigation configuration that incorrectly classified legitimate traffic. We mitigated the incident by reverting the update

configurationcdnrouting
low

Latency issues across a number of services

GitHub·Actions·Jul 23, 2026·1h 45m

On July 23, 2026, between 07:08 and 09:39 UTC, several services experienced delays: 8% of actions workflow runs experienced an average run start delay of 10 minutes, 5% of webhook deliveries exceeded SLO, and code scanning, repos, notifications, issues and pull requests experienced increased latency over the life of the incident. <br /><br />The root cause of the incident was a node of our background job processing system which did not recover after entering scheduled host maintenance. The i

apicapacity
high

Disruption with actions hosted runners

GitHub·Actions·Jul 22, 2026·1h 26m

On July 22, 2026, between 19:36 UTC and 22:04 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 15% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 1% failed to start.<br /><br />At 21:49 UTC, we restored th

api
low

Some SSH connections using deploy keys are failing

GitHub·Jul 21, 2026·1h 25m

On July 21, 2026, between 07:41 UTC and 11:57 UTC, the SSH Authentication service was degraded and some SSH connections failed to authenticate. On average, 12.2% of SSH authentication requests failed, peaking at 15.7%. Both user RSA keys and deploy keys were impacted. This was due to a change in how our SSH service handled one public-key authentication method that caused the affected authentication attempts to be rejected as invalid. <br /><br />We mitigated the incident by reverting the change,

dnsauthenticationdeployment
critical

Incident Severity Distribution

critical
15 (12%)
high
18 (14%)
low
93 (74%)

Frequently Asked Questions

Is GitHub down right now?
Check the real-time status at the top of this page. IncidentHub-Bay monitors GitHub's services every 5 minutes and shows current operational status, active incidents, and historical outage data.
How often does GitHub have outages?
IncidentHub-Bay has tracked 126 incidents for GitHub across its monitoring period. This includes outages, service degradations, and performance issues of varying severity levels.
What is GitHub's uptime percentage?
Based on tracked incidents and their durations, GitHub's calculated uptime is 94.105%. The reliability score is 10.6/100 (Poor), which factors in incident severity, frequency, resolution time, and recent trends.
What are the most common causes of GitHub outages?
The most frequently tagged causes of GitHub incidents are: api, deployment, capacity. These are automatically categorized based on incident reports and status page updates.
How long do GitHub outages typically last?
The average resolution time for GitHub incidents is approximately 2 hours and 9 minutes. This includes time from initial detection to full resolution.
How does GitHub's reliability compare to other cloud providers?
GitHub has a reliability score of 10.6/100 (Poor). Visit our Reliability Rankings page to see how GitHub compares to other AI and cloud providers like OpenAI, Anthropic, AWS, and Google AI.

Related Resources

Get Notified When GitHub Goes Down

Subscribe to outage alerts via webhook or Slack and be the first to know about GitHub incidents.

Set Up Alerts