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.78
% uptime
Today
Webhooks
Operational
90 days ago
99.66
% uptime
Today
Visit www.githubstatus.com for more information
Operational
API Requests
Operational
90 days ago
99.95
% uptime
Today
Issues
Operational
90 days ago
99.77
% uptime
Today
Pull Requests
Operational
90 days ago
99.73
% uptime
Today
Actions
Operational
90 days ago
99.36
% uptime
Today
Packages
Operational
90 days ago
99.97
% uptime
Today
Pages
Operational
90 days ago
99.9
% uptime
Today
Codespaces
Operational
90 days ago
99.48
% uptime
Today
Copilot
Operational
90 days ago
99.71
% 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.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Apr 17, 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.
Apr 17, 15:18 UTC
Apr 17, 15:18 UTC
Monitoring -
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Apr 17, 15:18 UTC
Apr 17, 15:18 UTC
Update -
We have isolated a problematic component in our infrastructure and are working to mitigate. We will continue to post updates as we work toward resolution.
Apr 17, 15:08 UTC
Apr 17, 15:08 UTC
Update -
We are experiencing an issue that impacts approximately 10% of traffic to the web, resulting in slow and failed calls. We are investigating and will continue to post updates as we work toward mitigation.
Apr 17, 14:57 UTC
Apr 17, 14:57 UTC
Update -
Issues is experiencing degraded performance. We are continuing to investigate.
Apr 17, 14:56 UTC
Apr 17, 14:56 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 17, 14:56 UTC
Apr 17, 14:56 UTC
Apr 16, 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.
Apr 16, 18:28 UTC
Apr 16, 18:28 UTC
Monitoring -
The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
Apr 16, 18:22 UTC
Apr 16, 18:22 UTC
Update -
Our provider is implementing a mitigation and we are seeing signs of recovery.
Apr 16, 16:37 UTC
Apr 16, 16:37 UTC
Update -
We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.
Apr 16, 15:49 UTC
Apr 16, 15:49 UTC
Update -
Codespaces is experiencing degraded availability. We are continuing to investigate.
Apr 16, 15:41 UTC
Apr 16, 15:41 UTC
Update -
We are experiencing degraded performance in Codespaces related to creating a new Codespace or starting an existing Codespace from the VS Code editor. SSH connections to Codespaces are not impacted. We are working toward mitigation and will continue to keep you updated on progress.
Apr 16, 15:08 UTC
Apr 16, 15:08 UTC
Investigating -
We are investigating reports of degraded performance for Codespaces
Apr 16, 15:06 UTC
Apr 16, 15:06 UTC
Apr 15, 2026
No incidents reported.
Apr 14, 2026
Resolved -
On April 14, between 00:58 UTC and 06:08 UTC, GitHub Enterprise Cloud customers experienced 500 errors when attempting to access Copilot Insights pages which was caused by an authentication failure in our metrics pipeline. We fully mitigated the issue and validated the fix in production. Approximately 709 users were impacted. The total impact duration was approximately 5 hours and 10 minutes.
Our investigation determined the incident was caused by a change in a tenant credential which caused authentication errors to retrieve the required data needed on our Copilot Insights pages.
We understand this disruption impacted customers' ability to access the Copilot Insights page. To prevent similar issues and reduce resolution time in the future, we are investing in improved diagnostics tooling to quickly identify the root cause of failures, enhanced monitoring, and alerting to detect issues at a more granular level.
GitHub is a critical infrastructure for your work, your teams, and your businesses. We are focused on these remediations and continued reliability improvements for Copilot Insights and related metrics experiences.
Apr 14, 06:08 UTC
Our investigation determined the incident was caused by a change in a tenant credential which caused authentication errors to retrieve the required data needed on our Copilot Insights pages.
We understand this disruption impacted customers' ability to access the Copilot Insights page. To prevent similar issues and reduce resolution time in the future, we are investing in improved diagnostics tooling to quickly identify the root cause of failures, enhanced monitoring, and alerting to detect issues at a more granular level.
GitHub is a critical infrastructure for your work, your teams, and your businesses. We are focused on these remediations and continued reliability improvements for Copilot Insights and related metrics experiences.
Apr 14, 06:08 UTC
Update -
This incident has been resolved. We will continue to monitor to ensure stability. Thank you for your patience and understanding as we addressed this issue.
Apr 14, 06:07 UTC
Apr 14, 06:07 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Apr 14, 06:07 UTC
Apr 14, 06:07 UTC
Update -
We identified an issue that impacts the Copilot Dashboard on the Insights tab and are working on mitigation. We will continue to keep you updated on progress.
Apr 14, 04:40 UTC
Apr 14, 04:40 UTC
Update -
The team continues to investigate issues accessing with Copilot Dashboard on the Insights tab. We will continue providing updates on the progress towards mitigation.
Apr 14, 03:47 UTC
Apr 14, 03:47 UTC
Update -
The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.
Apr 14, 02:40 UTC
Apr 14, 02:40 UTC
Update -
Degradation of Service - Insights Page
Apr 14, 02:37 UTC
Apr 14, 02:37 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 14, 01:57 UTC
Apr 14, 01:57 UTC
Apr 13, 2026
Resolved -
On Sunday April 13th, 2026, between 18:53 UTC and 20:30 UTC, the GitHub Pages service experienced elevated error rates. On average, the error rate was 10.58% and peaked at 12.77% of requests to the service, resulting in approximately 17.5 million failed requests returning HTTP 500 errors. This was due to an automated DNS management tool (octodns) erroneously deleting a DNS record for a Pages backend storage host after its upstream data source intermittently failed to return the record, causing the tool to treat it as stale and remove it.
We mitigated the incident by re-creating the deleted DNS record. To prevent future incidents, we are implementing availability-zone-tolerant routing in the Pages frontend so that an unresolvable backend host triggers failover to healthy hosts rather than returning errors, adding safeguards to prevent automated deletion of DNS records owned by other systems, and improving logging and alerting for DNS resolution failures in the Pages serving path.
Apr 13, 20:35 UTC
We mitigated the incident by re-creating the deleted DNS record. To prevent future incidents, we are implementing availability-zone-tolerant routing in the Pages frontend so that an unresolvable backend host triggers failover to healthy hosts rather than returning errors, adding safeguards to prevent automated deletion of DNS records owned by other systems, and improving logging and alerting for DNS resolution failures in the Pages serving path.
Apr 13, 20:35 UTC
Update -
We have mitigated the issue with Pages.
Apr 13, 20:32 UTC
Apr 13, 20:32 UTC
Monitoring -
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
Apr 13, 20:30 UTC
Apr 13, 20:30 UTC
Update -
We are investigating reports of issues with Pages. We will continue to keep users updated on progress towards mitigation.
Apr 13, 19:57 UTC
Apr 13, 19:57 UTC
Investigating -
We are investigating reports of degraded availability for Pages
Apr 13, 19:56 UTC
Apr 13, 19:56 UTC
Resolved -
On April 13, 2026, between 14:41 UTC and 17:29 UTC, the Copilot service experienced degraded performance. All Copilot users were impacted by increased latency, and approximately 20% experienced request failures when interacting with Copilot Cloud Agent (CCA). On average, request latency increased to approximately 950ms. The GitHub User Dashboard also displayed intermittent errors loading Copilot quota information. CCA and the User Dashboard were impacted for approximately 2 hours and 56 minutes.
This was due to an infrastructure change that reduced the available compute capacity for a backend service responsible for Copilot rate limiting and quota management. The reduced capacity caused resource exhaustion under normal traffic load, leading to cascading failures in downstream request processing.
We mitigated the incident by increasing compute resources allocated to the affected service and scaling out the number of service instances to distribute load more effectively.
We are working to improve proactive capacity monitoring to detect resource degradation before it impacts users, reviewing retry and timeout configurations across dependent services to reduce amplification during degraded states, and evaluating connection management strategies to improve resilience under constrained resources.
Apr 13, 17:40 UTC
This was due to an infrastructure change that reduced the available compute capacity for a backend service responsible for Copilot rate limiting and quota management. The reduced capacity caused resource exhaustion under normal traffic load, leading to cascading failures in downstream request processing.
We mitigated the incident by increasing compute resources allocated to the affected service and scaling out the number of service instances to distribute load more effectively.
We are working to improve proactive capacity monitoring to detect resource degradation before it impacts users, reviewing retry and timeout configurations across dependent services to reduce amplification during degraded states, and evaluating connection management strategies to improve resilience under constrained resources.
Apr 13, 17:40 UTC
Update -
We have identified the root cause and are rolling out a fix for Copilot. The services should now be in recovery, with expected full recovery in 5 to 10 minutes.
Apr 13, 16:59 UTC
Apr 13, 16:59 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 13, 16:41 UTC
Apr 13, 16:41 UTC
Apr 12, 2026
No incidents reported.
Apr 11, 2026
No incidents reported.
Apr 10, 2026
Resolved -
On April 9, 2026, between 22:59 UTC and April 10, 2026, 13:24 UTC, the Copilot Mission Control service was degraded and did not display Claude and Codex Cloud Agent sessions in the agents tab dashboard. Customers were unable to see, list, or manage their third party agent sessions during this period. The underlying agent sessions continued to function normally. This was a visibility and management issue only, and no HTTP errors were generated. The API returned successful responses with incomplete results, with an average error rate of 0% and a maximum error rate of 0%. This was due to a code change that introduced a filter which inadvertently excluded third party agent sessions.
We mitigated the incident by reverting the problematic code change and deploying the fix to production.
We are working to add automated monitoring for dashboard content visibility and improve integration test coverage for third party agent session listing to reduce our time to detection and mitigation of issues like this one in the future.
Apr 10, 13:28 UTC
We mitigated the incident by reverting the problematic code change and deploying the fix to production.
We are working to add automated monitoring for dashboard content visibility and improve integration test coverage for third party agent session listing to reduce our time to detection and mitigation of issues like this one in the future.
Apr 10, 13:28 UTC
Update -
We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.
Apr 10, 13:08 UTC
Apr 10, 13:08 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 10, 13:07 UTC
Apr 10, 13:07 UTC
Apr 9, 2026
Resolved -
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15–40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.
This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.
We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.
This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
Apr 9, 20:36 UTC
This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.
We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.
This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
Apr 9, 20:36 UTC
Update -
We continue to investigate periodic delays in Copilot Cloud Agent job processing
Apr 9, 19:52 UTC
Apr 9, 19:52 UTC
Update -
We are continuing to investigate Copilot Cloud Agent job delays
Apr 9, 18:57 UTC
Apr 9, 18:57 UTC
Update -
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Apr 9, 17:48 UTC
Apr 9, 17:48 UTC
Update -
We are investigating delays processing Copilot Cloud Agent jobs
Apr 9, 16:57 UTC
Apr 9, 16:57 UTC
Update -
We are experiencing issues where jobs are being delayed to start for copilot coding agent
Apr 9, 16:20 UTC
Apr 9, 16:20 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 9, 16:20 UTC
Apr 9, 16:20 UTC
Resolved -
On April 9, 2026, between 09:05 UTC and 19:05 UTC, the Copilot coding agent service was degraded and users experienced significant delays starting new agent sessions. Approximately 84% of new agent session requests were delayed across four separate outage waves, with queue wait times peaking at 54 minutes compared to a normal baseline of 15–40 seconds. On average, the error rate was 83.9% and peaked at 97.5% of requests to the service. Approximately 22,700 workflow creations were delayed or failed during the incident.
This was due to a bug in our rate limiting logic that incorrectly applied a rate limit globally across all users, rather than scoping it to the individual installation that triggered the limit. A contributing factor was a surge in API traffic from a client update that increased requests to an internal endpoint by 3–4x, which accelerated rate limit exhaustion.
We mitigated the incident by disabling the faulty rate limit caching mechanism via feature flag and updating our service to use per-installation credentials for API calls, ensuring rate limits are correctly scoped to individual installations.
We have since added automated monitoring and alerting to detect this failure mode proactively, deployed fixes to reduce unnecessary API traffic through caching improvements, and are continuing work to further isolate rate limit scoping across client types to prevent similar issues in the future.
This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/2rqwxl8y7m0j
Apr 9, 10:15 UTC
This was due to a bug in our rate limiting logic that incorrectly applied a rate limit globally across all users, rather than scoping it to the individual installation that triggered the limit. A contributing factor was a surge in API traffic from a client update that increased requests to an internal endpoint by 3–4x, which accelerated rate limit exhaustion.
We mitigated the incident by disabling the faulty rate limit caching mechanism via feature flag and updating our service to use per-installation credentials for API calls, ensuring rate limits are correctly scoped to individual installations.
We have since added automated monitoring and alerting to detect this failure mode proactively, deployed fixes to reduce unnecessary API traffic through caching improvements, and are continuing work to further isolate rate limit scoping across client types to prevent similar issues in the future.
This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/2rqwxl8y7m0j
Apr 9, 10:15 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Apr 9, 10:15 UTC
Apr 9, 10:15 UTC
Update -
We are investigating an issue affecting GitHub Copilot coding agent. Users may experience significant delays when starting new agent sessions, with jobs remaining queued longer than expected. Our team has identified increased load as a contributing factor and is actively working to restore normal performance.
Apr 9, 09:57 UTC
Apr 9, 09:57 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 9, 09:50 UTC
Apr 9, 09:50 UTC
Resolved -
On April 9, 2026, between 03:22 UTC and 04:49 UTC, GitHub Notifications experienced degraded availability. During this time, approximately 45% of requests to the notifications service returned errors, with a peak error rate of approximately 54%, preventing affected users from successfully viewing or interacting with their notifications service. The issue was identified and resolved, restoring the service to full availability.
We are working to improve our metrics to reduce time to detection and mitigation for similar issues in the future.
Apr 9, 04:57 UTC
We are working to improve our metrics to reduce time to detection and mitigation for similar issues in the future.
Apr 9, 04:57 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Apr 9, 04:57 UTC
Apr 9, 04:57 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 9, 04:42 UTC
Apr 9, 04:42 UTC
Apr 8, 2026
No incidents reported.
Apr 7, 2026
No incidents reported.
Apr 6, 2026
No incidents reported.
Apr 5, 2026
No incidents reported.
Apr 4, 2026
No incidents reported.
Apr 3, 2026
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe