GitHub Status

Jul `29`, `2026`

No incidents reported today.

Jul `28`, `2026`

No incidents reported.

Jul `27`, `2026`

Resolved - 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.
Jul 27, 04:09 UTC

Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Jul 27, 04:09 UTC

Investigating - We are investigating reports of degraded performance for API Requests
Jul 27, 03:53 UTC

Jul `26`, `2026`

No incidents reported.

Jul `25`, `2026`

Actions run failures and delays

Resolved - 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.
Jul 25, 13:13 UTC

Update - We have seen recovery in GitHub Actions performance following our earlier mitigation. Workflow runs are processing normally, though jobs queued before 12:40 UTC may still experience failures and will need to be retried.
Jul 25, 13:12 UTC

Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 25, 12:59 UTC

Update - We have applied a mitigation for the infrastructure issue affecting GitHub Actions. Workflow run failures and delays are improving but not yet fully resolved. Our engineering team continues to work on restoring full functionality across all affected infrastructure.
Jul 25, 12:58 UTC

Update - We are experiencing issues with GitHub Actions that are causing workflow run failures and delays for some users. Our engineering team is actively investigating the infrastructure issue and working to restore full functionality.
Jul 25, 12:34 UTC

Investigating - We are investigating reports of degraded availability for Actions
Jul 25, 12:31 UTC

Several GPT models degraded

Resolved - 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.
Jul 25, 10:11 UTC

Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Jul 25, 10:04 UTC

Update - We are experiencing degraded availability for 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 in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jul 25, 09:48 UTC

Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers
Jul 25, 09:42 UTC

Incident with Actions

Resolved - 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.
Jul 25, 09:25 UTC

Update - We identified an issue causing delays in GitHub Actions run starts. Some users may have experienced longer than expected wait times when triggering workflow runs. We have applied mitigations and have recovered. Our team continues to monitor and investigate the root cause.
Jul 25, 09:20 UTC

Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 25, 09:13 UTC

Investigating - We are investigating reports of degraded performance for Actions
Jul 25, 08:59 UTC

Jul `24`, `2026`

Incident with Pull Requests

Resolved - 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.
Jul 24, 20:23 UTC

Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Jul 24, 20:02 UTC

Update - We have applied a mitigation and are monitoring for recovery
Jul 24, 19:59 UTC

Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.
Jul 24, 19:43 UTC

Update - We are investigating errors creating pull requests
Jul 24, 19:40 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests
Jul 24, 19:37 UTC

Disruption with some GitHub services

Resolved - On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in each compute cage, and an aggregation layer interconnecting the spines from each cage within each AZ. The loss of connectivity affected links between one cage’s spine switches and the aggregation layer within that specific AZ.

Workloads depending on compute resources in this cage became degraded due to packet loss, and exhibited intermittent errors:

- Actions saw 10% of jobs fail during the impact window, and 5% of jobs succeeded but with delayed starts.
- 27% of GitHub issues interactions saw slow requests or timeouts.
- 4% of GitHub Copilot requests experienced errors, though most automatically retry.
- 4% of git push operations saw impacts during the affected window.
- Authentication requests saw increased latency during the affected window, but error rates, while elevated, were < 1% in all cases.

We were able to mitigate the outage by re-routing affected connections to available fiber paths that were allocated for future capacity upgrades. Sufficient network capacity to eliminate packet loss was restored at 17:07, with most services showing full recovery by 17:16. All paths were restored and services healthy at 17:36.

This incident affected 25% of available network interconnect capacity. Older cages utilize a 100Gbps network interface standard. To remove risk of reoccurrence, a planned upgrade to 400Gbps interfaces is being accelerated as much as possible, ensuring increased bandwidth available at all layers of the switch fabric for resiliency to path or device loss.
Jul 24, 17:36 UTC

Update - We are seeing recovery across all services
Jul 24, 17:24 UTC

Update - The degradation affecting API Requests, Actions, Copilot, Issues, Pages and Pull Requests has been mitigated. We are monitoring to ensure stability.
Jul 24, 17:16 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:41 UTC

Update - We have applied a mitigation and are monitoring for recovery
Jul 24, 16:40 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jul 24, 16:28 UTC

Update - Pages is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:27 UTC

Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:26 UTC

Update - We are investigating timeouts to some GitHub services
Jul 24, 16:22 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:20 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:19 UTC

Investigating - We are investigating reports of degraded performance for API Requests and Issues
Jul 24, 16:17 UTC

Incident With Blocked GitHub.com Traffic

Resolved - 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. We are adding validation and safeguards to prevent similar incorrect blocking in the future.
Jul 24, 11:00 UTC

Jul `23`, `2026`

Latency issues across a number of services

Resolved - 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.

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 incident was mitigated by identifying the problematic shard and restoring its correct state, after which queue backlogs drained and services recovered.

To speed mitigation, we have added monitors for nodes in this unhealthy state after maintenance operations. To prevent future recurrence, we are adapting our lifecycle automation to verify host rejoin after a scheduled reboot.
Jul 23, 09:39 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:39 UTC

Update - Webhooks is operating normally.
Jul 23, 09:35 UTC

Update - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:27 UTC

Update - We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.
Jul 23, 09:22 UTC

Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:19 UTC

Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:18 UTC

Update - We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.
Jul 23, 08:34 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Jul 23, 08:25 UTC

Investigating - We are investigating reports of degraded availability for Actions, Issues and Webhooks
Jul 23, 07:53 UTC

Jul `22`, `2026`

Disruption with actions hosted runners

Resolved - 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.

At 21:49 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.
Jul 22, 22:09 UTC

Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 22, 22:01 UTC

Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 22, 22:01 UTC

Update - Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.
Jul 22, 20:47 UTC

Investigating - We are investigating reports of degraded performance for Actions
Jul 22, 20:43 UTC

Jul `21`, `2026`

Some SSH connections using deploy keys are failing

Resolved - 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.
Jul 21, 11:57 UTC

Update - We have identified a recent code change as a potential cause of the SSH authentication failures affecting deploy key connections. Our engineering team is rolling back this change. Customers using deploy keys for SSH access to repositories may continue to experience intermittent connection failures until the fix is deployed.
Jul 21, 11:46 UTC

Update - We are investigating reports of intermittent SSH authentication failures affecting connections that use deploy keys. Customers may experience failed SSH connections when interacting with repositories via deploy keys. Our engineering team is actively investigating the root cause and working toward resolution.
Jul 21, 11:04 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jul 21, 10:31 UTC

Jul `20`, `2026`

Disruption with GPT 5.3 Codex

Resolved - 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.
Jul 20, 18:37 UTC

Update - We are seeing signs of sustained recovery from the upstream provider for GPT 5.3 Codex requests. Requests are succeeding as expected. We are awaiting confirmation from the provider that the issue is fully mitigated before resolving this incident.
Jul 20, 18:25 UTC

Update - The upstream provider continues to return intermittent errors for GPT 5.3 Codex requests. Some users may experience failed or interrupted responses when using this model. Traffic continues to be automatically rerouted to reduce impact, and we are actively working with the upstream provider on a resolution. In the meantime, selecting an alternative model will avoid disruption.
Jul 20, 17:21 UTC

Update - We identified that an upstream provider is returning errors for GPT 5.3 Codex requests, causing some users to experience failed or interrupted responses. Traffic is being automatically rerouted to mitigate impact. We are working with the upstream provider to resolve the underlying issue. We recommend using a different model at this time while we resolve the problem.
Jul 20, 16:39 UTC

Update - We are investigating GPT Codex 5.3 performance.
Jul 20, 16:04 UTC

Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Jul 20, 16:03 UTC

Incident with GitHub Actions

Resolved - Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.
Jul 20, 04:44 UTC

Update - Actions has fully recovered, and we will continue to monitor the platform to ensure stability.
Jul 20, 04:43 UTC

Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 20, 03:34 UTC

Update - We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.
Jul 20, 03:27 UTC

Update - API Requests is operating normally.
Jul 20, 03:03 UTC

Update - Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.
Jul 20, 02:43 UTC

Update - API Requests is experiencing degraded performance. We are continuing to investigate.
Jul 20, 02:23 UTC

Update - Issues is operating normally.
Jul 20, 02:20 UTC

Update - Pages is operating normally.
Jul 20, 01:37 UTC

Update - We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.

A separate incident was opened before we understood they were related. We will continue to post updates on this incident.
Jul 20, 01:11 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Jul 20, 00:52 UTC

Update - Actions and Pages are experiencing degraded performance. We are continuing to investigate.
Jul 20, 00:49 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Jul 20, 00:48 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jul 20, 00:20 UTC

Update - API Requests is experiencing degraded availability. We are continuing to investigate.
Jul 20, 00:07 UTC

Update - We have identified the cause of failures in GitHub Actions and are working to restore service.
Jul 19, 23:57 UTC

Update - We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.
Jul 19, 23:37 UTC

Investigating - We are investigating reports of degraded performance for Actions
Jul 19, 23:34 UTC

Disruption with some GitHub services

Resolved - Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.
Jul 20, 01:46 UTC

Update - Git LFS API success rates have returned to normal. We will continue to monitor the service closely.
Jul 20, 01:45 UTC

Investigating - The Git LFS API issues have been identified as being related to a separate incident where Actions is experiencing degraded availability. We’re consolidating our investigation efforts under that incident.
Jul 20, 01:15 UTC

Update - Some Git LFS operations, and loading files through the API are failing. We are investigating.
Jul 20, 00:26 UTC

Monitoring - Some Git LFS operations, and loading files through the API are failing. We are investigating.
Jul 20, 00:25 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jul 20, 00:25 UTC

Jul `19`, `2026`

Jul `18`, `2026`

No incidents reported.

Jul `17`, `2026`

Degraded REST API Availability

Resolved - From 22:21 UTC - 23:50 UTC on July 16, 2026, the REST API experienced significant degradation. During this period, about 39% of REST API requests failed with HTTP 500 level responses, with the errors peaking at 44.3%.

We identified the issue as an infrastructure change that wrongly marked the majority of API backends in a single region as unhealthy. As a result, requests routed to those backends failed before reaching the application layer.

To prevent this from happening again, we're improving our systems to catch this kind of invalid configuration before it reaches production. We'll also audit the related systems to make them more resilient to future changes, and we're increasing our monitoring sensitivity so we're alerted to problems like this sooner.
Jul 17, 00:14 UTC

Update - As of 23:46 UTC, the REST API service is reachable and responding to requests normally.
Jul 17, 00:14 UTC

Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Jul 17, 00:00 UTC

Update - We are continuing to investigate an issue causing approximately 35% of REST API requests to fail. Based on our current understanding, requests are not consistently reaching the application layer, resulting in failed requests returning HTML responses instead of the expected API response format. We are actively investigating the issue and will provide another update as soon as more information is available.
Jul 16, 23:29 UTC

Update - API Requests is experiencing degraded performance. We are continuing to investigate.
Jul 16, 22:58 UTC

Update - We are aware of degraded REST API availability and are investigating
Jul 16, 22:58 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jul 16, 22:51 UTC

Jul `16`, `2026`

Claude Fable 5 experiencing degraded performance

Resolved - 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.
Jul 16, 22:04 UTC

Update - We are experiencing degraded availability for the Claude Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jul 16, 21:06 UTC

Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Jul 16, 21:05 UTC

Disruption with some GitHub services

Resolved - On July 16, 2026, between 08:50 UTC and 09:50 UTC, the GitHub MCP Server’s web_search tool experienced elevated failures. The average error rate was 42% and peaked at 82% of requests to the tool. Other GitHub MCP Server tools were unaffected. This was caused by degradation at a downstream web search provider.

The incident was mitigated when the downstream provider recovered, after which we confirmed that the tool’s success rate had returned to normal.

We are improving the tool’s resilience and failure handling to reduce the customer impact and duration of similar incidents.
Jul 16, 12:20 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.
Jul 16, 10:17 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jul 16, 09:30 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jul 16, 09:13 UTC

Jul `15`, `2026`

No incidents reported.

All Systems Operational

About This Site

Related

Past Incidents

Jul 29, 2026

Jul 28, 2026

Jul 27, 2026

Jul 26, 2026

Jul 25, 2026

Jul 24, 2026

Jul 23, 2026

Jul 22, 2026

Jul 21, 2026

Jul 20, 2026

Jul 19, 2026

Jul 18, 2026

Jul 17, 2026

Jul 16, 2026

Jul 15, 2026

Jul `29`, `2026`

Jul `28`, `2026`

Jul `27`, `2026`

Jul `26`, `2026`

Jul `25`, `2026`

Jul `24`, `2026`

Jul `23`, `2026`

Jul `22`, `2026`

Jul `21`, `2026`

Jul `20`, `2026`

Jul `19`, `2026`

Jul `18`, `2026`

Jul `17`, `2026`

Jul `16`, `2026`

Jul `15`, `2026`