New Multi-region uptime checks and custom-domain status pages

GitHub Outage History

Daily provider-status observations and published incident history for GitHub.

Operational

GitHub is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow GitHub for future changes.

69.4% of 49 verified observed days had no reported provider issue

90-Day Trend

Jul 15Oct 12

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 76.7% 30 7

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 14 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Incident with Grok Copilot AI Model Provider
minor Observed active window 3h 2m

View incident details and source

Started:

Copilot AI Model Providers
investigating
The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.
investigating
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.<br />
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
Delays in commit processing
minor Observed active window 1h 4m

View incident details and source

Started:

Pull Requests
investigating
Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
investigating
We are investigating reports of degraded performance for Pull Requests
August 2026
Elevated rate of errors for OpenAI models provided by Copilot
minor Observed active window 44m

View incident details and source

Started:

Copilot AI Model Providers
monitoring
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
investigating
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.
investigating
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. <br />
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
Incident with Copilot AI Model Providers
critical Observed active window 2h 10m

View incident details and source

Started:

Copilot AI Model Providers
investigating
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
investigating
We are experiencing degraded availability for the Kimi K3 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.
investigating
We are investigating reports of degraded availability for Copilot AI Model Providers
Disruption with GitHub Billing
minor Observed active window 20h 7m

View incident details and source

Started:

investigating
No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause.
investigating
Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since the previous update. We will provide another update as the investigation progresses.
investigating
Our mitigation is still holding as we continue to investigate to find the root cause.
investigating
We are continuing to monitor the mitigation that we have applied for the billing page disruption.
investigating
We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered.
investigating
We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Actions and Pull Requests
minor Observed active window 1h 33m

View incident details and source

Started:

Pull Requests Actions
investigating
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
investigating
We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.
investigating
We are investigating reports of degraded performance for Actions and Pull Requests
Incident with Actions
critical Observed active window 2h 53m

View incident details and source

Started:

Actions Pages
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.
investigating
We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.
investigating
Pages is operating normally.
investigating
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.
investigating
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
investigating
We've identified an issue with a database primary and are failing over to a replica immediately
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of degraded availability for Actions
Disruption with some GitHub services
minor Observed active window 1h 5m

View incident details and source

Started:

investigating
We are investigating reports of impacted performance for some GitHub services.

Legacy Incident Archive

128 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

July 2026
Latency issues across a number of services
major Source not attested
Last archived state: resolved
View archived record details
investigating
Webhooks is operating normally.
investigating
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
investigating
We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.
investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
investigating
We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of degraded availability for Actions, Issues and Webhooks
Disruption with actions hosted runners
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.
investigating
We are investigating reports of degraded performance for Actions
Some SSH connections using deploy keys are failing
critical Source not attested
Last archived state: resolved
View archived record details
investigating
We have identified a recent code change as a potential cause of the SSH authentication failures affecting deploy key connections. Our engineering team is rolling back this change. Customers using deploy keys for SSH access to repositories may continue to experience intermittent connection failures until the fix is deployed.
investigating
We are investigating reports of intermittent SSH authentication failures affecting connections that use deploy keys. Customers may experience failed SSH connections when interacting with repositories via deploy keys. Our engineering team is actively investigating the root cause and working toward resolution.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with GPT 5.3 Codex
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are seeing signs of sustained recovery from the upstream provider for GPT 5.3 Codex requests. Requests are succeeding as expected. We are awaiting confirmation from the provider that the issue is fully mitigated before resolving this incident.
investigating
The upstream provider continues to return intermittent errors for GPT 5.3 Codex requests. Some users may experience failed or interrupted responses when using this model. Traffic continues to be automatically rerouted to reduce impact, and we are actively working with the upstream provider on a resolution. In the meantime, selecting an alternative model will avoid disruption.
investigating
We identified that an upstream provider is returning errors for GPT 5.3 Codex requests, causing some users to experience failed or interrupted responses. Traffic is being automatically rerouted to mitigate impact. We are working with the upstream provider to resolve the underlying issue. We recommend using a different model at this time while we resolve the problem.
investigating
We are investigating GPT Codex 5.3 performance.
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
Disruption with some GitHub services
major Source not attested
Last archived state: resolved
View archived record details
investigating
The Git LFS API issues have been identified as being related to a separate incident where Actions is experiencing degraded availability. We’re consolidating our investigation efforts under that incident.
monitoring
Some Git LFS operations, and loading files through the API are failing. We are investigating.
monitoring
Some Git LFS operations, and loading files through the API are failing. We are investigating.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with GitHub Actions
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.
investigating
API Requests is operating normally.
investigating
Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.
investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
investigating
Issues is operating normally.
investigating
Pages is operating normally.
investigating
We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.<br /><br />A separate incident was opened before we understood they were related. We will continue to post updates on this incident.
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
investigating
Actions and Pages are experiencing degraded performance. We are continuing to investigate.
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
investigating
API Requests is experiencing degraded availability. We are continuing to investigate.
investigating
We have identified the cause of failures in GitHub Actions and are working to restore service.
investigating
We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.
investigating
We are investigating reports of degraded performance for Actions
Degraded REST API Availability
major Source not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
investigating
We are continuing to investigate an issue causing approximately 35% of REST API requests to fail.  Based on our current understanding, requests are not consistently reaching the application layer, resulting in failed requests returning HTML responses instead of the expected API response format. We are actively investigating the issue and will provide another update as soon as more information is available.
investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
investigating
We are aware of degraded REST API availability and are investigating
investigating
We are investigating reports of impacted performance for some GitHub services.
Claude Fable 5 experiencing degraded performance
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are experiencing degraded availability for the Claude Fable 5 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.
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
Disruption with some GitHub services
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Webhooks
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
investigating
Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when deliveries were accepted and processed. Customers may notice missing webhook deliveries in the UI, and these deliveries will not be retryable.<br /><br />Impact resolved automatically once the deployment completed.
investigating
We are investigating reports of degraded performance for Webhooks
Get alerts for GitHub Subscribe to the provider incident feed Browse all services