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
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 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.
investigating
Pull Requests is operating normally.
investigating
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
investigating
Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.
investigating
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
Incident with Git Operations, Issues, Actions and Pull Requests
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
investigating
We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
Incident with Git Operations, Pull Requests and Actions
Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
monitoring
We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
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
The degradation affecting Git Operations and Webhooks 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 are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
investigating
Actions is operating normally.
investigating
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
investigating
Git Operations is operating normally.
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
We are deploying a mitigation and plan to resume migrations shortly thereafter
investigating
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
investigating
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
investigating
Pull Requests is operating normally.
investigating
Webhooks is operating normally.
investigating
We are investigating reports of degraded performance for Pull Requests and Webhooks
Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
investigating
We are investigating reports of impacted performance for some GitHub services.
We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
investigating
In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
investigating
We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
investigating
We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
investigating
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
investigating
We are investigating reports of degraded performance for Actions
GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.
investigating
We are currently applying a mitigation and anticipate recovery within thirty minutes.
investigating
We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.
investigating
We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.
investigating
We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.
investigating
We are investigating reports of degraded performance for Actions
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.
investigating
We are continuing to work on mitigation. We will post another update in approximately one hour.
investigating
We have identified the problem and are actively working on mitigation.
investigating
We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.
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.
April 2026
Copilot Coding Agent failing to start some jobs
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with GitHub's code search
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.
investigating
We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.
investigating
We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April 2026). We are still working on recovering our ingestion pipeline, and synchronizing the indexed data.<br /><br />We will update again within 2 hours.
investigating
We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic configuration which is causing most requests for Code Search results to fail. We are working to restore the service and to re-ingest the misaligned data.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Copilot
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The success rate and latency for creating and viewing agent sessions has stabilized at baseline levels, we are continuing to monitor recovery
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The success rate for creating and viewing agent sessions has stabilized, and we're continuing to monitor latency, which is trending toward baseline levels.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
investigating
Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate.
investigating
We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation.
investigating
We are investigating reports of degraded performance for Copilot
March 2026
Incident with Pull Requests: High percentage of 500s
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
investigating
We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.
investigating
Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.
investigating
We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.
investigating
We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.
investigating
We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.
investigating
We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.
investigating
We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.
investigating
We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.
investigating
We are investigating reports of degraded performance for Pull Requests
Issues with metered billing report generation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We have applied mitigations to a data store related to billing reports, and are seeing partial recovery to billing report generation. We continue to monitor for full recovery.
investigating
We are seeing a high number of 500s due to timeouts across GitHub services. We are redeploying some of our core services and we expect that this allow us to recover.
investigating
We're continuing to see high failure rates on billing report generation, and are working on mitigations for a data store related to billing reports.
investigating
We're seeing issues related to metered billing reports, intermittently affecting metered usage graphs and reports on the billing page. We have identified an issue with a data store, and are working on mitigations.
investigating
We are investigating reports of impacted performance for some GitHub services.
Elevated delays in Actions workflow runs and Pull Request status updates
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of degraded performance for Actions and Pull Requests
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating elevated error rates affecting multiple GitHub services including Actions, Issues, Pull Requests, Webhooks, Codespaces, and login functionality. Some users may have experienced errors when accessing these features. Most services are now showing signs of recovery. We'll post another update by 21:00 UTC.
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of degraded performance for Actions
Teams Github Notifications App is down
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are experiencing degraded availability from Azure Teams APIs, which is impacting notifications from GitHub to Microsoft Teams. We are awaiting resolution from Azure.
investigating
We are experiencing degraded availability from Azure APIs, which is impacting notifications from GitHub to Microsoft Teams. We are working with Azure to resolve the issue.
investigating
We found an issue impacting notifications from GitHub to Microsoft Teams. We are working on mitigation and will keep users updated on progress towards mitigation.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating intermittently high latency and errors from Git operations.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with Copilot Coding Agent Sessions
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are rolling out our mitigation and are seeing recovery.
investigating
We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation.
investigating
We are investigating reports of impacted performance for some GitHub services.
