All Systems Operational
About This Site
Check GitHub Enterprise Cloud status by region:
- Australia: au.githubstatus.com
- EU: eu.githubstatus.com
- Japan: jp.githubstatus.com
- US: us.githubstatus.com
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 10, 2026
No incidents reported today.
Sep 9, 2026
No incidents reported.
Sep 8, 2026
No incidents reported.
Sep 7, 2026
No incidents reported.
Sep 6, 2026
No incidents reported.
Sep 5, 2026
No incidents reported.
Sep 4, 2026
Resolved -
On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments.
The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC.
We apologize for the disruption.
Sep 4, 22:26 UTC
The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC.
We apologize for the disruption.
Sep 4, 22:26 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Sep 4, 22:25 UTC
Sep 4, 22:25 UTC
Update -
We are applying the mitigation and expect recovery within approximately 30 minutes.
Sep 4, 21:54 UTC
Sep 4, 21:54 UTC
Update -
Some users may be experiencing failures when using Copilot code review. We have identified the root cause and are working on a mitigation.
Sep 4, 20:57 UTC
Sep 4, 20:57 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Sep 4, 20:39 UTC
Sep 4, 20:39 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.
Sep 4, 22:23 UTC
Sep 4, 22:23 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Sep 4, 22:02 UTC
Sep 4, 22:02 UTC
Sep 3, 2026
Resolved -
Between 13:22 and 17:11 UTC on September 03, 2026, GitHub Copilot experienced degradation affecting several Grok models, including Grok 4.5 and Grok 4.6. Users encountered elevated error rates, but other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.
Sep 3, 17:11 UTC
Sep 3, 17:11 UTC
Update -
The issues with our upstream model provider have been resolved, and Grok models are once again available in Copilot products and IDE surfaces.
We will continue monitoring to ensure stability, but mitigation is complete.
Sep 3, 17:11 UTC
We will continue monitoring to ensure stability, but mitigation is complete.
Sep 3, 17:11 UTC
Update -
The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.
Sep 3, 14:22 UTC
Sep 3, 14:22 UTC
Update -
We are experiencing degraded availability for the Grok 4.6 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.
Sep 3, 14:20 UTC
Sep 3, 14:20 UTC
Investigating -
We are investigating reports of degraded performance for Copilot AI Model Providers
Sep 3, 14:17 UTC
Sep 3, 14:17 UTC
Sep 2, 2026
No incidents reported.
Sep 1, 2026
Resolved -
On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The incident was caused by a sharp, concentrated surge in push volume that saturated worker pools and job queueing infrastructure. Autoscaling did not increase capacity as intended, so the backlog did not clear on its own.
The incident was mitigated by manually scaling the affected worker pools and increasing push-processing capacity. This allowed the system to process the backlog, after which refresh times returned to normal. To reduce the likelihood and impact of similar incidents, we are adding quotas and throttling earlier in the push path so a single concentrated source of load cannot saturate shared capacity, improving worker-pool autoscaling so capacity is added automatically, and improving monitors for background job processing so on-call is paged before customers experience delayed pull request updates.
Sep 1, 16:01 UTC
The incident was mitigated by manually scaling the affected worker pools and increasing push-processing capacity. This allowed the system to process the backlog, after which refresh times returned to normal. To reduce the likelihood and impact of similar incidents, we are adding quotas and throttling earlier in the push path so a single concentrated source of load cannot saturate shared capacity, improving worker-pool autoscaling so capacity is added automatically, and improving monitors for background job processing so on-call is paged before customers experience delayed pull request updates.
Sep 1, 16:01 UTC
Update -
Time to update pull request diffs have improved to normal thresholds.
Sep 1, 16:00 UTC
Sep 1, 16:00 UTC
Update -
Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
Sep 1, 15:00 UTC
Sep 1, 15:00 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests
Sep 1, 15:00 UTC
Sep 1, 15:00 UTC
Aug 31, 2026
Resolved -
Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and interrupted streaming responses. Other models were not affected.
The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.
Aug 31, 09:58 UTC
The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.
Aug 31, 09:58 UTC
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.
We will continue monitoring to ensure stability, but mitigation is complete.
Aug 31, 09:58 UTC
We will continue monitoring to ensure stability, but mitigation is complete.
Aug 31, 09:58 UTC
Monitoring -
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Aug 31, 09:51 UTC
Aug 31, 09:51 UTC
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.
Aug 31, 09:48 UTC
Aug 31, 09:48 UTC
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.
Aug 31, 09:22 UTC
Aug 31, 09:22 UTC
Investigating -
We are investigating reports of degraded performance for Copilot AI Model Providers
Aug 31, 09:15 UTC
Aug 31, 09:15 UTC
Aug 30, 2026
No incidents reported.
Aug 29, 2026
No incidents reported.
Aug 28, 2026
No incidents reported.
Aug 27, 2026
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 (
This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure.
We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.
Aug 27, 19:44 UTC
This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure.
We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.
Aug 27, 19:44 UTC
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.
Aug 27, 17:58 UTC
Aug 27, 17:58 UTC
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.
Aug 27, 16:20 UTC
Aug 27, 16:20 UTC
Update -
Our mitigation is still holding as we continue to investigate to find the root cause.
Aug 27, 14:49 UTC
Aug 27, 14:49 UTC
Update -
We are continuing to monitor the mitigation that we have applied for the billing page disruption.
Aug 27, 01:35 UTC
Aug 27, 01:35 UTC
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.
Aug 27, 00:31 UTC
Aug 27, 00:31 UTC
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.
Aug 26, 23:42 UTC
Aug 26, 23:42 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 26, 23:37 UTC
Aug 26, 23:37 UTC
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.
The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.
Aug 27, 12:12 UTC
The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.
Aug 27, 12:12 UTC
Update -
The issues with our upstream model provider have been mitigated, and Kimi K3 is once again available in Copilot products and IDE surfaces.
We will continue monitoring to ensure stability.
Aug 27, 12:12 UTC
We will continue monitoring to ensure stability.
Aug 27, 12:12 UTC
Update -
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
Aug 27, 11:58 UTC
Aug 27, 11:58 UTC
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.
Aug 27, 10:43 UTC
Aug 27, 10:43 UTC
Investigating -
We are investigating reports of degraded availability for Copilot AI Model Providers
Aug 27, 10:04 UTC
Aug 27, 10:04 UTC
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.
Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information.
We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations.
We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.
Aug 27, 00:26 UTC
Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information.
We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations.
We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.
Aug 27, 00:26 UTC
Monitoring -
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
Aug 27, 00:26 UTC
Aug 27, 00:26 UTC
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.
Aug 27, 00:25 UTC
Aug 27, 00:25 UTC
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.
Aug 27, 00:01 UTC
Aug 27, 00:01 UTC
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.
Aug 26, 22:57 UTC
Aug 26, 22:57 UTC
Investigating -
We are investigating reports of degraded performance for Actions and Pull Requests
Aug 26, 22:56 UTC
Aug 26, 22:56 UTC
