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

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.

Sep 11, 2026

No incidents reported today.

Sep 10, 2026

No incidents reported.

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
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Sep 4, 22:25 UTC
Update - We are applying the mitigation and expect recovery within approximately 30 minutes.
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
Investigating - We are investigating reports of impacted performance for some GitHub services.
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
Investigating - We are investigating reports of impacted performance for some GitHub services.
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
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
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
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
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
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
Update - Time to update pull request diffs have improved to normal thresholds.
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
Investigating - We are investigating reports of degraded performance for Pull Requests
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
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
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
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
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
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Aug 31, 09:15 UTC

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.