GitHub Status

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

Jul 14, 2026

Incident with Webhooks

Resolved - On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to not be written to our webhook deliveries store after being processed and delivered successfully. Affected deliveries would be missing from the webhook delivery UI and API and won’t be available for redelivery.

The root cause was an uncoordinated rollout: a change to how delivery records are handed off between pipeline components was deployed before the upstream components producing those records were updated to match. While the rollout was in progress, affected records were silently skipped rather than persisted, with no automatic retry. The impact ended as soon as the rollout was completed.

About 2.4M delivery records were skipped (approximately 4% of the 20-minute impact window, 0.04% of a typical 24-hour period). Importantly, 95% of these deliveries reached customer endpoints successfully, only the record of the delivery is missing. Of the ~5% that failed to reach customer endpoints, only ~1.4% (5,463) map to webhooks that retried their deliveries in the past 28 days.

To prevent recurrence, we are making delivery persistence safe-by-default, adding alert on drops in the persisted-delivery rate, and tightening rollout coordination for changes that span multiple components in the pipeline.
Jul 14, 18:01 UTC

Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Jul 14, 17:55 UTC

Update - Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when deliveries were accepted and processed. Customers may notice missing webhook deliveries in the UI, and these deliveries will not be retryable.

Impact resolved automatically once the deployment completed.
Jul 14, 17:55 UTC

Investigating - We are investigating reports of degraded performance for Webhooks
Jul 14, 17:38 UTC

Disruption with some GitHub services

Resolved - On July 14, 2026, the GitHub Codespaces service was degraded during two periods — between 06:00 UTC and 09:56 UTC, and again between 10:54 UTC and 12:53 UTC — and some users experienced intermittent failures or delays when creating new codespaces. Impact was concentrated in a subset of geographic regions. During the first period, the error rate averaged 0.5% and peaked at 4.6% of codespace creation requests. The second period was more pronounced, peaking at approximately 30% of codespace creation requests in the most-affected region before recovery. Both periods were caused by an unexpected surge in codespace creation from an abusive actor that drained the available compute capacity in the affected regions faster than it could be replenished.

We mitigated the impact by identifying and stopping the sources of the excess creation volume, reducing the resources that could be consumed in the affected regions, and rebalancing traffic across regions to restore capacity. Codespace creation success rates returned to normal after each period.

We are working to add automated, low-latency controls to throttle abnormal codespace creation and to strengthen our detection and safeguards, so we can reduce our time to detection and mitigation of issues like this in the future.
Jul 14, 09:56 UTC

Monitoring - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
Jul 14, 09:51 UTC

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
Jul 14, 08:22 UTC

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

Jul 13, 2026

Actions runs are experiencing failures to start

Resolved - On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of Actions jobs failed to start and 2% were delayed more than 5 minutes.

The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values. This caused a critical Actions service to scale below its required baseline, reducing capacity for workflow processing. We identified the regression, rolled back the change, and restored service capacity. New workflow executions recovered by 13:39 UTC. Full recovery was reached by 13:53 UTC after the queued backlog was drained.

To prevent recurrence, we have added deployment guardrails to validate that autoscaling inputs are current and to detect drift between planned and live scaling state before autoscaling changes are applied.
Jul 13, 13:53 UTC

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

Update - Pages is experiencing degraded performance. We are continuing to investigate.
Jul 13, 13:32 UTC

Investigating - We are investigating reports of degraded availability for Actions
Jul 13, 13:32 UTC

Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026

No incidents reported.

Jul 9, 2026

Delays starting Actions runs

Resolved - On July 9, 2026, between 03:29 UTC and 13:39 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 8% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 2% failed to start.

At 13:39 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 9, 13:52 UTC

Update - Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated.

We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.
Jul 9, 13:41 UTC

Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
Jul 9, 13:39 UTC

Update - We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog.

Customers may see a small rate of API and job failures as the system is recovering.

Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery.

Pages were accessible throughout the incident.
Jul 9, 13:17 UTC

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

Update - We're seeing Actions and Pages recovery.

For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing.

GitHub pages builds were also failing during that period, but Pages are still accessible.

We are continuing to monitor for full recovery.
Jul 9, 12:54 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jul 9, 12:46 UTC

Update - Pages is experiencing degraded performance. We are continuing to investigate.
Jul 9, 12:36 UTC

Update - Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.
This has caused some customers to exceed their hosted compute concurrency and experience increased impact.

We are continuing to working on infrastructure mitigations.

Next update in one hour.
Jul 9, 12:01 UTC

Update - Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.
Jul 9, 10:15 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jul 9, 10:07 UTC

Update - We are continuing to work on a mitigation.
Jul 9, 06:01 UTC

Update - Approximately 5% 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 9, 04:51 UTC

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

Jul 8, 2026

No incidents reported.

Jul 7, 2026

Actions and Codespaces APIs experiencing partial failures

Resolved - On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests, though retries were frequently successful. In-progress Actions runs and Codespaces were not impacted and continued successfully. This was due to a recent change that did not deliver the expected performance and, under certain conditions, caused downstream errors.

We mitigated the incident by rolling back the change, after which the affected services recovered.

We are working to improve the resilience of our services to these conditions and to strengthen our monitoring to reduce our time to detection and mitigation of issues like this one in the future.
Jul 7, 16:17 UTC

Monitoring - The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability.
Jul 7, 16:02 UTC

Update - We have rolled out the mitigation and are seeing recovery.
Jul 7, 16:00 UTC

Update - Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation.
Jul 7, 15:50 UTC

Update - Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful.

We continue to investigate the source of these errors.
Jul 7, 15:06 UTC

Update - Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time. Retries may be successful.

Actions runs and codespaces in progress are continuing successfully.

We are continuing to investigate the source of these errors.
Jul 7, 14:47 UTC

Update - Codespaces is experiencing degraded availability. We are continuing to investigate.
Jul 7, 14:32 UTC

Update - Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time.

Actions runs in progress are continuing successfully.
Jul 7, 14:14 UTC

Investigating - We are investigating reports of degraded performance for Actions and Codespaces
Jul 7, 14:14 UTC

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents