📢 Heads up: We will be performing a status page migration on 2026-06-11 at 13:00 UTC. More details can be found here. To prepare, head to our new statuspage and click Subscribe to Updates to reconfigure your subscription. Learn more →
GitHub header

All Systems Operational

About This Site

For the status of GitHub.com, please visit: githubstatus.com

Uptime over the past 90 days. View historical uptime.
Git Operations Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
99.99 % uptime
Today
API Requests Operational
90 days ago
100.0 % uptime
Today
Issues Operational
90 days ago
99.96 % uptime
Today
Pull Requests Operational
90 days ago
99.84 % uptime
Today
Actions Operational
90 days ago
99.99 % uptime
Today
Copilot Operational
90 days ago
99.98 % uptime
Today
Packages Operational
90 days ago
100.0 % uptime
Today
Copilot AI Model Providers Operational
90 days ago
100.0 % uptime
Today
Pages Operational
90 days ago
100.0 % uptime
Today
Visit eu.githubstatus.com for more information 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.

Scheduled Maintenance

Status Page Migration Jun 11, 2026 13:00-15:00 UTC

Update - This is a reminder for our scheduled migration on 2026-06-11 at 13:00 UTC.

We will be migrating the EU status page to a new provider on 2026-06-11 at 13:00 UTC. We expect this maintenance to take approximately 2 hours. During this time, the status page will be unavailable.

Once the maintenance is complete, eu.githubstatus.com will resolve to the new page.

All email subscriptions will be automatically migrated. After the maintenance, email subscribers will receive a subscription confirmation email.

Slack subscriptions will not be migrated automatically. If you subscribe through Slack, please navigate to our updated status page and select Subscribe to Updates to configure your subscription to the new status page.

SMS notifications will no longer be supported. Existing SMS subscriptions will not be migrated. To continue receiving updates, please navigate to our updated status page and select Subscribe to Updates to configure your subscription to the new status page via Email, Slack, or Webhooks.
Jun 03, 2026 - 13:06 UTC
Scheduled - We will be migrating the EU status page to a new provider on 2026-06-11 at 13:00 UTC. We expect this maintenance to take approximately 2 hours. During this time, the status page will be unavailable.

Once the maintenance is complete, eu.githubstatus.com will resolve to the new page.

All email subscriptions will be automatically migrated. After the maintenance, email subscribers will receive a subscription confirmation email.

Slack subscriptions will not be migrated automatically. If you subscribe through Slack, please navigate to our updated status page and select Subscribe to Updates to configure your subscription to the new status page.

SMS notifications will no longer be supported. Existing SMS subscriptions will not be migrated. To continue receiving updates, please navigate to our updated status page and select Subscribe to Updates to configure your subscription to the new status page via Email, Slack, or Webhooks.
May 28, 2026 - 12:58 UTC
Jun 10, 2026

No incidents reported today.

Jun 9, 2026

No incidents reported.

Jun 8, 2026
EU - Disruption with Claude Opus 4.7
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.
Jun 8, 10:03 UTC
Update - We are experiencing degraded availability for the Claude Opus 4.7 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, and starting to see recovery.
Jun 8, 09:49 UTC
Update - We are experiencing degraded availability for the Claude Opus 4.7 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.
Jun 8, 09:08 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Jun 8, 09:05 UTC
Jun 7, 2026

No incidents reported.

Jun 6, 2026

No incidents reported.

Jun 5, 2026

No incidents reported.

Jun 4, 2026
EU - Copilot Code Review Failing
Resolved - On June 4, 2026, from 17:30 UTC to 18:55 UTC, Copilot Code Review experienced elevated failures for review requests on GitHub.com. Affected users saw “Copilot ran into an error” on pull requests when requesting a code review.

During the incident window, an average of 81.6% of Copilot Code Review requests failed, with a peak failure rate of 93.9%. Approximately 36,800 code review requests failed. GitHub Enterprise Cloud with data residency was not impacted.

The issue was caused by a newly released dependency used by the Copilot Code Review processing workflow. The release introduced an incompatibility with the runtime environment. Because the workflow automatically consumed the latest release, the incompatible version was picked up without sufficient compatibility validation and caused review processing to fail.

We mitigated the incident by removing the problematic dependency version and redeploying the affected processing service. New code reviews began recovering at 18:44 UTC, and the failure rate returned to baseline by 18:55 UTC. Remaining timed-out work drained by 19:59 UTC.

To reduce the risk of recurrence, we are pinning the dependency version instead of automatically consuming the latest release, adding compatibility checks for future releases, improving fast-failure behavior when the review processor cannot start, adding shorter timeout controls for review workflows, and improving monitoring for review completion failures.
Jun 4, 19:59 UTC
Update - This issue is now fully resolved and Copilot Code Review is working as expected.
Jun 4, 19:59 UTC
Update - The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected.  We are continuing to monitor for full resolution.

 Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
Jun 4, 19:41 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 4, 19:07 UTC
Update - The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected.

Customers may need to re-request Copilot Code Review.  Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
Jun 4, 19:07 UTC
Update - The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.
Jun 4, 18:52 UTC
Update - We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.

A mitigation is in progress, we expect mitigation in approximately 30m.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 4, 18:22 UTC
Update - We have identified that Copilot Code Review.  Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.

A mitigation is in progress.
Jun 4, 18:03 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 4, 18:02 UTC
Jun 3, 2026
EU - Disruption with some GitHub services
Resolved - On June 2, 2026, between 21:54 UTC and June 3, 2026 06:45 UTC, the Spark service was degraded and users were unable to store or retrieve data for their Spark apps in one of our hosting regions. Users could still make changes to their app configuration during this time. The error rate peaked at 25% of affected requests to the service. Impact was limited to users whose requests were served through a single affected region; 43 users experienced errors during this window.

The root cause was a configuration that referenced a service component by a fixed address rather than a dynamic service endpoint. When the component was replaced, requests could no longer reach the fixed address and began to fail. We resolved the incident by updating the configuration to use a our standard service endpoints that are resilient to component replacement. Recovery time was extended because replacing the component required overrides to a temporary deployment safeguard.

We are working to add validation that prevents fixed infrastructure addresses from being used in application configuration outside of test environments and to improve our monitoring to reduce our time to detect.
Jun 3, 06:47 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 3, 06:45 UTC
Update - We are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation.
Jun 3, 06:02 UTC
Update - We are investigating reports of impacted performance for some GitHub services.

---
Relevant stamps: dotcom
Jun 3, 03:45 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 3, 03:13 UTC
Jun 2, 2026
EU - Delays with Code Scanning and Billing
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.
Jun 2, 00:18 UTC
Update - We have identified the root cause and applied mitigations to address delays in billing updates and are continuing to see improvement in the processing rate. We will continue to monitor the progress and will provide an update in few hours.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 1, 21:59 UTC
Update - We are continuing to investigate delayed billing updates, on GitHub.com.  We have applied additional mitigations are continuing to see signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.

Next update in 2 hours.
Jun 1, 19:27 UTC
Update - We are continuing to investigate delayed billing updates, on GitHub.com.  We have applied additional mitigations and are seeing some more signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 1, 18:48 UTC
Update - We are continuing to investigate delayed billing updates, on GitHub.com.   We have applied multiple mitigations and are seeing some signs of improvement, and are continuing to work to improve the processing rate.  We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 1, 17:28 UTC
Update - We are investigating reports of delayed billing updates, on GitHub.com. We are continuing to investigate delays in our job processing architecture. We are attempting to mitigate at the infrastructure level.  Code scanning runs and notifications have recovered.  We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Cloud with Data Residency is not impacted.
Jun 1, 16:42 UTC
Update - We are investigating reports of delayed code scanning runs, billing updates, email and mobile push notifications. We are investigating delays in our job processing architecture. We will continue to keep users updated on progress towards mitigation.
Jun 1, 15:43 UTC
Update - We are investigating reports of delayed code scanning runs and delayed billing updates.  We will continue to keep users updated on progress towards mitigation.
Jun 1, 15:17 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 1, 15:17 UTC
Jun 1, 2026
May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026
EU - Investigating Copilot code completions degraded performance
Resolved - On May 29, 2026 between 14:43 UTC and 17:02 UTC, EU GitHub Enterprise Cloud Copilot users experienced degraded availability for code completions due to an upstream model provider outage. During this time, on average 36.15% of requests failed, with the error rate peaking at 78.44%.

We mitigated the incident within an hour by redistributing traffic to healthy regions.

We are investing in improved failover automation and regional redundancy to reduce customer impact from similar upstream outages in the future.
May 29, 17:36 UTC
Monitoring - Copilot is operating normally.
May 29, 17:36 UTC
Investigating - We are investigating reports of degraded performance for Copilot
May 29, 16:50 UTC
May 28, 2026
EU - Disruption with Copilot Cloud Agent and Copilot Code Review
Resolved - On May 28th, 2026, between approximately 18:27 and 20:41 UTC, the GitHub Copilot service was degraded due to an issue with the Responses API of an upstream provider affecting the GPT-5.2, GPT-5.3-Codex, GPT-5.4, and GPT-5.5 models. Requests routed to these models via the Responses API returned elevated error rates, which also affected Copilot coding agent and Copilot code review. No other models were impacted.

We mitigated the incident by shifting traffic away from the affected models while the upstream provider deployed a fix.

GitHub is working to improve automated failover for the affected models and strengthen monitoring to prevent similar incidents in the future.
May 28, 20:41 UTC
Update - Open AI models are currently unavailable. We are shifting requests to other models to reduce impact.
May 28, 20:06 UTC
Investigating - We are investigating reports of degraded performance for Copilot
May 28, 19:20 UTC
May 27, 2026
EU - Incident with Actions, Issues and Webhooks
Resolved - On May 27, 2026, between 18:49 and 19:23 UTC in the West EU region of GitHub Enterprise Cloud, webhooks and actions customers experienced delays. Over the 34m incident, 18.76% of external webhook deliveries exceeded latency thresholds, and Actions run start delays peaked at 42% of workflow jobs taking longer than 5 minutes to begin execution.

The delays were caused by a planned operating system upgrade which updated too many nodes at once, creating excess latency which caused request-timeout errors for the duration of the upgrade. This upgrade process was automated, and all services recovered upon completion.

To prevent future recurrence, we have slowed our process to upgrade a safer number of nodes at a time.
May 27, 19:28 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
May 27, 19:23 UTC
Update - Issues is operating normally.
May 27, 19:23 UTC
Update - Webhooks is operating normally.
May 27, 19:23 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.
May 27, 19:06 UTC
Update - Webhooks is experiencing degraded availability. We are continuing to investigate.
May 27, 19:05 UTC
Investigating - We are investigating reports of degraded performance for Actions, Issues and Webhooks
May 27, 19:05 UTC
← Incident History Powered by Atlassian Statuspage