Disruption with some Copilot services
Update - We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon.
Oct 28, 2026 - 15:15 UTC
Update - We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. We have identified the root cause and working to apply a mitigation. While we work to resolve the issue we recommend choosing another model to continue using Copilot.
Oct 28, 2026 - 14:55 UTC
Update - We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models 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 to continue using Copilot.
Oct 28, 2026 - 14:33 UTC
Update - We are experiencing issues with upstream model providers resulting in a degraded experience across Copilot services. The team is actively investigating the issue.
Oct 28, 2026 - 14:15 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 28, 2026 - 14:12 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.

Oct 28, 2026

Unresolved incident: Disruption with some Copilot services.

Oct 27, 2026

Elevated 404s for GitHub App s2s tokens in git/API
Resolved - Between 0655 and 0801 UTC on 10/27, customers experienced increased failure rates for API and git requests authenticated with server-to-server tokens for GitHub Apps (excluding Actions tokens). During this window, authenticated git operations mistakenly returned 404 for 1.24% (2.6x) of requests on average and 2.49% (5.3x) at peak.

These failures were caused by a scheduled maintenance event where GitHub migrated 7 tables between two MySQL clusters in our IAD and Azure Central US datacenters. One of the affected tables stores installation records for GitHub App server-to-server tokens (excluding Actions). We've successfully completed several of these migrations in recent months without notable customer impact. However, in this case, the migration coincided with a scheduled cleanup job on the installation records table, which deleted approximately 59 million records from 0444-0617 UTC. As a result, the gh-ost tooling used in the migration experienced inter-cluster replication delays (up to 1 hour at peak).

At 0655 UTC, we begin transitioning reads of the target tables to the new MySQL cluster, with 100% of reads cutover at 0721 UTC. Customer impact began, but was not detected, throughout the read cutover and persisted until completion of the write cutover at 0801 UTC. We are updating our processes and automation to prevent a repeat of this incident, including disabling overlapping cleanup jobs prior to these migrations and blocking the cutover of reads when replication delays are high.
Oct 27, 08:00 UTC

Oct 26, 2026

Incident with Actions, Issues, API Requests and 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.
Oct 26, 18:57 UTC
Update - We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.

We mitigated the issue and all services have recovered.
Oct 26, 18:54 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 26, 18:50 UTC
Investigating - We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests
Oct 26, 18:48 UTC

Oct 25, 2026

No incidents reported.

Oct 24, 2026

Grok 4.6 and Grok 4.7 Service Issues
Resolved - Between 23:28 and 00:23 UTC on October 27, 2026, GitHub Copilot experienced degradation affecting Grok 4.6 and Grok 4.7 models. 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.
Oct 24, 00:23 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Oct 24, 00:23 UTC
Update - We are experiencing degraded availability for the Grok 4.6 and Grok 4.7 models 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.
Oct 23, 23:42 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Oct 23, 23:41 UTC

Oct 23, 2026

Disruption with Dependabot Alerts
Resolved - We identified that an advisory-publication driven fan-out was overwhelming Dependabot alert processing on repositories by saturating the queue with its own events, delaying processing of events related to repository pushes.

We have now isolated this fan-out and applied a throttle so it runs at a fixed rate and cannot delay other events. This remediation has successfully prevented a new fan-out process impacting users.
Oct 23, 18:51 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 23, 18:36 UTC
Update - Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability.

We're continuing to investigate and work to restore normal processing.
Oct 23, 17:27 UTC
Update - We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring progress and will share another update as we learn more.
Oct 23, 16:43 UTC
Update - We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring the rollout and will share another update as we learn more.
Oct 23, 16:11 UTC
Update - We’re scaling alert processing capacity to reduce the backlog causing delays in some Dependabot alerts closing after affected repositories have been updated. We’re continuing to monitor and will share another update as more information becomes available.
Oct 23, 15:39 UTC
Update - We’re investigating delays in some Dependabot alerts closing after affected repositories have been updated to address a vulnerability. Alert processing is backed up. We’ll share more information as it becomes available.
Oct 23, 15:00 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 23, 14:58 UTC
Delayed Actions status check results
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.
Oct 23, 08:05 UTC
Update - As of 07:27 UTC, Actions results are delivering within normal SLOs again.

Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future.
Oct 23, 07:56 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Oct 23, 07:53 UTC
Update - We are seeing delays in results from Actions workflows being reported within GitHub starting from 07:07 UTC.

Recovery is already being seen but our team is continuing to investigate and monitor performance.
Oct 23, 07:31 UTC
Investigating - We are investigating reports of degraded performance for Actions
Oct 23, 07:29 UTC
Project updates delayed
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.
Oct 23, 02:30 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 23, 00:55 UTC
Update - GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear.

We're continuing to work on the remaining delays and monitor recovery.
Oct 22, 23:48 UTC
Update - Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed.

We have seen some recovery, and are working to add more capacity to accelerate the recovery.
Oct 22, 22:07 UTC
Update - Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed.

We've identified interruptions in update processing and are evaluating mitigations to restore normal operation.
Oct 22, 20:46 UTC
Update - Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.
Oct 22, 19:56 UTC
Update - Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.
Oct 22, 19:04 UTC
Update - The other affected services have recovered.

We're continuing to investigate GitHub Projects and verify that normal operation has been restored.
Oct 22, 18:26 UTC
Update - We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.
Oct 22, 17:43 UTC
Update - Actions, Issues, Packages and Pull Requests are operating normally.
Oct 22, 17:41 UTC
Update - We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com.

We're continuing to work towards full recovery and monitoring for stability.
Oct 22, 17:16 UTC
Update - Some users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com.

We're working through multiple mitigation efforts and continuing to investigate.
Oct 22, 16:41 UTC
Update - API Requests is operating normally.
Oct 22, 16:35 UTC
Update - Packages is experiencing degraded performance. We are continuing to investigate.
Oct 22, 16:28 UTC
Update - API Requests is experiencing degraded performance. We are continuing to investigate.
Oct 22, 16:26 UTC
Update - Some users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com.

We're investigating and evaluating mitigation options to restore normal service.
Oct 22, 16:08 UTC
Update - Some users may experience intermittent errors loading Issues, Pull Requests and search results on github.com.

We're investigating and working to restore normal service.
Oct 22, 15:33 UTC
Investigating - We are investigating reports of degraded performance for Actions, Issues and Pull Requests
Oct 22, 15:28 UTC

Oct 22, 2026

Incident with Actions Results
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.
Oct 22, 15:18 UTC
Update - GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.
Oct 22, 15:18 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Oct 22, 15:17 UTC
Update - We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.
Oct 22, 15:06 UTC
Update - Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.
Oct 22, 14:35 UTC
Update - We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.
Oct 22, 14:19 UTC
Investigating - We are investigating reports of degraded performance for Actions
Oct 22, 14:18 UTC

Oct 21, 2026

Delays for Pull Requests and Webhook deliveries
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.
Oct 21, 19:22 UTC
Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed.
Oct 21, 19:22 UTC
Update - Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates.
Oct 21, 18:52 UTC
Update - Audit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow.
Oct 21, 18:18 UTC
Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates.
Oct 21, 17:09 UTC
Update - Actions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues.
Oct 21, 16:59 UTC
Update - Actions and Webhooks are operating normally.
Oct 21, 16:57 UTC
Update - Audit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more.
Oct 21, 16:34 UTC
Update - Pull Requests is operating normally.
Oct 21, 16:33 UTC
Update - Audit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will share further updates as we learn more.
Oct 21, 16:25 UTC
Update - Audit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.
Oct 21, 16:17 UTC
Update - We continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.
Oct 21, 15:58 UTC
Update - We are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these mitigations take effect.
Oct 21, 15:36 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Oct 21, 15:15 UTC
Investigating - We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
Oct 21, 14:52 UTC

Oct 20, 2026

No incidents reported.

Oct 19, 2026

Degraded availability for GitHub Actions, GitHub Pages and Webhooks
Resolved - On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost.

Impact

- Workflow status updates, logs, and checks were delayed.
- 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed.
- During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors.

Pages deployments and webhooks generated by Actions runs were delayed.

An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to investigate the cause of the initial connection timeouts.

We were already in the process of rolling out a limit on how quickly this service can open new connections, but it was still in shadow mode (logging only, not enforcing) at the time of the incident. We have since fully enforced it and capped the service's concurrent connection attempts. We are extending these limits to other Actions services, adding backoff to retries, limiting how much shared network capacity a single service can use, and improving alerting so we can find the source of connection surges faster.
Oct 19, 16:56 UTC
Monitoring - Actions, Pages and Webhooks are operating normally.
Oct 19, 16:56 UTC
Update - We’re seeing recovery following mitigation and are continuing to monitor.

Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.
Oct 19, 16:30 UTC
Update - We’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks.

Customers may experience delays in workflow processing, site builds and webhook delivery.
Oct 19, 15:56 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Oct 19, 15:50 UTC
Investigating - We are investigating reports of degraded performance for Actions and Pages
Oct 19, 15:49 UTC

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

CCA Automations are delayed when starting an Automation
Resolved - We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.
Oct 15, 18:56 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 15, 18:53 UTC
Update - CCA Automations are experiencing delays when users start an Automation
Oct 15, 18:34 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 15, 18:31 UTC

Oct 14, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage