GitHub Status

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 17, 19:28 UTC

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

Update - We have applied mitigation and are seeing recovery
Jun 17, 19:09 UTC

Update - We have identified a likely cause and are applying a mitigation
Jun 17, 18:40 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 17, 17:57 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.

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 17, 04:44 UTC

Monitoring - Copilot is operating normally.
Jun 17, 04:44 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 17, 04:26 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 17, 03:52 UTC

Investigating - We are investigating reports of degraded availability for Copilot
Jun 17, 03:50 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 16, 18:15 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.

Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Jun 16, 18:00 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 16, 17:47 UTC

Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers
Jun 16, 17:45 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 15, 19:10 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 15, 19:10 UTC

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

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 15, 18:32 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 15, 17:37 UTC

Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 15, 16:39 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 15, 16:39 UTC

Investigating - We are investigating reports of degraded performance for Webhooks
Jun 15, 15:37 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 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

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.

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

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.

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

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.

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

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

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.

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

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.

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