GitHub Status

Jun 12, 2026

No incidents reported today.

Jun 11, 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.
Jun 11, 22:19 UTC

Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 11, 20:00 UTC

Update - We have applied a mitigation and are monitoring for recovery.
Jun 11, 19:58 UTC

Update - We are currently experiencing delays in Web Hook delivery and are actively investigating the root cause.
Jun 11, 19:42 UTC

Investigating - We are investigating reports of degraded performance for Webhooks
Jun 11, 19:42 UTC

Jun 10, 2026

Authentication issues related to API 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.
Jun 10, 16:39 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 10, 16:37 UTC

Update - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Jun 10, 16:36 UTC

Update - We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Erroneous 401 responses are causing app integrations to trigger authentication flows. We have identified a problematic component in our infrastructure and are working to mitigate.
Jun 10, 16:21 UTC

Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Jun 10, 15:46 UTC

Update - We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Further updates will be provided as we work to mitigate.
Jun 10, 15:46 UTC

Update - We are investigating issues related to sporadic authentication failures impacting approximately 15% of API traffic. We will continue to investigate and provide updates.
Jun 10, 15:27 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Jun 10, 15:27 UTC

Update - API Requests is experiencing degraded availability. We are continuing to investigate.
Jun 10, 15:23 UTC

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

Jun 9, 2026

No incidents reported.

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 was used to notify for a maintenance event. There is no specific root cause analysis. Maintenance did run longer than expected (we were complete at 18:48 UTC) but the work proceeded as planned.
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 - On June 6, 2026 between 16:18 UTC and 17:01 UTC, users experienced elevated error rates when performing Git operations (cloning, fetching, downloading archives) and accessing package registries. The issue affected users whose traffic was routed through our European infrastructure.

During this time, on average 0.95% of Codeload requests and 9.2% of Package Registry requests failed with server errors. At peak, the Codeload error rate reached 1.76% and Package Registry errors reached 27%.

The root cause was a planned network circuit migration that disrupted connectivity at one of our points of presence. Our process for shifting traffic away from the site did not operate as expected, resulting in a small amount of production traffic to continue being serviced at the effected site during the maintenance window. The issue was mitigated by rolling back the network change, restoring normal connectivity. Services fully recovered by 17:01 UTC.

To reduce the likelihood of similar incidents in the future, we are reviewing our site drain process to make it more verbose and add visibility so any unexpected behavior is caught earlier.
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 - On June 5, 2026, between 15:35 UTC and 16:45 UTC, 0.11% of authenticated REST API requests incorrectly returned “not found” responses. Impact was concentrated among - and significantly higher for - users authenticating with user-to-server tokens to access organization-owned repositories.

Some users of our GitHub for Slack and GitHub for Microsoft Teams integrations saw their channel subscriptions removed as those systems interpreted the transient "not found" response as durable loss of access. Roughly 12% of organizations with active channel subscriptions were impacted, with ~2% of all channel subscriptions being removed.

These issues were triggered by a change to an internal authorization component that did not correctly resolve access for user-to-server tokens against organization-owned repositories. We mitigated the incident by disabling the accompanying feature flag at 16:45 UTC, after which API responses returned to normal. We then restored all impacted Slack and Microsoft Teams channel subscriptions, with restoration completed at 22:21 UTC.

We are working to add retry and grace-period logic in the chat integrations so transient errors no longer trigger subscription deletions. In parallel, we are improving observability and gating of authorization changes so downstream impact is detected during scoped, gradual rollouts.
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

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 - Starting from 13:00 UTC June 1, 2026, to 00:17 UTC June 2, 2026, multiple services experienced delayed job processing due to increased latency in our background job queue service. The root cause was insufficient queue processing capacity to handle a large week-over-week increase in total job traffic.

Users saw up to 90 minutes of delay in billing usage updates, 30 minutes of delay for webhook notifications to show, and 15 minutes of delay to see email notifications. Mitigation involved scaling up our background job service capacity to handle the spike in job traffic.

We have added queue capacity monitoring to our background job queue service to stay ahead of weekly growth patterns and to reduce time to detect in the future.
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.

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents