GitHub Status

Jul 2, 2025

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jul 2, 10:16 UTC

Update - We are no longer experiencing degradation—Claude Sonnet 4 is once again available in Copilot Chat and across IDE integrations.

We will continue monitoring to ensure stability, but mitigation is complete.
Jul 2, 10:16 UTC

Update - We are experiencing degraded availability for the Claude Sonnet 4 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. Other models are available and working as expected.
Jul 2, 09:55 UTC

Investigating - We are currently investigating this issue.
Jul 2, 09:54 UTC

Jul 1, 2025

No incidents reported.

Jun 30, 2025

Disruption with Claude 3.7 Sonnet in Copilot Chat

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 30, 19:55 UTC

Update - The issues with our upstream model provider have been resolved, and Claude Sonnet 3.7 is once again available in Copilot Chat and across IDE integrations [VSCode, Visual Studio, JetBrains].
We will continue monitoring to ensure stability, but mitigation is complete.
Jun 30, 19:55 UTC

Update - We are experiencing degraded availability for the Claude 3.7 Sonnet 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.

Other models are available and working as expected.
Jun 30, 19:14 UTC

Investigating - We are currently investigating this issue.
Jun 30, 19:13 UTC

Incident With Actions

Resolved - Due to a degradation of one instance of our internal message delivery service, a percentage of jobs started between 06/30/2025 19:18 UTC and 06/30/2025 19:50 UTC failed, and are no longer retry-able. Runners assigned to these jobs will automatically recover within 24 hours, but deleting and recreating the runner will free up the runner immediately.
Jun 30, 19:00 UTC

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

No incidents reported.

Jun 26, 2025

Disruption with some GitHub services

Resolved - On June 26, 2025, between 17:10 UTC and 23:30 UTC, around 40% of attempts to create a repository from a template repository failed. The failures were an unexpected result of a gap in testing and observability.

We mitigated the incident by rolling back the deployment.

We are working to improve our testing and automatic detection of errors associated with failed template repository creation.
Jun 26, 23:33 UTC

Update - We identified an internal change that was causing errors when creating a repository from a template. This change has now been rolled back, and customers should no longer encounter errors when creating repositories from templates.
Jun 26, 23:32 UTC

Update - Users may experience errors when creating a repository from a template. The error message may prompt the user to delete the repository, however this deletion attempt will not be successful. We are investigating the cause of these errors.
Jun 26, 23:05 UTC

Investigating - We are currently investigating this issue.
Jun 26, 23:05 UTC

GitHub Enterprise Importer delays

Resolved - On June 26th, between 14:42UTC and 18:05UTC, the GitHub Enterprise Importer (GEI) service was in a degraded state, during which time, customers of the service experienced extended repository migration durations.

Our investigation found that the combined effect of several database updates resulted in the severe throttling of GEI to preserve overall database health.

We have taken steps to prevent additional impact and are working to implement additional safeguards to prevent similar incidents from occurring in the future.
Jun 26, 18:05 UTC

Update - The earlier delays affecting GitHub Enterprise Importer queries and jobs have now been resolved and are operating normally.
Thank you for your patience while we investigated and addressed the issue.
Jun 26, 18:04 UTC

Update - We're continuing to investigate delays with GitHub Enterprise importer, and are investigating potential delays with queries and jobs.

Next update in 60 minutes.
Jun 26, 16:51 UTC

Update - We're continuing to investigate delays with GitHub Enterprise importer, and are investigating potential delays with infrastructure.

Next update in 60 minutes.
Jun 26, 15:19 UTC

Update - GitHub Enterprise Importer is experiencing degraded throughput, resulting in significant slowdowns in migration processes and extended wait times for customers.
Jun 26, 14:43 UTC

Investigating - We are currently investigating this issue.
Jun 26, 14:42 UTC

Jun 25, 2025

No incidents reported.

Jun 24, 2025

Repository Navigation Bar Missing in GitHub Enterprise Cloud

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 24, 12:26 UTC

Update - We have identified that the navigation bar is missing in GitHub Enterprise Cloud with data residency instances for the repositories related pages and are currently attempting a mitigation.
Jun 24, 11:00 UTC

Investigating - We are currently investigating this issue.
Jun 24, 10:55 UTC

Jun 23, 2025

No incidents reported.

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

Jun 20, 2025

Disruption with the GitHub mobile android application

Resolved - Between June 19th, 2025 11:35 UTC and June 20th, 2025 11:20 UTC the GitHub Mobile Android application was unable to login new users. The iOS app was unaffected.

This was due to a new GitHub App feature being tested internally, which was inadvertently enforced for all GitHub-owned applications, including GitHub Mobile.

A mismatch in client and server expectations due to this feature caused logins to fail. We mitigated the incident by disabling the feature flag controlling the feature.

We are working to improve our time to detection and put in place stronger guardrails that reduce impact from internal testing on applications used by all customers.

Jun 20, 11:20 UTC

Update - We are investigating reports that some users are unable to sign in to the GitHub app on Android. Normal functionality is otherwise available. Our team is actively working to identify the cause.
Jun 20, 10:53 UTC

Investigating - We are currently investigating this issue.
Jun 20, 10:49 UTC

Jun 19, 2025

No incidents reported.

Jun 18, 2025

Disruption with some GitHub services

Resolved - On June 18, 2025 between 22:20 UTC and 23:00 UTC the Claude Sonnet 3.7 and Claude Sonnet 4 models for GitHub Copilot Chat experienced degraded performance. During the impact, some users would receive an immediate error when making a request to a Claude model. This was due to upstream errors with one of our model providers, which have since been resolved. We mitigated the impact by disabling the affected provider endpoints to reduce user impact, redirecting Claude Sonnet requests to additional partners.

We are working to update our incident response playbooks for infrastructure provider outages and improve our monitoring and alerting systems to reduce our time to detection and mitigation of issues like this one in the future.
Jun 18, 23:13 UTC

Update - We are experiencing degraded availability for the Claude 4 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.

Other models are available and working as expected. We recommend using Claude 3.7 as an alternative.
Jun 18, 22:42 UTC

Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Jun 18, 22:40 UTC

Investigating - We are currently investigating this issue.
Jun 18, 22:39 UTC

Partial Actions Cache degradation

Resolved - On June 18, 2025, between 08:21 UTC and 18:47 UTC, some Actions jobs experienced intermittent failures downloading from the Actions Cache service. During the incident, 17% of workflow runs experienced cache download failures, resulting in a warning message in the logs and performance degradation. The disruption was caused by a network issue in our database systems that led to a database replica getting out of sync with the primary. We mitigated the incident by routing cache download url requests to bypass the out-of-sync replica until it was fully restored.

To prevent this class of incidents, we are developing capability in our database system to more robustly bypass out-of-sync replicas. We are also implementing improved monitoring to help us detect similar issues more quickly going forward.
Jun 18, 18:47 UTC

Update - We are continuing to rollout a mitigation and are progressing towards having this rolled out for all customers.
Jun 18, 18:11 UTC

Update - We are currently deploying a mitigation for this issue and will be rolling it out shortly. We will update our progress as we monitor the deployment.
Jun 18, 17:22 UTC

Update - We are actively investigating and working on a mitigation for database instability leading to replication lag in the Actions Cache service. We will continue to post updates on progress towards mitigation.
Jun 18, 17:03 UTC

Update - The actions cache service is experiencing degradation in a number of regions causing cache misses when attempting to download cache entries. This is not causing workflow failures, but workflow runtime might be elevated for certain runs.
Jun 18, 16:46 UTC

Investigating - We are currently investigating this issue.
Jun 18, 16:46 UTC

Partial Degradation in Issues Experience

Resolved - On June 18, 2025, between 15:15 UTC and 19:29 UTC, the Issues service was degraded, and certain GraphQL queries accessing the `ReactionGroup.reactors` field returned errors. Our query routing infrastructure was impacted by exceptions from a particular database migration, resulting in errors for an average of 0.0097% of overall GraphQL requests (peaking at 0.02%).

We mitigated the incident by reverting the migration.

We continue to investigate the cause of the exceptions and are holding off on similar migrations until the underlying issue is understood and resolved.
Jun 18, 17:42 UTC

Update - We have confirmed that we are currently within SLA for Issues experience. Remaining clean up will complete over the next few hours to fully restore the ability to search Issues by reaction as well as related GraphQL API queries.
Jun 18, 17:41 UTC

Update - We have confirmed that impact is restricted to failing to display reactions on some issues and searching issues by reaction. Mitigation is in progress to restore these features and should be fully rolled out to all customers in the next few hours.
Jun 18, 17:07 UTC

Update - Some users are seeing errors when accessing issues on GitHub. We have identified the problem and are working on a revert to restore full functionality.
Jun 18, 16:25 UTC

Investigating - We are investigating reports of degraded performance for Issues
Jun 18, 16:21 UTC

About This Site

Past Incidents