GitHub header
Delays with Code Scanning and Billing
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 01, 2026 - 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 01, 2026 - 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 01, 2026 - 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 01, 2026 - 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 01, 2026 - 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 01, 2026 - 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 01, 2026 - 15:17 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 01, 2026 - 15:17 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
90 days ago
99.85 % uptime
Today
Webhooks Operational
90 days ago
99.75 % uptime
Today
Visit www.githubstatus.com for more information Operational
API Requests Operational
90 days ago
99.99 % uptime
Today
Issues Operational
90 days ago
99.97 % uptime
Today
Pull Requests Operational
90 days ago
99.61 % uptime
Today
Actions Operational
90 days ago
99.67 % uptime
Today
Packages Operational
90 days ago
99.98 % uptime
Today
Pages Operational
90 days ago
99.96 % uptime
Today
Copilot Operational
90 days ago
99.93 % uptime
Today
Codespaces Operational
90 days ago
99.77 % uptime
Today
Copilot AI Model Providers Operational
90 days ago
100.0 % uptime
Today
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.

Jun 1, 2026

Unresolved incident: Delays with Code Scanning and Billing.

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026
Disruption with OpenAI Models
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
Update - We are investigating errors with Copilot requests using OpenAI models
May 28, 19:40 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
May 28, 19:20 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
May 28, 19:01 UTC
Elevated error rates across multiple services
Resolved - On May 28, 2026, between 19:07 UTC and 19:16 UTC, multiple GitHub services experienced elevated error rates. This was due to a change that was partially deployed to an authentication service, causing errors for dependent services including the web experience, REST API, Git operations, and GitHub Actions. At peak impact, 10% of GitHub Actions runs failed to queue or encountered errors while downloading actions. We mitigated the incident by rolling back the change.

We are expanding test coverage and improving our deployment validation process to prevent recurrence of this issue in the future.
May 28, 19:07 UTC
Webhook APIs and UI Degraded
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.
May 28, 01:32 UTC
Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
May 28, 01:27 UTC
Investigating - We are investigating reports of degraded performance for Webhooks
May 28, 01:13 UTC
May 27, 2026
Incident with Pull Requests, Issues, Git Operations and API Requests
Resolved - On May 27, 2026, between 12:07 UTC and 13:16 UTC, users experienced degraded performance for Git operations, Pull Requests, Issues, GraphQL API, and related services on github.com. During this time, operations that depended on Git file servers experienced elevated error rates (3.5% of pushes via HTTPS and 0.2% of pushes via SSH failed; no fetches/clones failed). An internal analytics component generated unexpectedly high load, which caused CPU saturation on the underlying infrastructure. This led to cascading slowdowns and errors across services that depend on Git operations. The issue was mitigated by stopping the offending component. Services began recovering shortly after mitigation and were fully restored by 13:16 UTC. We are taking steps to add resource limits and kill switches for internal analytics components to prevent similar issues in the future.
May 27, 13:16 UTC
Update - We're continuing to investigate degraded performance of Git operations, Issues and Pull requests.
May 27, 12:54 UTC
Investigating - We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests
May 27, 12:10 UTC
May 26, 2026
Disruption with some GitHub services
Resolved - On May 26, 2026, between 15:10 UTC and 16:35 UTC the Copilot service was degraded and many models were no longer available for use. On average, the error rate was ~5% and peaked at 11% of requests to the service. This was due to a change that introduced a configuration mismatch in HMAC signing credentials which caused the list of available models to be truncated. This was mitigated by rolling back the change. This rollback was complete by 15:34 UTC though users continued to see impact until cache TTLs expired.

We are working to improve our monitoring and error handling to reduce time to detection and better experience for issues like this in the future.
May 26, 16:35 UTC
Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
May 26, 16:24 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
May 26, 15:48 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
May 26, 15:44 UTC
Incident with Actions and Pages
Resolved - On May 26, 2026, between 10:40 UTC and 12:56 UTC, GitHub Actions jobs were degraded. From 10:40 to 12:16 UTC, all newly queued Actions runs failed to start. From 12:16 to 12:56 UTC, Actions runs that required downloading actions for their workflows continued to fail. GitHub Pages, Copilot Code Review, Copilot coding agent, Octoshift, and GitHub Enterprise Importer were also impacted due to their dependency on Actions.

This was caused by our automated account review system incorrectly suspending the service account used by GitHub Actions to authenticate workflow runs and download actions.

We mitigated by restoring the account at 12:16 UTC, marking it exempt from further automated review at 12:20 UTC, and redeploying a related service at 12:48 UTC to flush cached account state. Full recovery was confirmed at 12:56 UTC.

During this incident, a small number of Issues, PRs, Comments, and Discussions were marked as hidden when the service account was disabled. No data was lost. All content hidden because of this incident has been restored and full search index restoration is in progress.

To prevent a recurrence, we have added an allowlist of all service accounts that cannot be suspended by automated systems, and ensuring these protections are enforced consistently across all account management tooling. We are also improving diagnostic tooling for accounts and reducing cache propagation delays to shorten time to mitigate similar incidents in the future.
May 26, 13:18 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.
May 26, 13:01 UTC
Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
May 26, 13:00 UTC
Update - We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation
May 26, 12:37 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
May 26, 12:17 UTC
Update - We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.
May 26, 11:53 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.
May 26, 11:19 UTC
Investigating - We are investigating reports of degraded performance for Actions and Pages
May 26, 10:57 UTC
May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.

May 23, 2026
Intermittent errors with app installation token authentication
Resolved - On May 23, 2026 between 06:00 UTC and 19:12 UTC, GitHub experienced intermittent errors authenticating GitHub app installation tokens.

During this time, between 1-5% of app installation token authentication requests failed, with an average of 2.3% and the error rate peaking at approximately 5.4% around 14:00 UTC. Users may have experienced authentication failures when using GitHub Apps, including failures in Git operations and API calls using app installation tokens.

The issue was caused by an issue in a caching proxy component and was remediated by rolling back that component to a previous version. We are taking steps to improve monitoring for cache miss anomalies to ensure that token authentication remains functional during infrastructure changes and reviewing our protocol for testing and when we upgrade third-party dependencies.
May 23, 19:32 UTC
Update - This is fully mitigated, we will continue to monitor to ensure it does not reoccur.
May 23, 19:32 UTC
Update - We have identified and are applying additional mitigation and will continue to monitor for complete mitigation.
May 23, 19:06 UTC
Update - We see significant signs of mitigation and are monitoring for full mitigation.
May 23, 18:42 UTC
Update - We are seeing signs of mitigation and are continuing to monitor for complete mitigation. 

Next update in one hour.
May 23, 17:41 UTC
Update - We are continuing to investigate an elevated error rate of authentication failures for app installation tokens.  Next update in one hour.
May 23, 16:35 UTC
Update - We are seeing an increased rate of authentication failures for app installation tokens, affecting approximately 1% of tokens.  We are continuing to investigate.
May 23, 16:01 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
May 23, 16:00 UTC
May 22, 2026

No incidents reported.

May 21, 2026

No incidents reported.

May 20, 2026
Incident with Actions
Resolved - On May 20, 2026, between 16:00 UTC and 17:45 UTC, GitHub Actions customers experienced run start delays exceeding 5 minutes. Approximately 4.5% of all runs were delayed during the impact window, with scale set jobs disproportionately affected. 30% of scale set jobs were delayed and 4% failed to start entirely.

The incident was caused by a misconfigured health check on an internal service that assigns jobs to runners. A brief latency spike in an upstream dependency triggered health check failures across several pods, removing them from service and concentrating load on the remaining capacity. The added load drove memory pressure that escalated into a cascading failure in one regional cluster, leaving it unable to self-recover.

Responders mitigated the incident by scaling capacity in the healthy regional clusters and draining traffic away from the impaired one, after which run start latency recovered. To prevent recurrence, we are strengthening our health check configuration to avoid cascading failure scenarios and evaluating automated mitigations to rebalance traffic when a region is degraded.
May 20, 20:14 UTC
Update - Customer impact has fully subsided. We are maintaining yellow status while we deploy a permanent fix to prevent recurrence.
May 20, 19:41 UTC
Update - We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
May 20, 18:17 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
May 20, 17:52 UTC
Update - A subset of runners are taking longer than expected to connect, which may delay some jobs from beginning execution. We are actively working to mitigate the issue.
May 20, 17:46 UTC
Investigating - We are investigating reports of degraded performance for Actions
May 20, 16:58 UTC
May 19, 2026
Incident with Copilot
Resolved - On May 19, 2026, between 05:30 UTC and 14:50 UTC, some Copilot users experienced failures when using code completions, chat sessions, and cloud agent sessions. At peak impact, approximately 13% of Copilot API requests failed, and approximately 24% of remote sessions failed to initialize. A partial mitigation at 08:16 UTC reduced the Copilot API error rate to approximately 0.3%, but intermittent failures persisted until a full fix was deployed at 14:15 UTC and recovery was verified by 14:50 UTC.

The incident was caused by rate limits being exceeded on a shared infrastructure component. A recently enabled feature increased call volume to this component, and the combined load exceeded capacity limits as traffic increased during business hours.

We mitigated the incident by deploying a caching layer to reduce load on shared infrastructure. To prevent recurrence, we are separating rate limit scopes between services, adding monitoring for internal dependency rate limiting, and reducing redundant calls.
May 19, 05:30 UTC
May 18, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage