GitHub Status

Oct 10, 2025

No incidents reported today.

Oct 9, 2025

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.
Oct 9, 16:40 UTC

Update - All services have fully recovered.
Oct 9, 16:39 UTC

Update - Actions has fully recovered but Notifications is still experiencing delays. We will continue to update as the system is fully restored to normal operation.
Oct 9, 16:27 UTC

Update - Actions is operating normally.
Oct 9, 16:24 UTC

Update - Pages is operating normally.
Oct 9, 16:08 UTC

Update - Git Operations is operating normally.
Oct 9, 16:04 UTC

Update - Actions and Notifications are still experiencing delays as we process the backlog. We will continue to update as the system is fully restored to normal operation.
Oct 9, 16:02 UTC

Update - Pull Requests is operating normally.
Oct 9, 15:51 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Oct 9, 15:48 UTC

Update - We are seeing full recovery in many of our systems, but delays are still expected for actions. We will continue to update as the system is fully restored to normal operation.
Oct 9, 15:44 UTC

Update - Webhooks is operating normally.
Oct 9, 15:43 UTC

Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Oct 9, 15:40 UTC

Update - Issues is operating normally.
Oct 9, 15:39 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Oct 9, 15:38 UTC

Update - API Requests is operating normally.
Oct 9, 15:26 UTC

Update - We identified a faulty network component and have removed it from the infrastructure. Recovery has started and we expect full recovery shortly.
Oct 9, 15:25 UTC

Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.
Oct 9, 15:20 UTC

Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
Oct 9, 15:20 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Oct 9, 15:17 UTC

Update - We are investigating widespread reports of delays and increased latency in various services. We will continue to keep users updated on progress toward mitigation.
Oct 9, 15:11 UTC

Update - Issues is experiencing degraded availability. We are continuing to investigate.
Oct 9, 15:09 UTC

Update - API Requests is experiencing degraded performance. We are continuing to investigate.
Oct 9, 15:09 UTC

Update - Pages is experiencing degraded performance. We are continuing to investigate.
Oct 9, 15:09 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Oct 9, 14:50 UTC

Investigating - We are investigating reports of degraded availability for Webhooks
Oct 9, 14:45 UTC

Multiple GitHub API endpoints are experiencing errors

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.
Oct 9, 13:56 UTC

Update - A feature was partially rolled out that had high impact on one of our primary databases but we were able to roll it back. All services are recovered but we will monitor for recovery before statusing green.
Oct 9, 13:54 UTC

Investigating - We are currently investigating this issue.
Oct 9, 13:52 UTC

Oct 8, 2025

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.
Oct 8, 00:05 UTC

Update - We are seeing recovery of audit log ingestion and continue to monitor recovery.
Oct 7, 22:45 UTC

Update - We are seeing recovery of audit log ingestion and continue to monitor recovery.
Oct 7, 21:51 UTC

Update - We continue to apply mitigations and monitor for recovery.
Oct 7, 21:17 UTC

Update - We have identified an issue causing delayed audit log event ingestion and are working on a mitigation.
Oct 7, 20:33 UTC

Update - Ingestion of new audit log events is delayed
Oct 7, 19:48 UTC

Investigating - We are currently investigating this issue.
Oct 7, 19:48 UTC

Oct 7, 2025

Oct 6, 2025

No incidents reported.

Oct 5, 2025

No incidents reported.

Oct 4, 2025

No incidents reported.

Oct 3, 2025

Incident with Copilot

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.
Oct 3, 03:47 UTC

Update - 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.
Oct 3, 03:47 UTC

Update - The upstream provider is implementing a fix. Services are recovering. We are monitoring the situation.
Oct 3, 03:04 UTC

Update - We’re seeing degraded experience across Anthropic models. We’re working with our partners to restore service.
Oct 3, 02:42 UTC

Investigating - We are investigating reports of degraded performance for Copilot
Oct 3, 02:41 UTC

Oct 2, 2025

Degraded Gemini 2.5 Pro experience in Copilot

Resolved - Between October 1st, 2025 at 1 AM UTC and October 2nd, 2025 at 10:33 PM UTC, the Copilot service experienced a degradation of the Gemini 2.5 Pro model due to an issue with our upstream provider. Before 15:53 UTC on October 1st, users experienced higher error rates with large context requests while using Gemini 2.5 Pro. After 15:53 UTC and until 10:33 PM UTC on October 2nd, requests were restricted to smaller context windows when using Gemini 2.5. Pro. No other models were impacted.

The issue was resolved by a mitigation put in place by our provider. GitHub is collaborating with our provider to enhance communication and improve the ability to reproduce issues with the aim to reduce resolution time.
Oct 2, 22:33 UTC

Update - We have confirmed that the fix for the lower token input limit for Gemini 2.5 Pro is in place and are currently testing our previous higher limit to verify that customers will experience no further impact.
Oct 2, 22:26 UTC

Update - The underlying issue for the lower token limits for Gemini 2.5 Pro has been identified and a fix is in progress. We will update again once we have tested and confirmed that the fix is correct and globally deployed.
Oct 2, 17:13 UTC

Update - We are continuing to work with our provider to resolve the issue where some Copilot requests using Gemini 2.5 Pro return an error indicating a bad request due to exceeding the input limit size.
Oct 2, 02:52 UTC

Update - We are continuing to investigate and test solutions internally while working with our model provider on a deeper investigation into the cause. We will update again when we have identified a mitigation.
Oct 1, 18:16 UTC

Update - We are testing other internal mitigations so that we can return to the higher maximum input length. We are still working with our upstream model provider to understand the contributing factors for this sudden decrease in input limits.
Oct 1, 17:37 UTC

Update - We are experiencing a service regression for the Gemini 2.5 Pro model in Copilot Chat, VS Code and other Copilot products. The maximum input length of Gemini 2.5 prompts been decreased. Long prompts or large context windows may result in errors. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

Other models are available and working as expected.
Oct 1, 16:49 UTC

Investigating - We are investigating reports of degraded performance for Copilot
Oct 1, 16:43 UTC

Oct 1, 2025

Degraded Performance for GitHub Actions MacOS Runners

Resolved - On October 1, 2025 between 07:00 UTC and 17:20 UTC, Mac hosted runner capacity for Actions was degraded, leading to timed out jobs and long queue times. On average, the error rate was 46% and peaked at 96% of requests to the service. XL and Intel runners recovered by 10:10 UTC, with the other types taking longer to recover.

The degraded capacity was triggered by a scheduled event at 07:00 UTC that led to a permission failure on Mac runner hosts, blocking reimage operations. The permission issue was resolved by 9:41 UTC, but the recovery of available runners took longer than expected due to a combination of backoff logic slowing backend operations and some hosts needing state resets.

We deployed changes immediately following the incident to address the scheduled event and ensure that similar failures will not block critical operations in the future. We are also working to reduce the end-to-end time for self-healing of offline hosts for quicker full recovery of future capacity or host events.
Oct 1, 16:55 UTC

Update - We are seeing some recovery for image queueing and continuing to monitor.
Oct 1, 16:27 UTC

Update - We are continuing work to restore capacity for our MacOS ARM runners.
Oct 1, 14:41 UTC

Update - Our team continues to work hard on restoring capacity for the Mac runners.
Oct 1, 13:58 UTC

Update - Work continues on restoring capacity on the Mac runners.
Oct 1, 13:12 UTC

Update - MacOS ARM runners continue to be at reduced capacity, causing queuing of jobs. Investigation is ongoing.
Oct 1, 12:32 UTC

Update - Work continues to bring the full runner capacity back online. Resources are focused on improving the recovery of certain runner types.
Oct 1, 11:51 UTC

Update - We are continuing to see recovery of some runner capacity and investigating slow recovery of certain runner types.
Oct 1, 11:11 UTC

Update - We are seeing recovery of some runner capacity, while also investigating slow recovery of certain runner types.
Oct 1, 10:30 UTC

Update - MacOS runners are coming back online and starting to process queued work.
Oct 1, 09:44 UTC

Update - We are continuing to deploy the necessary changes to restore MacOS runner capacity.
Oct 1, 08:59 UTC

Update - We have identified the cause and are deploying a change to restore MacOS runner capacity.
Oct 1, 08:27 UTC

Update - Customers using GitHub Actions Mac OS runners are experiencing job start delays and failures. We are aware of this issue and actively investigating.
Oct 1, 08:17 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Oct 1, 08:09 UTC

Investigating - We are currently investigating this issue.
Oct 1, 07:59 UTC

Sep 30, 2025

No incidents reported.

Sep 29, 2025

Disruption with Gemini 2.5 Pro and Gemini 2.0 Flash in Copilot

Resolved - On September 29, 2025, between 17:53 and 18:42 UTC, the Copilot service experienced a degradation of the Gemini 2.5 model due to an issue with our upstream provider. Approximately 24% of requests failed, affecting 56% of users during this period. No other models were impacted.

GitHub notified the upstream provider of the problem as soon as it was detected. The issue was resolved after the upstream provider rolled back a recent change that caused the disruption. GitHub will continue to enhance our monitoring and alerting systems to reduce the time it takes to detect and mitigate similar issues in the future.
Sep 29, 19:12 UTC

Update - The upstream model provided has resolved the issue and we are seeing full availability for Gemini 2.5 Pro and Gemini 2.0 Flash.
Sep 29, 19:12 UTC

Update - We are experiencing degraded availability for the Gemini 2.5 Pro & Gemini 2.0 Flash models in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

Other models are available and working as expected.
Sep 29, 18:40 UTC

Investigating - We are currently investigating this issue.
Sep 29, 18:39 UTC

Disruption with some GitHub services

Resolved - On September 29, 2025 between 16:26 UTC and 17:33 UTC the Copilot API experienced a partial degradation causing intermittent erroneous 404 responses for an average of 0.2% of GitHub MCP server requests, peaking at times around 2% of requests. The issue stemmed from an upgrade of an internal dependency which exposed a misconfiguration in the service.

We resolved the incident by rolling back the upgrade to address the misconfiguration. We fixed the configuration issue and will improve documentation and rollout process to prevent similar issues.
Sep 29, 17:33 UTC

Update - Customers are getting 404 responses when connecting to the GitHub MCP server. We have reverted a change we believe is contributing to the impact, and are seeing resolution in deployed environments.
Sep 29, 17:28 UTC

Investigating - We are currently investigating this issue.
Sep 29, 16:45 UTC

Sep 28, 2025

No incidents reported.

Sep 27, 2025

No incidents reported.

Sep 26, 2025

No incidents reported.

All Systems Operational

About This Site

Past Incidents