ÍNDICE Help Community Status GitHub.com Features Enterprise Copilot Security Pricing Team Resources Roadmap Compare GitHub Developer API Partners Education GitHub CLI GitHub Desktop GitHub Mobile Docs Community Forum Professional Services Skills Contact GitHub  | www.githubstatus.com https://www.githubstatus.com/[GitHub header][GitHub header] x Get email notifications whenever GitHub creates, updates or resolves an incident. Email address: Enter OTP: Resend OTP in: seconds Didn't receive the OTP? Resend OTP By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.Get text message notifications whenever GitHub creates or resolves an incident. Country code: Afghanistan (+93)Albania (+355)Algeria (+213)American Samoa (+1)Andorra (+376)Angola (+244)Anguilla (+1)Antigua and Barbuda (+1)Argentina (+54)Armenia (+374)Aruba (+297)Australia/Cocos/Christmas Island (+61)Austria (+43)Azerbaijan (+994)Bahamas (+1)Bahrain (+973)Bangladesh (+880)Barbados (+1)Belarus (+375)Belgium (+32)Belize (+501)Benin (+229)Bermuda (+1)Bolivia (+591)Bosnia and Herzegovina (+387)Botswana (+267)Brazil (+55)Brunei (+673)Bulgaria (+359)Burkina Faso (+226)Burundi (+257)Cambodia (+855)Cameroon (+237)Canada (+1)Cape Verde (+238)Cayman Islands (+1)Central Africa (+236)Chad (+235)Chile (+56)China (+86)Colombia (+57)Comoros (+269)Congo (+242)Congo, Dem Rep (+243)Costa Rica (+506)Croatia (+385)Cyprus (+357)Czech Republic (+420)Denmark (+45)Djibouti (+253)Dominica (+1)Dominican Republic (+1)Egypt (+20)El Salvador (+503)Equatorial Guinea (+240)Estonia (+372)Ethiopia (+251)Faroe Islands (+298)Fiji (+679)Finland/Aland Islands (+358)France (+33)French Guiana (+594)French Polynesia (+689)Gabon (+241)Gambia (+220)Georgia (+995)Germany (+49)Ghana (+233)Gibraltar (+350)Greece (+30)Greenland (+299)Grenada (+1)Guadeloupe (+590)Guam (+1)Guatemala (+502)Guinea (+224)Guyana (+592)Haiti (+509)Honduras (+504)Hong Kong (+852)Hungary (+36)Iceland (+354)India (+91)Indonesia (+62)Iraq (+964)Ireland (+353)Israel (+972)Italy (+39)Jamaica (+1)Japan (+81)Jordan (+962)Kenya (+254)Korea, Republic of (+82)Kosovo (+383)Kuwait (+965)Kyrgyzstan (+996)Laos (+856)Latvia (+371)Lebanon (+961)Lesotho (+266)Liberia (+231)Libya (+218)Liechtenstein (+423)Lithuania (+370)Luxembourg (+352)Macao (+853)Macedonia (+389)Madagascar (+261)Malawi (+265)Malaysia (+60)Maldives (+960)Mali (+223)Malta (+356)Martinique (+596)Mauritania (+222)Mauritius (+230)Mexico (+52)Monaco (+377)Mongolia (+976)Montenegro (+382)Montserrat (+1)Morocco/Western Sahara (+212)Mozambique (+258)Namibia (+264)Nepal (+977)Netherlands (+31)New Zealand (+64)Nicaragua (+505)Niger (+227)Nigeria (+234)Norway (+47)Oman (+968)Pakistan (+92)Palestinian Territory (+970)Panama (+507)Paraguay (+595)Peru (+51)Philippines (+63)Poland (+48)Portugal (+351)Puerto Rico (+1)Qatar (+974)Reunion/Mayotte (+262)Romania (+40)Russia/Kazakhstan (+7)Rwanda (+250)Samoa (+685)San Marino (+378)Saudi Arabia (+966)Senegal (+221)Serbia (+381)Seychelles (+248)Sierra Leone (+232)Singapore (+65)Slovakia (+421)Slovenia (+386)South Africa (+27)Spain (+34)Sri Lanka (+94)St Kitts and Nevis (+1)St Lucia (+1)St Vincent Grenadines (+1)Sudan (+249)Suriname (+597)Swaziland (+268)Sweden (+46)Switzerland (+41)Taiwan (+886)Tajikistan (+992)Tanzania (+255)Thailand (+66)Togo (+228)Tonga (+676)Trinidad and Tobago (+1)Tunisia (+216)Turkey (+90)Turks and Caicos Islands (+1)Uganda (+256)Ukraine (+380)United Arab Emirates (+971)United Kingdom (+44)United States (+1)Uruguay (+598)Uzbekistan (+998)Venezuela (+58)Vietnam (+84)Virgin Islands, British (+1)Virgin Islands, U.S. (+1)Yemen (+967)Zambia (+260)Zimbabwe (+263) Phone number: Enter OTP: Resend OTP in: 30 seconds Didn't receive the OTP? Resend OTP Message and data rates may apply. By subscribing you agree to our Privacy Policy, the Atlassian Terms of Service, and the Atlassian Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via SlackBy subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy. Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status. Webhook URL: The URL we should send the webhooks to Email address: We'll send you email if your endpoint fails By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.Visit our support site. Get the Atom Feed or RSS Feed. All Systems Operational
Check GitHub Enterprise Cloud status by region:
Uptime over the past 90 days. View historical uptime. Git Operations ? Operational Webhooks ? Operational Visit www.githubstatus.com for more information Operational API Requests ? Operational Issues ? Operational Pull Requests ? Operational Actions ? Operational Packages ? Operational Pages ? Operational Copilot Operational Codespaces ? Operational Copilot AI Model Providers Operational Operational Degraded Performance Partial Outage Major Outage Maintenance Major outage Partial outage No downtime recorded on this day. No data exists for this day. had a major outage. had a partial outage. Related No incidents or maintenance related to this downtime. Past Incidents Sep 2, 2026 No incidents reported today. Sep 1, 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. Update -
Time to update pull request diffs have improved to normal thresholds. Update -
Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources. Investigating -
We are investigating reports of degraded performance for Pull Requests Aug 31, 2026 Elevated rate of errors for OpenAI models provided by Copilot 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. Update -
The issues with our upstream model provider have been resolved, and gpt-5.3-codex, gpt-5.4-mini, gpt-5.4-nano, gpt-5.5, and the gpt-5.6 family of models are once again available in Copilot products and IDE surfaces. Monitoring -
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Update -
One of our model providers has confirmed an incident on their end. We have provided them details to help identify the issue. We are starting to see recovery. Update -
Copilot is experiencing a higher rate of errors for OpenAI models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4, and the gpt-5.6 family of models. Other models are not impacted. Investigating -
We are investigating reports of degraded performance for Copilot AI Model Providers Aug 30, 2026 No incidents reported. Aug 29, 2026 No incidents reported. Aug 28, 2026 No incidents reported. Aug 27, 2026 Disruption with GitHub Billing Resolved -
On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers ( Update -
No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause. Update -
Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since the previous update. We will provide another update as the investigation progresses. Update -
Our mitigation is still holding as we continue to investigate to find the root cause. Update -
We are continuing to monitor the mitigation that we have applied for the billing page disruption. Update -
We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered. Update -
We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions. Investigating -
We are investigating reports of impacted performance for some GitHub services. Incident with Copilot AI Model Providers Resolved -
On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. Update -
The issues with our upstream model provider have been mitigated, and Kimi K3 is once again available in Copilot products and IDE surfaces. Update -
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate. Update -
We are experiencing degraded availability for the Kimi K3 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. Investigating -
We are investigating reports of degraded availability for Copilot AI Model Providers Incident with Actions and Pull Requests Resolved -
On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. Monitoring -
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability. Update -
We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health. Update -
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving. Update -
We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more. Investigating -
We are investigating reports of degraded performance for Actions and Pull Requests Aug 26, 2026 Resolved -
On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database primary used by the service processing triggers for Actions workflows. The primary was failed over, but the system did not fully recover. The saturation was caused by growing daily peak load combined with an upstream issue in GitHub’s event processing infrastructure, https://www.githubstatus.com/incidents/hcbtzksccj2f, which caused burst amplification of already-high load. Downstream throttles that were later used to recover were set ~10% too high to protect the system. Update -
All inbound queues have recovered and Actions is operating as expected. 3.7% of jobs assigned to larger runners during the early stage of this incident are stuck waiting for runner assignment. Those will be canceled within the hour. Other runners are successfully processing all new jobs. Monitoring -
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Update -
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits. Update -
We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour. Update -
Pages is operating normally. Update -
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up. Update -
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues Update -
We've identified an issue with a database primary and are failing over to a replica immediately Update -
Pages is experiencing degraded performance. We are continuing to investigate. Investigating -
We are investigating reports of degraded availability for Actions Disruption with some GitHub services Resolved -
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/y1t7p9fzrlj2 Investigating -
We are investigating reports of impacted performance for some GitHub services. Aug 25, 2026 No incidents reported. Aug 24, 2026 Actions delays in starting runs Resolved -
On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. Monitoring -
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Update -
Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery. Investigating -
We are investigating reports of degraded performance for Actions Elevated errors on Fable 5 due to upstream provider Resolved -
On August 24th, 2026, between approximately 06:35 and 07:25 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates when using Claude Fable 5, with requests sometimes failing mid-response. No other models were impacted. Update -
We are experiencing degraded availability for the Fable model in Copilot products and IDE surfaces. This is due to an issue with the upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot. Investigating -
We are investigating reports of degraded availability for Copilot AI Model Providers Aug 23, 2026 No incidents reported. Aug 22, 2026 No incidents reported. Aug 21, 2026 Degraded Git Operations over SSH Resolved -
On August 21, 2026, between 14:00 and 14:07 UTC, dotcom Git operations over SSH were degraded. Successful Git operations over SSH fell by more than 95% for during the peak impact window, making clone, fetch, or push over SSH effectively unavailable to most users for approximately four minutes. Git operations over HTTPS were not affected. Intermittent failures creating agent tasks Resolved -
Between 13:57 UTC on August 20 and 00:37 UTC on August 21, 2026, some users of the Copilot Cloud Agent experienced delays of up to 60 to 90 minutes in seeing the status and results of their agent tasks. The agent tasks themselves continued to run and complete during this time; only the visibility of their status was delayed. Update -
We are seeing gradual recovery in Copilot Cloud Agent task status visibility as we deploy a fix for the root cause. Session output remains delayed by approximately one hour while remediation continues. Update -
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility. Session output continues to be delayed by approximately 1 hour as our remediation steps take effect. Update -
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and expect this to take effect within the next hour. Update -
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact. Update -
We are observing gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact. Update -
We are seeing signs of recovery for Copilot Cloud Agent task status visibility, but this recovery is slower than anticipated. We are pursuing additional mitigating measures to accelerate recovery. Update -
Users are experiencing delays when starting tasks using Copilot Cloud Agent and are not be able to see the status of these tasks. Copilot Cloud Agent tasks are still being completed. We have identified the cause of the issue and are putting mitigations in place to return service to normal levels. We will provide another update about the expected recovery time shortly. Update -
We are experiencing issues with Copilot Cloud Agent tasks, resulting in newly started tasks not properly displaying on-going progress. These Copilot Cloud Agent tasks are still being completed correctly but lack proper visibility. We are actively investigating the issue and will provide updates as we learn more. Update -
We have identified the problematic component and are working to fail over to a healthy instance. Further updates will be provided as we perform mitigations. Update -
Users may experience delays when starting tasks using Copilot Cloud Agent. We are actively investigating the issue and will provide updates as we learn more. Investigating -
We are investigating reports of impacted performance for some GitHub services. Aug 20, 2026 Aug 19, 2026 No incidents reported. ← Incident HistoryPowered by Atlassian Statuspage [GitHub footer] Get tips, technical guides, and best practices. Twice a month. Right in your inbox. Subscribe |
desde el 12/06/1996 · Última actualización: 02/09/2026 · [inicio] · Convertido a HTML 3.2 por el proxy rebajador de Bivid Dial-Up · [ver la versión reinterpretada por IA]
