Incident across several services
Update - We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
Sep 23, 2026 - 11:38 UTC
Update - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Sep 23, 2026 - 10:58 UTC
Update - Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
Sep 23, 2026 - 10:57 UTC
Update - Database replicas have detached. We're working to restore the database replicas. Users may experience issues beyond creating organizations and a degraded experience with the GitHub API and Projects.
Sep 23, 2026 - 10:20 UTC
Investigating - We are investigating reports of degraded performance for API Requests
Sep 23, 2026 - 10:11 UTC

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.

No incidents or maintenance related to this downtime.

Sep 23, 2026

Unresolved incident: Incident across several services.

Sep 22, 2026

No incidents reported.

Sep 21, 2026

No incidents reported.

Sep 20, 2026

Incident with Pull Requests
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 20, 23:22 UTC
Update - A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
Sep 20, 22:32 UTC
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Sep 20, 22:27 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Sep 20, 22:13 UTC

Sep 19, 2026

No incidents reported.

Sep 18, 2026

No incidents reported.

Sep 17, 2026

Elevated rate of errors for OpenAI models provided by Copilot
Resolved - Between 20:26 and 21:17 UTC on September 17, 2026, GitHub Copilot experienced degradation affecting several GPT models, including GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-5.3-Codex, and GPT-6 Astra. Users encountered elevated error rates when using these models.

The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.
Sep 17, 21:49 UTC
Monitoring - We are experiencing degraded availability for GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-6 Astra, GPT-5.3-Codex in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. The provider is working to mitigate the problem and we are monitoring recovery. We recommend choosing another model or selecting 'Auto' to continue using Copilot.
Sep 17, 21:39 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Sep 17, 20:59 UTC

Sep 16, 2026

Degradation with Gemini 3.8 Flash
Resolved - On September 16, 2026, between 04:40 and 11:45 UTC, the Gemini 3.8 Flash model in GitHub Copilot experienced degraded availability. Requests to this model failed at an average rate of 6.4%, and the impact was highest during peak traffic hours. Other Copilot models were not affected. Users could continue to work with a different model or with 'Auto'.

The degradation was caused due to a capacity issue with an upstream model provider. Failure rates returned to normal as the daily traffic peak passed. We monitored the model until it was healthy and resolved the incident at 17:48 UTC. We are working to make our systems resilient to cover peak demand for all the Copilot models.
Sep 16, 17:48 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Sep 16, 11:45 UTC
Update - Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
Sep 16, 10:58 UTC
Update - Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
Sep 16, 08:28 UTC
Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers
Sep 16, 07:21 UTC

Sep 15, 2026

Disruption with some GitHub services
Resolved - On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock acquisition, which interrupted the job. We reverted the change to the internal caching service and restored normal operation by 20:00 UTC.

We sincerely apologize for the disruption.
Sep 15, 20:00 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Sep 15, 19:48 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Sep 15, 19:11 UTC
Disruption with some GitHub services
Resolved - On September 15, 2026, between 05:45 and 09:50 UTC, the Claude Fable 5.1 model in GitHub Copilot experienced intermittently degraded availability, with an average error rate of 2.8%. During brief recurring 15 minute periods that recurred every ~45 minutes, availability for Claude Fable 5.1 dropped to a maximum of ~40% before recovering completely. Other Copilot models were not affected. Users could continue to work with a different model or with 'Auto'.

The cause was an issue with an upstream model provider that intermittently rejected requests while overloaded. GitHub worked with the provider, who acknowledged and then resolved the underlying issue at 9:50 UTC, after which the model returned to constant normal availability. Once recovery was guaranteed, we resolved the incident at 11:17 UTC.

To reduce the chance of recurrence and customer impact, GitHub is reviewing per-model availability alerting and automatic in-product fallback so that requests to a degraded model can shift to a healthy alternative more quickly.
Sep 15, 11:17 UTC
Update - The issues with our upstream model provider have been resolved, and Claude Fable 5.1 is once again available in Copilot products and IDE surfaces.

We will continue monitoring to ensure stability, but mitigation is complete.
Sep 15, 11:17 UTC
Update - We continue to monitor intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customer-facing metrics have recovered, and we are awaiting confirmation from our upstream provider that the issue will not recur. Customers can select another model or Auto in the meantime.
Sep 15, 11:09 UTC
Update - We continue to investigate intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customers can use another model or select Auto while we monitor the situation.
Sep 15, 10:32 UTC
Investigating - Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
Sep 15, 10:20 UTC
Monitoring - We are investigating degraded availability for Claude Fable 5.1, affecting some Copilot products and integrated development environments. The issue is caused by a problem with our upstream model provider. Customers can use another model or select Auto while we investigate.
Sep 15, 09:48 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Sep 15, 09:47 UTC

Sep 14, 2026

Actions Larger Runner Jobs for some customers may be slow to start
Resolved - On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, 5.7% of larger-runner jobs were affected.

A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new runners, leaving insufficient runner capacity to start affected jobs promptly.

We restored normal provisioning by correcting the affected capacity records. We have fixed the underlying capacity-selection bug to prevent this failure from recurring. We have also added alerts for VM-record creation failures associated with this capacity issue.
Sep 14, 19:35 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Sep 14, 19:01 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Sep 14, 18:40 UTC

Sep 13, 2026

Incident with several GitHub Services
Resolved - On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications, Code Scanning, Git LFS, and new account signup. At peak, 8.8% of requests to create GitHub App installation access tokens failed. Token issuance for Actions workflows was also affected, impacting approximately 4% of workflows during the incident time frame. Creating issues through the web interface failed for about 96% of attempts, and signup failures were above 90%.

The cause was an internal data-cleanup job that began writing to a shared database cluster at 07:33 UTC. That cluster stores permission data read on nearly every authenticated request. The safeguard that was pacing the background job watched only one health signal — how far the database replicas were lagging — and that signal stayed low the whole time. It did not account for the load building on the primary itself, so the job kept writing while the primary quietly ran toward its limit.

When the primary ran out of available connections, requests that needed it could not complete. First, there was no quick timeout on these database calls, so request handlers waited on the stalled database instead of failing fast, and the shared request-handling capacity degraded into site-wide errors. Second, a retry loop around token creation kept re-sending the writes that were already failing, which held the database saturated rather than letting it recover.

Monitoring declared the incident at 08:50 UTC, but due to the broad impact and amplification from token creation, it took time to identify the source of the load. First responders mitigated by shedding internal load and pausing the job, and all services recovered by 10:44 UTC.

To prevent recurrence, we are rate-limiting background jobs against shared, customer-serving databases by default, and adding automatic pausing and paging on primary-server load rather than replication lag alone. We are also surfacing running background work directly alongside database health signals so responders can see and pause it without leaving those dashboards, bounding retries in the token-issuing path, and adding request-level timeouts so one unhealthy database cannot consume shared web server capacity. In addition, we are breaking apart this database cluster to remove the single point of failure. We will be moving various service-specific data, including the authorization data, out of this shared cluster in the next two weeks.
Sep 13, 10:44 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Sep 13, 10:28 UTC
Update - We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor
Sep 13, 10:26 UTC
Update - We're seeing increased database replication delays on collab which is causing increased error rates in authorization endpoints and follow-on increased error rates across the system - we are investigating
Sep 13, 09:36 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Sep 13, 09:25 UTC
Investigating - We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests
Sep 13, 09:16 UTC

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

No incidents reported.

Sep 9, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage