GitHub Status

Jun 9, 2026

No incidents reported today.

Jun 8, 2026

Degraded availability for GitHub.com, GraphQL API, and Webhooks UI/API

Resolved - On June 8, 2026, between 14:49 and 14:54 UTC, a subset of requests to GitHub.com, the REST API, GraphQL API, and Webhooks UI/API experienced elevated error rates due to a transient infrastructure capacity issue that self-resolved within approximately 5 minutes.

Users experienced HTTP 500 errors and timeouts when accessing GitHub.com, the REST API, GraphQL API, and Webhooks UI/API for approximately 5 minutes, with the REST API taking up to 12 minutes to fully recover.
Jun 8, 15:00 UTC

Disruption with Claude Opus 4.7

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.
Jun 8, 10:03 UTC

Update - We are experiencing degraded availability for the Claude Opus 4.7 model 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, and starting to see recovery.

Jun 8, 09:49 UTC

Update - We are experiencing degraded availability for the Claude Opus 4.7 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.
Jun 8, 09:08 UTC

Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Jun 8, 09:05 UTC

Pull Requests and Issues unavailable for signed-out users

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.
Jun 8, 08:36 UTC

Monitoring - The degradation affecting Actions, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
Jun 8, 08:35 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Jun 8, 08:27 UTC

Update - Following investigation, we are seeing that impact is limited to unauthenticated users when accessing Pull Requests, Issues, or Actions. Our team continues to work towards mitigation with more updates to follow as we have them.
Jun 8, 08:13 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Jun 8, 07:32 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Jun 8, 07:31 UTC

Update - Issues is experiencing degraded availability. We are continuing to investigate.
Jun 8, 07:14 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 8, 07:11 UTC

Jun 7, 2026

No incidents reported.

Jun 6, 2026

EU Network Maintenance

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.
Jun 6, 18:49 UTC

Update - All work has been completed and we are hands off.
Jun 6, 18:48 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 6, 15:36 UTC

Update - We are conducting routine maintenance on our network infrastructure in the EU. This will not impact production traffic, but may result in slightly increased latency for the remainder of our work. We expect this to last until 17:00 UTC.
Jun 6, 15:31 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 6, 15:31 UTC

Disruption with some GitHub services in the EU region

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.
Jun 6, 17:07 UTC

Update - Packages is experiencing degraded performance. We are continuing to investigate.
Jun 6, 16:56 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 6, 16:53 UTC

Jun 5, 2026

Auth issue resulting in API impacts, including some Slack and Teams channel subscriptions

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.
Jun 5, 22:21 UTC

Update - Affected Slack and Teams subscriptions have been restored. Please contact support if you encounter any additional issues.
Jun 5, 22:21 UTC

Update - Additional detail on the scope of impact during the 14:49 UTC to 16:45 UTC window: a small but elevated percentage of authenticated requests to GitHub.com received incorrect authorization failures. We saw a 1 to 2% increase in 4xx responses for a small number of endpoints (/repos/{owner}/{repo}/pulls/{pull_number}, /repos/{owner}/{repo}, /repos/{owner}/{repo}/contents/{path}). The vast majority of requests completed normally; customers who saw errors during the window can retry now and should see them succeed.
Jun 5, 20:34 UTC

Update - We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.
Jun 5, 18:43 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 5, 18:05 UTC

Update - During 14:49 UTC to 16:45 UTC, customers may have experienced authorization failures for legitimate requests. This was caused by a recently enabled feature flag, which has now been turned off as a mitigation. Customers should now see normal authorization behavior. This is also the cause of the chat integration issue, and we are exploring options to restore it. In the meantime, customers can manually re-subscribe their repo.
Jun 5, 18:04 UTC

Update - Customers may see unexpected repo unsubscription events in their Slack or Teams channels.
Jun 5, 17:25 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 5, 17:20 UTC

Jun 4, 2026

Live updates degraded

Resolved - Everything is operating normally.
Jun 4, 20:32 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 4, 20:20 UTC

Copilot Code Review Failing

Resolved - On June 4, 2026, from 17:30 UTC to 18:55 UTC, Copilot Code Review experienced elevated failures for review requests on GitHub.com. Affected users saw “Copilot ran into an error” on pull requests when requesting a code review.

During the incident window, an average of 81.6% of Copilot Code Review requests failed, with a peak failure rate of 93.9%. Approximately 36,800 code review requests failed. GitHub Enterprise Cloud with data residency was not impacted.

The issue was caused by a newly released dependency used by the Copilot Code Review processing workflow. The release introduced an incompatibility with the runtime environment. Because the workflow automatically consumed the latest release, the incompatible version was picked up without sufficient compatibility validation and caused review processing to fail.

We mitigated the incident by removing the problematic dependency version and redeploying the affected processing service. New code reviews began recovering at 18:44 UTC, and the failure rate returned to baseline by 18:55 UTC. Remaining timed-out work drained by 19:59 UTC.

To reduce the risk of recurrence, we are pinning the dependency version instead of automatically consuming the latest release, adding compatibility checks for future releases, improving fast-failure behavior when the review processor cannot start, adding shorter timeout controls for review workflows, and improving monitoring for review completion failures.
Jun 4, 19:59 UTC

Update - This issue is now fully resolved and Copilot Code Review is working as expected.
Jun 4, 19:59 UTC

Update - The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. We are continuing to monitor for full resolution.

Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
Jun 4, 19:41 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 4, 19:07 UTC

Update - The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected.

Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
Jun 4, 19:07 UTC

Update - The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.
Jun 4, 18:52 UTC

Update - We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.

A mitigation is in progress, we expect mitigation in approximately 30m.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 4, 18:22 UTC

Update - We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.

A mitigation is in progress.
Jun 4, 18:03 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 4, 18:02 UTC

Disruption with some GitHub services

Resolved - Between June 1, 2026, 23:00 UTC and June 4, 2026 04:11 UTC, customers experienced delays in Dependabot scheduled version updates.

Pull request creation for version updates was delayed, with delays increasing over time and reaching up to two days. Approximately 1.5 million repositories with active Dependabot version update configurations were affected. Dependabot security updates were not affected. The primary cause was changes to an internal platform service that routes requests for Dependabot and other services.

We mitigated the incident by deploying a fix that enables batch enqueuing of update jobs, which significantly increased processing throughput. Once the backlog was drained, Dependabot returned to normal processing times.

To reduce the risk of recurrence, we are working on tuning batch size and concurrency limits for Dependabot update job processing. We are also adding monitoring for job processing lag to enable earlier detection and faster mitigation of similar issues.
Jun 4, 04:11 UTC

Update - Job lag has recovered to within normal operating thresholds. We are declaring this incident closed and will follow up with a summary soon.
Jun 4, 04:11 UTC

Update - Job lag has recovered from a peak of 1.71 days to 9h 9m at 19:29 UTC and continues to decrease. Backlog is draining at a healthy rate with no signs of reversal. New jobs are processing on schedule. Remaining lag will continue to drain over the next few hours as queued work completes; this is expected post-incident catch-up, not active impact. We will continue monitoring and re-engage if lag trend reverses.
Jun 4, 02:37 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 4, 02:35 UTC

Update - We have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates.

Next update in 12 hours.
Jun 3, 23:38 UTC

Update - We are preparing a mitigation for the delayed Dependabot scheduled version updates.

Next update in 2 hours.
Jun 3, 21:10 UTC

Update - Customers may see delays of up to two days in Dependabot version updates.

Dependabot Security updates are not delayed.

The team is investigating mitigations for the backlog.

Next update in 1 hour.
Jun 3, 20:18 UTC

Update - We're seeing delays in Dependabot scheduled version update runs. Our team is actively working on a fix and will share updates as the situation develops.
Jun 3, 19:43 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 3, 19:42 UTC

Jun 3, 2026

Disruption with some GitHub services

Resolved - On June 2, 2026, between 21:54 UTC and June 3, 2026 06:45 UTC, the Spark service was degraded and users were unable to store or retrieve data for their Spark apps in one of our hosting regions. Users could still make changes to their app configuration during this time. The error rate peaked at 25% of affected requests to the service. Impact was limited to users whose requests were served through a single affected region; 43 users experienced errors during this window.

The root cause was a configuration that referenced a service component by a fixed address rather than a dynamic service endpoint. When the component was replaced, requests could no longer reach the fixed address and began to fail. We resolved the incident by updating the configuration to use a our standard service endpoints that are resilient to component replacement. Recovery time was extended because replacing the component required overrides to a temporary deployment safeguard.

We are working to add validation that prevents fixed infrastructure addresses from being used in application configuration outside of test environments and to improve our monitoring to reduce our time to detect.
Jun 3, 06:46 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 3, 06:45 UTC

Update - We are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation.
Jun 3, 06:02 UTC

Update - We are investigating reports of impacted performance for some GitHub services.

---
Relevant stamps: dotcom
Jun 3, 03:45 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 3, 03:13 UTC

Jun 2, 2026

Delays with Code Scanning and Billing

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.
Jun 2, 00:17 UTC

Update - We have identified the root cause and applied mitigations to address delays in billing updates and are continuing to see improvement in the processing rate. We will continue to monitor the progress and will provide an update in few hours.

GitHub Enterprise Cloud with Data Residency is not impacted.

Jun 1, 21:59 UTC

Update - We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations are continuing to see signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.

Next update in 2 hours.
Jun 1, 19:27 UTC

Update - We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations and are seeing some more signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 1, 18:48 UTC

Update - We are continuing to investigate delayed billing updates, on GitHub.com. We have applied multiple mitigations and are seeing some signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 1, 17:28 UTC

Update - We are investigating reports of delayed billing updates, on GitHub.com. We are continuing to investigate delays in our job processing architecture. We are attempting to mitigate at the infrastructure level. Code scanning runs and notifications have recovered. We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 1, 16:42 UTC

Update - We are investigating reports of delayed code scanning runs, billing updates, email and mobile push notifications. We are investigating delays in our job processing architecture. We will continue to keep users updated on progress towards mitigation.
Jun 1, 15:43 UTC

Update - We are investigating reports of delayed code scanning runs and delayed billing updates. We will continue to keep users updated on progress towards mitigation.
Jun 1, 15:17 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 1, 15:17 UTC

Jun 1, 2026

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026

Disruption with OpenAI Models

Resolved - On May 28th, 2026, between approximately 18:27 and 20:41 UTC, the GitHub Copilot service was degraded due to an issue with the Responses API of an upstream provider affecting the GPT-5.2, GPT-5.3-Codex, GPT-5.4, and GPT-5.5 models. Requests routed to these models via the Responses API returned elevated error rates, which also affected Copilot coding agent and Copilot code review. No other models were impacted.

We mitigated the incident by shifting traffic away from the affected models while the upstream provider deployed a fix.

GitHub is working to improve automated failover for the affected models and strengthen monitoring to prevent similar incidents in the future.
May 28, 20:41 UTC

Update - Open AI models are currently unavailable. We are shifting requests to other models to reduce impact.
May 28, 20:06 UTC

Update - We are investigating errors with Copilot requests using OpenAI models
May 28, 19:40 UTC

Update - Copilot is experiencing degraded performance. We are continuing to investigate.
May 28, 19:20 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
May 28, 19:01 UTC

Elevated error rates across multiple services

Resolved - On May 28, 2026, between 19:07 UTC and 19:16 UTC, multiple GitHub services experienced elevated error rates. This was due to a change that was partially deployed to an authentication service, causing errors for dependent services including the web experience, REST API, Git operations, and GitHub Actions. At peak impact, 10% of GitHub Actions runs failed to queue or encountered errors while downloading actions. We mitigated the incident by rolling back the change.

We are expanding test coverage and improving our deployment validation process to prevent recurrence of this issue in the future.
May 28, 19:07 UTC

Webhook APIs and UI Degraded

Resolved - On May 28, 2026, between 00:54 UTC and 01:19 UTC, some users experienced errors when interacting with the Webhooks API, including webhook delivery history and configuration endpoints. On average, the error rate was 0.28% and peaked at 0.45%. This was due to a bug that caused a single Kubernetes pod to enter a CrashLoopBackOff after receiving a 500 with an empty response body from Cosmos DB.

We mitigated the incident by restarting the service. To prevent future incidents, we are pushing a change to handle this response scenario from Cosmos DB appropriately.
May 28, 01:32 UTC

Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
May 28, 01:27 UTC

Investigating - We are investigating reports of degraded performance for Webhooks
May 28, 01:13 UTC

May 27, 2026

Incident with Pull Requests, Issues, Git Operations and API Requests

Resolved - On May 27, 2026, between 12:07 UTC and 13:16 UTC, users experienced degraded performance for Git operations, Pull Requests, Issues, GraphQL API, and related services on github.com. During this time, operations that depended on Git file servers experienced elevated error rates (3.5% of pushes via HTTPS and 0.2% of pushes via SSH failed; no fetches/clones failed). An internal analytics component generated unexpectedly high load, which caused CPU saturation on the underlying infrastructure. This led to cascading slowdowns and errors across services that depend on Git operations. The issue was mitigated by stopping the offending component. Services began recovering shortly after mitigation and were fully restored by 13:16 UTC. We are taking steps to add resource limits and kill switches for internal analytics components to prevent similar issues in the future.
May 27, 13:16 UTC

Update - We're continuing to investigate degraded performance of Git operations, Issues and Pull requests.
May 27, 12:54 UTC

Investigating - We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests
May 27, 12:10 UTC

May 26, 2026

Disruption with some GitHub services

Resolved - On May 26, 2026, between 15:10 UTC and 16:35 UTC the Copilot service was degraded and many models were no longer available for use. On average, the error rate was ~5% and peaked at 11% of requests to the service. This was due to a change that introduced a configuration mismatch in HMAC signing credentials which caused the list of available models to be truncated. This was mitigated by rolling back the change. This rollback was complete by 15:34 UTC though users continued to see impact until cache TTLs expired.

We are working to improve our monitoring and error handling to reduce time to detection and better experience for issues like this in the future.
May 26, 16:35 UTC

Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
May 26, 16:24 UTC

Update - Copilot is experiencing degraded performance. We are continuing to investigate.
May 26, 15:48 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
May 26, 15:44 UTC

Incident with Actions and Pages

Resolved - On May 26, 2026, between 10:40 UTC and 12:56 UTC, GitHub Actions jobs were degraded. From 10:40 to 12:16 UTC, all newly queued Actions runs failed to start. From 12:16 to 12:56 UTC, Actions runs that required downloading actions for their workflows continued to fail. GitHub Pages, Copilot Code Review, Copilot coding agent, Octoshift, and GitHub Enterprise Importer were also impacted due to their dependency on Actions.

This was caused by our automated account review system incorrectly suspending the service account used by GitHub Actions to authenticate workflow runs and download actions.

We mitigated by restoring the account at 12:16 UTC, marking it exempt from further automated review at 12:20 UTC, and redeploying a related service at 12:48 UTC to flush cached account state. Full recovery was confirmed at 12:56 UTC.

During this incident, a small number of Issues, PRs, Comments, and Discussions were marked as hidden when the service account was disabled. No data was lost. All content hidden because of this incident has been restored and full search index restoration is in progress.

To prevent a recurrence, we have added an allowlist of all service accounts that cannot be suspended by automated systems, and ensuring these protections are enforced consistently across all account management tooling. We are also improving diagnostic tooling for accounts and reducing cache propagation delays to shorten time to mitigate similar incidents in the future.
May 26, 13:18 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.
May 26, 13:01 UTC

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

Update - We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation
May 26, 12:37 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
May 26, 12:17 UTC

Update - We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.
May 26, 11:53 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
May 26, 11:19 UTC

Investigating - We are investigating reports of degraded performance for Actions and Pages
May 26, 10:57 UTC

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents