Jun <var data-var='date'>25</var>, <var data-var='time'>18:27</var> UTC 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 <var data-var='date'>25</var>, <var data-var='time'>18:27</var> UTC Update - We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered. Jun <var data-var='date'>25</var>, <var data-var='time'>18:07</var> UTC Monitoring - The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>25</var>, <var data-var='time'>17:58</var> UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Jun <var data-var='date'>25</var>, <var data-var='time'>17:53</var> UTC Update - Actions is experiencing degraded availability. We are continuing to investigate. Jun <var data-var='date'>25</var>, <var data-var='time'>17:50</var> UTC Investigating - We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks

Degradation with Webhooks, Pull Requests and Actions

Jun <var data-var='date'>23</var>, <var data-var='time'>23:29</var> UTC Resolved - On June 23, 2026, between 22:45 and 23:29 UTC, GitHub Copilot Completions and Next Edit Suggestions were degraded for users in all regions. During this window, affected users may have seen failed or missing code completions and Next Edit Suggestions. On average about 25% of Completions and Next Edit Suggestions requests failed during the impact window, peaking at roughly 27%. The cause was a configuration change that prevented the Copilot service from obtaining the authentication tokens it needs to reach its model backends; this both failed requests directly and caused the service to temporarily remove backends from rotation. GitHub engineers detected the elevated error rate within minutes, declared an incident, and mitigated the issue at 23:22 UTC by redeploying the service with a known-good configuration, which restored normal operation. As a follow-up, the team disabled the affected authentication path to prevent a future deployment from re-introducing the problem, and is making the change rollout safer. We apologize for the disruption and are taking steps to reduce the likelihood of similar incidents. Jun <var data-var='date'>23</var>, <var data-var='time'>23:27</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>23</var>, <var data-var='time'>23:26</var> UTC Update - We have applied a rollback and are seeing recovery. Jun <var data-var='date'>23</var>, <var data-var='time'>23:04</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

We are seeing elevated errors with Next Edit Suggestions and Completions

Jun <var data-var='date'>17</var>, <var data-var='time'>19:28</var> UTC Resolved - On June 17, 2026, between 16:57 UTC and 19:14 UTC, Copilot code completions were degraded and users were unable to receive Next Edit Suggestions. Standard ghost text code completions were not affected. This was due to a configuration change that caused the service's routing layer to incorrectly discard all Next Edit Suggestion model endpoints as invalid. We mitigated the incident by deploying a corrected configuration change at 18:55 UTC, with full recovery observed at 19:14 UTC. We are working to improve the resilience of our routing layer to limit impact due to a subset of invalid configurations, and to improve our alerting to detect sudden traffic changes that are not captured by standard error rate monitors. Jun <var data-var='date'>17</var>, <var data-var='time'>19:14</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>17</var>, <var data-var='time'>19:09</var> UTC Update - We have applied mitigation and are seeing recovery Jun <var data-var='date'>17</var>, <var data-var='time'>18:40</var> UTC Update - We have identified a likely cause and are applying a mitigation Jun <var data-var='date'>17</var>, <var data-var='time'>17:57</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with Copilot next edit suggestions

Jun <var data-var='date'>17</var>, <var data-var='time'>19:00</var> UTC Resolved - On June 17, 2026, between 11:35 UTC and 19:20 UTC, the Webhooks service was degraded and delivered webhook payloads with missing installation information. On average, 11.3% of webhook deliveries were impacted. Customers relying on the installation field for authentication or routing were unable to process affected webhooks. A smaller subset of deliveries for the security_advisory event (0.04%) were delivered successfully but were not recorded for redelivery. This was due to a defect in a new delivery code path that failed to include installation data in webhook payloads. We mitigated the incident by disabling the feature flag controlling the new code path. We are working to improve our automated validation of webhook payloads, and introduce automated alerting for webhook payload regressions to reduce our time to detection and mitigation of issues like this one in the future. The following events were affected: branch_protection_configuration, code_scanning_alert, commit_comment, custom_property, custom_property_values, dependabot_alert, deploy_key, deployment_protection_rule, deployment_review, dismissal_request_code_scanning, dismissal_request_secret_scanning, installation_target, member, membership, merge_queue_entry, org_block, organization, projects_v2, projects_v2_item, pull_request_review_thread, repository_ruleset, secret_scanning_alert, secret_scanning_alert_location, secret_scanning_scan, security_and_analysis, star, sub_issues, team, team_add, workflow_job.

Incident With Webhooks

Jun <var data-var='date'>17</var>, <var data-var='time'>04:44</var> UTC 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 <var data-var='date'>17</var>, <var data-var='time'>04:44</var> UTC Monitoring - Copilot is operating normally. Jun <var data-var='date'>17</var>, <var data-var='time'>04:26</var> UTC Update - We've applied a mitigation to unblock Copilot functionality. Users may start to see signs of recovery. Relaunching your client should accelerate signs of recovery. We will continue to monitor the situation. Jun <var data-var='date'>17</var>, <var data-var='time'>03:52</var> UTC Update - We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible. Jun <var data-var='date'>17</var>, <var data-var='time'>03:50</var> UTC Investigating - We are investigating reports of degraded availability for Copilot

Incident with Copilot Availability

Jun <var data-var='date'>16</var>, <var data-var='time'>18:15</var> UTC Resolved - On June 16, 2026, between 17:20 UTC and 18:15 UTC, the Opus 4.8 model experienced degraded availability in GitHub Copilot. During this window, some requests to Opus 4.8 failed or errored. Other Copilot models were not affected and remained available as alternatives. This was caused by an issue with an upstream model provider. The upstream provider resolved the issue, and we monitored Opus 4.8 until success rates returned to normal. The incident is fully resolved. Jun <var data-var='date'>16</var>, <var data-var='time'>18:14</var> UTC Update - The issues with our upstream model provider have been resolved, and Opus 4.8 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete. Jun <var data-var='date'>16</var>, <var data-var='time'>18:00</var> UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>16</var>, <var data-var='time'>17:47</var> UTC Update - We are experiencing degraded availability for the Opus 4.8 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 <var data-var='date'>16</var>, <var data-var='time'>17:45</var> UTC Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers

Disruption with some GitHub services

Jun <var data-var='date'>15</var>, <var data-var='time'>19:10</var> UTC Resolved - Between 17:38 UTC and 18:22 UTC on June 15, 2026, approximately 83% of requests to the analytics endpoint serving the /chronicle feature failed.  The cause was an internal feature-flag service that encountered a transient error and failed to recover, causing feature flag checks to fail. The analytics endpoint was gated behind one of these flags, resulting in requests being rejected. We restored service health by removing the feature flag gating the analytics endpoint and deploying that change. To avoid recurrence of similar incidents, we have changed the feature-flag client so that errors that are not known to be permanent are retried, and we are improving alerting and startup behavior so this class of failure is detected and recovered from faster. Jun <var data-var='date'>15</var>, <var data-var='time'>19:10</var> UTC Update - We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services. Customers may have experienced failed requests or degraded functionality. A fix has been deployed and error rates are steadily decreasing. All affected services are now mitigated and we are monitoring recovery. Jun <var data-var='date'>15</var>, <var data-var='time'>19:02</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>15</var>, <var data-var='time'>18:32</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Multiple services have elevated errors and endpoint failures when checking feature flags

Jun <var data-var='date'>15</var>, <var data-var='time'>17:37</var> UTC Resolved - On June 15, 2026, between 15:27 UTC and 16:23 UTC, GitHub webhook deliveries were delayed. During this window, webhook events were delivered later than normal, with average end-to-end delivery latency peaking at approximately 8.8 minutes. No webhook deliveries were lost — delayed events were queued and delivered once processing recovered. This was caused by a temporary throughput constraint in an internal event-processing system that moves webhook events through GitHub's delivery pipeline. The rate at which events were processed for delivery dropped below the incoming volume, creating a backlog. We restarted the affected pipeline service, after which throughput recovered and the backlog fully drained by approximately 16:29 UTC. Webhook delivery latency returned to normal, the incident was mitigated at 16:39 UTC, and fully resolved at 17:37 UTC. To reduce the likelihood and impact of similar incidents, we are working on improving the accuracy of the utilization metrics used to scale our delivery worker pools, reviewing connection and capacity headroom in the delivery pipeline. Jun <var data-var='date'>15</var>, <var data-var='time'>16:39</var> UTC Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>15</var>, <var data-var='time'>16:39</var> UTC Update - Webhooks delivery latency has returned to normal levels. The backlog that built up during the incident has been cleared at approximately 4:29 UTC. We consider this incident resolved. Jun <var data-var='date'>15</var>, <var data-var='time'>15:37</var> UTC Investigating - We are investigating reports of degraded performance for Webhooks

Increased latency with webhooks

Jun <var data-var='date'>11</var>, <var data-var='time'>22:19</var> UTC Resolved - On June 11, 2026, between 19:28 UTC and 21:06 UTC, GitHub webhook deliveries were delayed. Average delivery latency peaked at approximately 3.4 minutes, with some deliveries delayed by as much as 62 minutes at the 99th percentile. No events were lost — delayed events were queued and delivered once processing caught up. This was due to a change in how webhook traffic was distributed across regions: to relieve load on one region, a portion of processing was shifted to another, where higher latency prevented our delivery workers from keeping pace with incoming volume, creating a backlog. We mitigated the incident by rebalancing webhook traffic distribution; as load returned to normal levels, processing caught up and the delivery backlog fully drained. We are working on improving the accuracy of the utilization metrics used to scale our delivery worker pools, and reassess how we distribute webhook traffic across regions, to reduce our time to detection and mitigation of issues like this one in the future. Jun <var data-var='date'>11</var>, <var data-var='time'>20:00</var> UTC Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>11</var>, <var data-var='time'>19:58</var> UTC Update - We have applied a mitigation and are monitoring for recovery. Jun <var data-var='date'>11</var>, <var data-var='time'>19:42</var> UTC Update - We are currently experiencing delays in Web Hook delivery and are actively investigating the root cause. Jun <var data-var='date'>11</var>, <var data-var='time'>19:42</var> UTC Investigating - We are investigating reports of degraded performance for Webhooks

Incident with Webhooks

Jun <var data-var='date'>10</var>, <var data-var='time'>16:39</var> UTC Resolved - Between 15:05 UTC and 16:25 UTC, GitHub API services experienced degraded availability due to sporadic authentication failures affecting approximately 9% of requests. Customers experienced intermittent "logged out" behavior as erroneous 401 responses triggered repeated authentication flows in app integrations. Affected requests also experienced approximately 800ms of additional latency. A memcached proxy service rollout to our internal API infrastructure caused our authentication service to pick up an incorrect memcached host configuration, leading to intermittent authentication lookup failures. We mitigated the incident by deploying a configuration change to memcached to use the correct host. To prevent similar issues in the future, we plan to migrate our authentication system to the new memcached infrastructure to improve resilience and strengthen overall reliability posture. Jun <var data-var='date'>10</var>, <var data-var='time'>16:37</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>10</var>, <var data-var='time'>16:36</var> UTC Update - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>10</var>, <var data-var='time'>16:21</var> 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 <var data-var='date'>10</var>, <var data-var='time'>15:46</var> UTC Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'>10</var>, <var data-var='time'>15:46</var> 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 <var data-var='date'>10</var>, <var data-var='time'>15:27</var> 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 <var data-var='date'>10</var>, <var data-var='time'>15:27</var> UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Jun <var data-var='date'>10</var>, <var data-var='time'>15:23</var> UTC Update - API Requests is experiencing degraded availability. We are continuing to investigate. Jun <var data-var='date'>10</var>, <var data-var='time'>15:20</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Authentication issues related to API requests

Jun <var data-var='date'> 8</var>, <var data-var='time'>15:00</var> UTC 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.

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

Jun <var data-var='date'> 8</var>, <var data-var='time'>10:03</var> UTC Resolved - On June 8, 2026, between 08:40 UTC and 09:30 UTC, the Claude Opus 4.7 model experienced degraded availability with error rates peaking at 8.4% and averaging 1.9%. This was due to an upstream provider issue that caused temporary unavailability and rate limiting on secondary failover systems. Users selecting Auto or alternative models were unaffected. We are improving provider failover mechanisms and monitoring to prevent similar issues. Jun <var data-var='date'> 8</var>, <var data-var='time'>09:49</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>09:08</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>09:05</var> UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers

Disruption with Claude Opus 4.7

Jun <var data-var='date'> 8</var>, <var data-var='time'>08:36</var> UTC Resolved - On June 8, 2026, between approximately 06:30 UTC and 08:36 UTC, signed-out users experienced sustained elevated HTTP 504 errors when accessing Pull Requests, Issues, releases, patch diffs, and other related GitHub.com pages. During the incident, approximately 17% of unauthenticated requests to the affected GitHub.com endpoints returned gateway timeout errors, peaking at roughly 34% of requests at around 06:50 UTC. Some GitHub Actions workflows were also affected when they depended on release downloads or related GitHub.com endpoints. The impact lasted approximately two hours and was isolated to unauthenticated traffic; signed-in users were not affected. The issue was caused by a significant increase in abusive traffic to specific GitHub.com endpoints. This degraded our ability to respond to unauthenticated requests, causing requests to queue beyond timeout thresholds and return gateway timeout errors. We mitigated the incident by identifying the anomalous traffic pattern and applying targeted blocks at the load balancer and application layers. Error rates returned to normal and affected services were fully restored by 08:36 UTC. To reduce the likelihood and impact of similar incidents in the future, we are improving automated detection and blocking for these traffic patterns, improving our emergency traffic-blocking deployment path, and evaluating routing changes for endpoints used by both signed-out users and automated workflows. Jun <var data-var='date'> 8</var>, <var data-var='time'>08:35</var> UTC Monitoring - The degradation affecting Actions, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'> 8</var>, <var data-var='time'>08:27</var> UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. Jun <var data-var='date'> 8</var>, <var data-var='time'>08:13</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>07:32</var> UTC Update - Pull Requests is experiencing degraded performance. We are continuing to investigate. Jun <var data-var='date'> 8</var>, <var data-var='time'>07:31</var> UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Jun <var data-var='date'> 8</var>, <var data-var='time'>07:14</var> UTC Update - Issues is experiencing degraded availability. We are continuing to investigate. Jun <var data-var='date'> 8</var>, <var data-var='time'>07:11</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Pull Requests and Issues unavailable for signed-out users

Jun <var data-var='date'> 6</var>, <var data-var='time'>18:49</var> UTC 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 <var data-var='date'> 6</var>, <var data-var='time'>18:48</var> UTC Update - All work has been completed and we are hands off. Jun <var data-var='date'> 6</var>, <var data-var='time'>15:36</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'> 6</var>, <var data-var='time'>15:31</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>15:31</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

EU Network Maintenance

Jun <var data-var='date'> 6</var>, <var data-var='time'>17:07</var> UTC 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 <var data-var='date'> 6</var>, <var data-var='time'>16:56</var> UTC Update - Packages is experiencing degraded performance. We are continuing to investigate. Jun <var data-var='date'> 6</var>, <var data-var='time'>16:53</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with some GitHub services in the EU region

Jun <var data-var='date'> 5</var>, <var data-var='time'>22:21</var> UTC 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 <var data-var='date'> 5</var>, <var data-var='time'>22:21</var> UTC Update - Affected Slack and Teams subscriptions have been restored. Please contact support if you encounter any additional issues. Jun <var data-var='date'> 5</var>, <var data-var='time'>20:34</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>18:43</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>18:05</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'> 5</var>, <var data-var='time'>18:04</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>17:25</var> UTC Update - Customers may see unexpected repo unsubscription events in their Slack or Teams channels. Jun <var data-var='date'> 5</var>, <var data-var='time'>17:20</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

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

Jun <var data-var='date'> 4</var>, <var data-var='time'>19:59</var> UTC 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 <var data-var='date'> 4</var>, <var data-var='time'>19:59</var> UTC Update - This issue is now fully resolved and Copilot Code Review is working as expected. Jun <var data-var='date'> 4</var>, <var data-var='time'>19:41</var> 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 <var data-var='date'> 4</var>, <var data-var='time'>19:07</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'> 4</var>, <var data-var='time'>19:07</var> 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 <var data-var='date'> 4</var>, <var data-var='time'>18:52</var> UTC Update - The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery. Jun <var data-var='date'> 4</var>, <var data-var='time'>18:22</var> 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 <var data-var='date'> 4</var>, <var data-var='time'>18:03</var> 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 <var data-var='date'> 4</var>, <var data-var='time'>18:02</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Copilot Code Review Failing

Jun <var data-var='date'> 4</var>, <var data-var='time'>04:11</var> UTC 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 <var data-var='date'> 4</var>, <var data-var='time'>04:11</var> 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 <var data-var='date'> 4</var>, <var data-var='time'>02:37</var> 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 <var data-var='date'> 4</var>, <var data-var='time'>02:35</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'> 3</var>, <var data-var='time'>23:38</var> UTC Update - We have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates. Next update in 12 hours. Jun <var data-var='date'> 3</var>, <var data-var='time'>21:10</var> UTC Update - We are preparing a mitigation for the delayed Dependabot scheduled version updates. Next update in 2 hours. Jun <var data-var='date'> 3</var>, <var data-var='time'>20:18</var> 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 <var data-var='date'> 3</var>, <var data-var='time'>19:43</var> 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 <var data-var='date'> 3</var>, <var data-var='time'>19:42</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Jun <var data-var='date'> 3</var>, <var data-var='time'>06:46</var> UTC 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 <var data-var='date'> 3</var>, <var data-var='time'>06:45</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Jun <var data-var='date'> 3</var>, <var data-var='time'>06:02</var> UTC Update - We are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation. Jun <var data-var='date'> 3</var>, <var data-var='time'>03:45</var> UTC Update - We are investigating reports of impacted performance for some GitHub services. --- Relevant stamps: dotcom Jun <var data-var='date'> 3</var>, <var data-var='time'>03:13</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Jun <var data-var='date'> 2</var>, <var data-var='time'>00:17</var> UTC 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 <var data-var='date'> 1</var>, <var data-var='time'>21:59</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>19:27</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>18:48</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>17:28</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>16:42</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>15:43</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>15:17</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>15:17</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Delays with Code Scanning and Billing

May <var data-var='date'>28</var>, <var data-var='time'>20:41</var> UTC 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 <var data-var='date'>28</var>, <var data-var='time'>20:06</var> UTC Update - Open AI models are currently unavailable. We are shifting requests to other models to reduce impact. May <var data-var='date'>28</var>, <var data-var='time'>19:40</var> UTC Update - We are investigating errors with Copilot requests using OpenAI models May <var data-var='date'>28</var>, <var data-var='time'>19:20</var> UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate. May <var data-var='date'>28</var>, <var data-var='time'>19:01</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with OpenAI Models

May <var data-var='date'>28</var>, <var data-var='time'>19:07</var> UTC 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.

Elevated error rates across multiple services

May <var data-var='date'>28</var>, <var data-var='time'>01:32</var> UTC 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 <var data-var='date'>28</var>, <var data-var='time'>01:27</var> UTC Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. May <var data-var='date'>28</var>, <var data-var='time'>01:13</var> UTC Investigating - We are investigating reports of degraded performance for Webhooks

Webhook APIs and UI Degraded

May <var data-var='date'>27</var>, <var data-var='time'>13:16</var> UTC 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 <var data-var='date'>27</var>, <var data-var='time'>12:54</var> UTC Update - We're continuing to investigate degraded performance of Git operations, Issues and Pull requests. May <var data-var='date'>27</var>, <var data-var='time'>12:10</var> UTC Investigating - We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests

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

May <var data-var='date'>26</var>, <var data-var='time'>16:35</var> UTC 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 <var data-var='date'>26</var>, <var data-var='time'>16:24</var> UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. May <var data-var='date'>26</var>, <var data-var='time'>15:48</var> UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate. May <var data-var='date'>26</var>, <var data-var='time'>15:44</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Is Github down?

Github status is UP

Lastest published events

Degradation with Webhooks, Pull Requests and Actions

We are seeing elevated errors with Next Edit Suggestions and Completions

Disruption with Copilot next edit suggestions

Github Services, Components and Regions

Recent Github events

Degradation with Webhooks, Pull Requests and Actions

We are seeing elevated errors with Next Edit Suggestions and Completions

Disruption with Copilot next edit suggestions

Incident With Webhooks

Incident with Copilot Availability

Disruption with some GitHub services

Get your FREE account now,
5 monitors included!

Is Github down?

Github status is UP

Lastest published events

Degradation with Webhooks, Pull Requests and Actions

We are seeing elevated errors with Next Edit Suggestions and Completions

Disruption with Copilot next edit suggestions

Github Services, Components and Regions

Recent Github events

Degradation with Webhooks, Pull Requests and Actions

We are seeing elevated errors with Next Edit Suggestions and Completions

Disruption with Copilot next edit suggestions

Incident With Webhooks

Incident with Copilot Availability

Disruption with some GitHub services

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!