Subscribe to UpdatesSubscribe
Get email notifications whenever GitHub creates, updates or resolves an incident.
Get text message notifications whenever GitHub creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
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.99
% uptime
Today
Webhooks
Operational
90 days ago
100.0
% uptime
Today
Visit www.githubstatus.com for more information
Operational
API Requests
Operational
90 days ago
99.94
% uptime
Today
Issues
Operational
90 days ago
99.98
% uptime
Today
Pull Requests
Operational
90 days ago
99.71
% uptime
Today
Actions
Operational
90 days ago
99.8
% uptime
Today
Packages
Operational
90 days ago
100.0
% uptime
Today
Pages
Operational
90 days ago
99.96
% uptime
Today
Copilot
Operational
90 days ago
99.89
% uptime
Today
Codespaces
Operational
90 days ago
99.84
% uptime
Today
Copilot AI Model Providers
Operational
90 days ago
99.88
% 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.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Jul 10, 2026
No incidents reported today.
Jul 9, 2026
Resolved -
On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 8% of hosted-runner jobs experienced start delays exceeding 5 minutes, while roughly 2% failed to start.
At 13:39 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.
Jul 9, 13:52 UTC
At 13:39 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.
Jul 9, 13:52 UTC
Update -
Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated.
We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.
Jul 9, 13:41 UTC
We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.
Jul 9, 13:41 UTC
Monitoring -
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
Jul 9, 13:39 UTC
Jul 9, 13:39 UTC
Update -
We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog.
Customers may see a small rate of API and job failures as the system is recovering.
Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery.
Pages were accessible throughout the incident.
Jul 9, 13:17 UTC
Customers may see a small rate of API and job failures as the system is recovering.
Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery.
Pages were accessible throughout the incident.
Jul 9, 13:17 UTC
Update -
Actions is experiencing degraded availability. We are continuing to investigate.
Jul 9, 13:16 UTC
Jul 9, 13:16 UTC
Update -
We're seeing Actions and Pages recovery.
For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing.
GitHub pages builds were also failing during that period, but Pages are still accessible.
We are continuing to monitor for full recovery.
Jul 9, 12:54 UTC
For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing.
GitHub pages builds were also failing during that period, but Pages are still accessible.
We are continuing to monitor for full recovery.
Jul 9, 12:54 UTC
Update -
Actions is experiencing degraded availability. We are continuing to investigate.
Jul 9, 12:46 UTC
Jul 9, 12:46 UTC
Update -
Pages is experiencing degraded performance. We are continuing to investigate.
Jul 9, 12:36 UTC
Jul 9, 12:36 UTC
Update -
Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.
This has caused some customers to exceed their hosted compute concurrency and experience increased impact.
We are continuing to working on infrastructure mitigations.
Next update in one hour.
Jul 9, 12:01 UTC
This has caused some customers to exceed their hosted compute concurrency and experience increased impact.
We are continuing to working on infrastructure mitigations.
Next update in one hour.
Jul 9, 12:01 UTC
Update -
Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.
Jul 9, 10:15 UTC
Jul 9, 10:15 UTC
Update -
Actions is experiencing degraded availability. We are continuing to investigate.
Jul 9, 10:07 UTC
Jul 9, 10:07 UTC
Update -
We are continuing to work on a mitigation.
Jul 9, 06:01 UTC
Jul 9, 06:01 UTC
Update -
Approximately 5% 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.
Jul 9, 04:51 UTC
Jul 9, 04:51 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Jul 9, 04:34 UTC
Jul 9, 04:34 UTC
Jul 8, 2026
No incidents reported.
Jul 7, 2026
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.
Jul 7, 16:17 UTC
Jul 7, 16:17 UTC
Monitoring -
The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability.
Jul 7, 16:02 UTC
Jul 7, 16:02 UTC
Update -
We have rolled out the mitigation and are seeing recovery.
Jul 7, 16:00 UTC
Jul 7, 16:00 UTC
Update -
Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation.
Jul 7, 15:50 UTC
Jul 7, 15:50 UTC
Update -
Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful.
We continue to investigate the source of these errors.
Jul 7, 15:06 UTC
We continue to investigate the source of these errors.
Jul 7, 15:06 UTC
Update -
Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time. Retries may be successful.
Actions runs and codespaces in progress are continuing successfully.
We are continuing to investigate the source of these errors.
Jul 7, 14:47 UTC
Actions runs and codespaces in progress are continuing successfully.
We are continuing to investigate the source of these errors.
Jul 7, 14:47 UTC
Update -
Codespaces is experiencing degraded availability. We are continuing to investigate.
Jul 7, 14:32 UTC
Jul 7, 14:32 UTC
Update -
Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time.
Actions runs in progress are continuing successfully.
Jul 7, 14:14 UTC
Actions runs in progress are continuing successfully.
Jul 7, 14:14 UTC
Investigating -
We are investigating reports of degraded performance for Actions and Codespaces
Jul 7, 14:14 UTC
Jul 7, 14:14 UTC
Jul 6, 2026
No incidents reported.
Jul 5, 2026
No incidents reported.
Jul 4, 2026
No incidents reported.
Jul 3, 2026
No incidents reported.
Jul 2, 2026
Resolved -
On July 2nd, 2026, between approximately 15:00 and 18:30 UTC, the GitHub Pages service experienced degraded deployment performance due to a surge in demand that exceeded available processing capacity. During this period, users publishing to GitHub Pages may have seen their deployments queued or taking substantially longer than usual to go live. No other GitHub services were impacted.
We mitigated the incident by scaling up Pages deployment workers and provisioning additional storage capacity to clear the backlog.
GitHub is reviewing capacity planning and autoscaling measures to reduce the likelihood of similar delays in the future.
Jul 2, 18:25 UTC
We mitigated the incident by scaling up Pages deployment workers and provisioning additional storage capacity to clear the backlog.
GitHub is reviewing capacity planning and autoscaling measures to reduce the likelihood of similar delays in the future.
Jul 2, 18:25 UTC
Update -
Pages deployment latency is recovering. The team continues working toward full mitigation and a return to nominal state.
Jul 2, 17:57 UTC
Jul 2, 17:57 UTC
Update -
We are investigating reports of slow and failing Pages deployments. Access to Pages is unaffected.
Jul 2, 16:56 UTC
Jul 2, 16:56 UTC
Investigating -
We are investigating reports of degraded performance for Pages
Jul 2, 16:54 UTC
Jul 2, 16:54 UTC
Jul 1, 2026
Resolved -
On July 1, 2026, between approximately 00:00 UTC and 13:04 UTC, some GitHub Copilot customers whose budget was exhausted before the monthly reset remained incorrectly blocked from paid Copilot usage after the new billing month began, even though their budgets had reset. Some budget changes also took longer than usual to apply. Only customers with an exhausted budget were affected, which limited the impact.
This was caused by a caching issue at the monthly reset: for some users, a pre-reset "budget exhausted" status was re-saved and served even though their budget had reset, so they stayed blocked. We had built a safeguard ahead of the reset to prevent this, but it did not take effect because an internal configuration service did not load its settings correctly. We resolved the incident by deploying a change that discards the outdated status and recomputes access from current budget data independently of that configuration, and by working through the backlog of budget updates.
To prevent recurrence, we are ensuring pre-reset status cannot survive the monthly budget reset, adding alerting for this failure mode, and increasing capacity to absorb the monthly surge of budget updates.
Jul 1, 13:26 UTC
This was caused by a caching issue at the monthly reset: for some users, a pre-reset "budget exhausted" status was re-saved and served even though their budget had reset, so they stayed blocked. We had built a safeguard ahead of the reset to prevent this, but it did not take effect because an internal configuration service did not load its settings correctly. We resolved the incident by deploying a change that discards the outdated status and recomputes access from current budget data independently of that configuration, and by working through the backlog of budget updates.
To prevent recurrence, we are ensuring pre-reset status cannot survive the monthly budget reset, adding alerting for this failure mode, and increasing capacity to absorb the monthly surge of budget updates.
Jul 1, 13:26 UTC
Update -
The fix has been deployed globally and we are monitoring the results
Jul 1, 13:05 UTC
Jul 1, 13:05 UTC
Monitoring -
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
Jul 1, 13:04 UTC
Jul 1, 13:04 UTC
Update -
A fix for the delayed resets is currently being deployed.
Jul 1, 12:42 UTC
Jul 1, 12:42 UTC
Update -
We have identified the likely reason for the delays and are working on a solution.
Jul 1, 11:44 UTC
Jul 1, 11:44 UTC
Investigating -
We are investigating reports of degraded performance for Copilot
Jul 1, 10:51 UTC
Jul 1, 10:51 UTC
Jun 30, 2026
Resolved -
Between 15:19 UTC and 15:49 UTC on June 30, 2026, users were unable to complete the signup flow for GitHub.com/signup. Approximately 62% of new user signups failed for about 30 minutes during this window.
This was caused by a configuration change to the signup flow that unintentionally blocked users from completing signup.
We mitigated the incident by reverting the change, which restored successful signups. To reduce the likelihood and impact of similar issues, we are adopting staged, incremental rollouts for changes on the signup path, improving our ability to test these changes before they reach production, and adding checks to verify signup health before and during any change that affects this flow.
Jun 30, 15:49 UTC
This was caused by a configuration change to the signup flow that unintentionally blocked users from completing signup.
We mitigated the incident by reverting the change, which restored successful signups. To reduce the likelihood and impact of similar issues, we are adopting staged, incremental rollouts for changes on the signup path, improving our ability to test these changes before they reach production, and adding checks to verify signup health before and during any change that affects this flow.
Jun 30, 15:49 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Jun 30, 15:38 UTC
Jun 30, 15:38 UTC
Jun 29, 2026
No incidents reported.
Jun 28, 2026
Resolved -
From June 26, 2026 at 23:40 UTC through June 28, 2026 at 20:55 UTC, Copilot Cloud Agent was degraded. The agent could fail when reporting progress, replying to pull request comments, or opening pull requests. For affected built-in tool calls, the average error rate was approximately 8%, with hourly error rates peaking around 26%.
This was due to a regression introduced during a Copilot Cloud Agent runtime deployment that caused several built-in agent tools to become unavailable. In many cases, the affected tool calls failed silently so agent jobs appeared to succeed. This monitoring gap meant it took longer than expected to identify the failure. We mitigated the incident by reverting the runtime deployment to the previously stable version.
We've added monitoring and alerting for this class of tool-availability error to reduce time-to-detection. We're also adding regression tests for these built-in agent tools, and improving the shipping safety for future runtime rollouts to avoid similar issues.
Jun 28, 20:55 UTC
This was due to a regression introduced during a Copilot Cloud Agent runtime deployment that caused several built-in agent tools to become unavailable. In many cases, the affected tool calls failed silently so agent jobs appeared to succeed. This monitoring gap meant it took longer than expected to identify the failure. We mitigated the incident by reverting the runtime deployment to the previously stable version.
We've added monitoring and alerting for this class of tool-availability error to reduce time-to-detection. We're also adding regression tests for these built-in agent tools, and improving the shipping safety for future runtime rollouts to avoid similar issues.
Jun 28, 20:55 UTC
Update -
Copilot cloud agent had been experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. A fix has been deployed and we are validating that fix.
Jun 28, 20:02 UTC
Jun 28, 20:02 UTC
Update -
Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have validated a fix and are deploying that fix now.
Jun 28, 18:31 UTC
Jun 28, 18:31 UTC
Update -
Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have identified the issue and are validating a fix.
Jun 28, 17:59 UTC
Jun 28, 17:59 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Jun 28, 17:50 UTC
Jun 28, 17:50 UTC
Jun 27, 2026
Resolved -
This incident was used to notify for a maintenance event. There is no specific root cause analysis. Work progressed as planned without any issues to report.
Jun 27, 20:33 UTC
Jun 27, 20:33 UTC
Update -
Maintenance has completed and we've begun normalizing traffic in EU. We will monitor for a while longer before confirming resolution.
Jun 27, 20:19 UTC
Jun 27, 20:19 UTC
Update -
This is progressing as expected, but we're going to extend the maintenance window by a couple of hours. Our new expected completion time is 21:00 UTC.
Jun 27, 18:22 UTC
Jun 27, 18:22 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Jun 27, 14:04 UTC
Jun 27, 14:04 UTC
Update -
We are conducting routine maintenance on our network infrastructure in the EU. This will not impact production traffic, but may result in slightly increased latency for the remainder of our work. We expect this to last until 19:00 UTC.
Jun 27, 14:02 UTC
Jun 27, 14:02 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Jun 27, 14:02 UTC
Jun 27, 14:02 UTC
Jun 26, 2026
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe