Is GitHub Down?

All Systems Operational

GitHub outage history and incident tracker. 38 incidents analyzed.

Reliability Score18.7
PoorUptime: 92.190%

Total Incidents

38

Uptime

92.190%

Avg Resolution

2h 25m

Top Cause

api

GitHub Outage Timeline

Outages by Year

Incident Severity

Recent GitHub Incidents

View all →

Incident with Webhooks

GitHub·Mar 6, 2026·6h 30m

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.

apiauthenticationdeploymentconfiguration
low

Actions is experiencing degraded availability

GitHub·Actions·Mar 5, 2026·1h 2m

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
high

Multiple services are affected, service degradation

GitHub·Actions·Mar 5, 2026·2h 55m

On Mar 5, 2026, between 16:24 UTC and 19:30 UTC, Actions was degraded. During this time, 95% of workflow runs failed to start within 5 minutes with an average delay of 30 minutes and 10% workflow runs failed with an infrastructure error. This was due to Redis infrastructure updates that were being rolled out to production to improve our resiliency. These changes introduced a set of incorrect configuration change into our Redis load balancer causing internal traffic to be routed to an incorrect h

apiconfigurationcapacityrouting
high

Disruption with some GitHub services

GitHub·Mar 5, 2026·9m

From Feb 2, 2026 17:13 UTC to Feb 2, 2026 17:36 UTC we experienced failures on ~0.02% of Git operations. While deploying an internal service, a misconfiguration caused a small subset of traffic to route to a service that was not ready. During the incident we observed the degradation and statused publicly.<br /><br />To mitigate the issue, traffic was redirected to healthy instances and we resumed normal operation.<br /><br />We are improving our monitoring and deployment processes in this area t

networkcomputedatabaseapiauthenticationdeploymentconfigurationcapacityrouting
low

Some OpenAI models degraded in Copilot

GitHub·Copilot·Mar 5, 2026·26m

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

Claude Opus 4.6 Fast not appearing for some Copilot users

GitHub·Copilot·Mar 3, 2026·40m

On March 3, 2026, between 19:44 UTC and 21:05 UTC, some GitHub Copilot users reported that the Claude Opus 4.6 Fast model was no longer available in their IDE model selection. After investigation, we confirmed that this was caused by enterprise administrators adjusting their organization's model policies, which correctly removed the model for users in those organizations. No users outside the affected organizations lost access.<br /><br />We confirmed that the Copilot settings were functioning a

computeauthenticationconfiguration
low

Incident with all GitHub services

GitHub·API·Mar 3, 2026·1h 9m

On March 3, 2026, between 18:46 UTC and 20:09 UTC, GitHub experienced a period of degraded availability impacting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other dependent services. At the peak of the incident, GitHub.com request failures reached approximately 40%. During the same period, approximately 43% of GitHub API requests failed. Git operations over HTTP had an error rate of approximately 6%, while SSH was not impacted. GitHub Copilot requests had an

api
high

Delayed visibility of newly added issues on project boards

GitHub·Mar 2, 2026·6h 44m

Between March 2, 21:42 UTC and March 3, 05:54 UTC project board updates, including adding new issues, PRs, and draft items to boards, were delayed from 30 minutes to over 2 hours, as a large backlog of messages accumulated in the Projects data denormalization pipeline.<br /><br />The incident was caused by an anomalously large event that required longer processing time than expected. Processing this message exceeded the Kafka consumer heartbeat timeout, triggering repeated consumer group rebalan

databasecapacity
low

Incident with Pull Requests /pulls

GitHub·Mar 2, 2026·2h 53m

On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.

deploymentconfigurationrouting
low

Incident with Copilot agent sessions

GitHub·Copilot·Feb 27, 2026·31m

On February 27, 2026, between 22:53 UTC and 23:46 UTC, the Copilot coding agent service experienced elevated errors and degraded functionality for agent sessions. Approximately 87% of attempts to start or interact with agent sessions encountered errors during this period.<br /><br />This was due to an expired authentication credential for an internal service component, which prevented Copilot agent session operations from completing successfully.<br /><br />We mitigated the incident by rotating

computeauthentication
low

Incident Severity Distribution

high
6 (16%)
low
32 (84%)

Frequently Asked Questions

Is GitHub down right now?â–¾
Check the real-time status at the top of this page. IncidentHub 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 has tracked 38 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 92.190%. The reliability score is 18.7/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, capacity, deployment. 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 25 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 18.7/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