Subscribe to UpdatesSubscribe
Get email notifications whenever GitHub Enterprise Cloud - EU creates, updates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
All Systems Operational
About This Site
For the status of GitHub.com, please visit: githubstatus.com
Uptime over the past 90 days. View historical uptime.
Git Operations
Operational
90 days ago
100.0
% uptime
Today
Webhooks
Operational
90 days ago
100.0
% uptime
Today
API Requests
Operational
90 days ago
100.0
% uptime
Today
Issues
Operational
90 days ago
99.96
% uptime
Today
Pull Requests
Operational
90 days ago
99.91
% uptime
Today
Actions
Operational
90 days ago
99.83
% uptime
Today
Copilot
Operational
90 days ago
99.76
% uptime
Today
Packages
Operational
90 days ago
100.0
% uptime
Today
Copilot AI Model Providers
Operational
90 days ago
100.0
% uptime
Today
Pages
Operational
90 days ago
99.95
% 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 27, 2026
No incidents reported today.
Apr 26, 2026
No incidents reported.
Apr 25, 2026
No incidents reported.
Apr 24, 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 24, 01:20 UTC
Apr 24, 01:20 UTC
Update -
Issues is operating normally.
Apr 24, 01:16 UTC
Apr 24, 01:16 UTC
Update -
We have identified the issue with missing search data and are working to restore it.
Apr 24, 00:51 UTC
Apr 24, 00:51 UTC
Update -
Issues is experiencing degraded availability. We are continuing to investigate.
Apr 24, 00:33 UTC
Apr 24, 00:33 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 23, 23:58 UTC
Apr 23, 23:58 UTC
Apr 23, 2026
Resolved -
On April 23, 2026, between 16:05 UTC and 20:43 UTC, the Pull Requests service experienced a regression affecting merge queue operations. PRs merged via merge queue using the squash merge method produced incorrect merge commits when the merge group contained more than one PR. In affected cases, changes from previously merged PRs and prior commits were inadvertently reverted by subsequent merges.
During the impact window 2,092 pull requests were affected. The issue did not affect pull requests merged outside of merge queue, nor merge queue groups using the merge or rebase methods.
It took approximately 3 hours and 33 minutes to identify the issue. The change completed deployment at approximately 16:05 UTC, and we became aware at 19:38 UTC following an increase in customer support inquiries. Because the issue affected merge commit correctness rather than availability, it was not detected by existing automated monitoring and was identified through customer reports.
The regression was introduced by a new code path that adjusted merge base computation for merge queue ref updates. This code path was intended to be gated behind a feature flag for an unreleased feature, but the gating was incomplete.
As a result, the new behavior was inadvertently applied to squash merge groups, producing an incorrect three-way merge. This caused subsequent squash merges to revert changes from earlier pull requests and, in some cases, changes between their starting points.
We mitigated the incident by reverting the code change and force-deploying the fix across all environments. After resolution, we identified affected repositories and sent targeted remediation instructions to repository administrators with step-by-step recovery guidance.
The regression was not identified during internal validation. Existing test coverage primarily exercised single-PR merge queue groups, which did not exhibit the faulty base-reference calculation. Because automated checks did not validate merge correctness for multi-PR squash groups, the defect surfaced only in production.
To prevent recurrence, GitHub is expanding test coverage for merge correctness validation. We are broadening automated coverage for merge queue operations, including regression checks that validate resulting Git contents across supported configurations, so issues affecting merge correctness are caught before reaching production.
We are committed to ensuring the correctness and reliability of merge queue operations. These actions will reduce the risk of similar regressions and improve confidence in future changes to the Pull Requests service.
Apr 23, 21:43 UTC
During the impact window 2,092 pull requests were affected. The issue did not affect pull requests merged outside of merge queue, nor merge queue groups using the merge or rebase methods.
It took approximately 3 hours and 33 minutes to identify the issue. The change completed deployment at approximately 16:05 UTC, and we became aware at 19:38 UTC following an increase in customer support inquiries. Because the issue affected merge commit correctness rather than availability, it was not detected by existing automated monitoring and was identified through customer reports.
The regression was introduced by a new code path that adjusted merge base computation for merge queue ref updates. This code path was intended to be gated behind a feature flag for an unreleased feature, but the gating was incomplete.
As a result, the new behavior was inadvertently applied to squash merge groups, producing an incorrect three-way merge. This caused subsequent squash merges to revert changes from earlier pull requests and, in some cases, changes between their starting points.
We mitigated the incident by reverting the code change and force-deploying the fix across all environments. After resolution, we identified affected repositories and sent targeted remediation instructions to repository administrators with step-by-step recovery guidance.
The regression was not identified during internal validation. Existing test coverage primarily exercised single-PR merge queue groups, which did not exhibit the faulty base-reference calculation. Because automated checks did not validate merge correctness for multi-PR squash groups, the defect surfaced only in production.
To prevent recurrence, GitHub is expanding test coverage for merge correctness validation. We are broadening automated coverage for merge queue operations, including regression checks that validate resulting Git contents across supported configurations, so issues affecting merge correctness are caught before reaching production.
We are committed to ensuring the correctness and reliability of merge queue operations. These actions will reduce the risk of similar regressions and improve confidence in future changes to the Pull Requests service.
Apr 23, 21:43 UTC
Update -
Pull Requests is operating normally.
Apr 23, 21:38 UTC
Apr 23, 21:38 UTC
Update -
We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.
Apr 23, 19:58 UTC
Apr 23, 19:58 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests
Apr 23, 19:50 UTC
Apr 23, 19:50 UTC
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 23, 19:42 UTC
Apr 23, 19:42 UTC
Update -
We have identified the root cause of the issue and are working on mitigation.
Apr 23, 19:33 UTC
Apr 23, 19:33 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 23, 19:29 UTC
Apr 23, 19:29 UTC
Resolved -
Between 06:07 and 06:57 UTC, during a routine OS upgrade to our search infrastructure, a pre-existing corruption on one of our coordinator nodes in a single availability zone caused it to stop serving requests. As a result, search query requests routed to that availability zone were dropped, affecting approximately 142,000 requests over the course of the incident. The issue was resolved by provisioning additional coordinator nodes in the availability zone to restore capacity, after which the corrupted node was decommissioned.
Apr 23, 05:00 UTC
Apr 23, 05:00 UTC
Apr 22, 2026
Resolved -
On April 22, 2026, between 09:00 UTC and 22:05 UTC, the Copilot coding agent and pull request comment event processing were degraded. During this period, approximately 0.5% of total pull request and issue comments mentioned @copilot (~23,000 invocations), explicitly requested work from the Copilot coding agent but were not acted upon.
Creating, viewing, and replying to pull request comments was unaffected, and other Copilot
functionality continued to operate normally. The impact was limited to @copilot mentions on pull request comments not triggering Copilot coding agent runs, and to some downstream systems not receiving new pull request comment events during the impact window.
The cause was a serialization error that prevented pull request comment events from being published to downstream consumers, including the Copilot coding agent. This was related to the same class of issue as incident #4295 on April 20, affecting a another event type.
We mitigated the incident by deploying a fix that restored event publishing, after which the Copilot coding agent and other downstream consumers resumed processing pull request comment events normally.
We are working to complete our audit of related event schemas, migrate remaining consumers to use
the updated identifier fields, and improve monitoring to detect drops in publishing on critical event topics, to reduce our time to detection and mitigation of issues like this one in the future.
Apr 22, 22:44 UTC
Creating, viewing, and replying to pull request comments was unaffected, and other Copilot
functionality continued to operate normally. The impact was limited to @copilot mentions on pull request comments not triggering Copilot coding agent runs, and to some downstream systems not receiving new pull request comment events during the impact window.
The cause was a serialization error that prevented pull request comment events from being published to downstream consumers, including the Copilot coding agent. This was related to the same class of issue as incident #4295 on April 20, affecting a another event type.
We mitigated the incident by deploying a fix that restored event publishing, after which the Copilot coding agent and other downstream consumers resumed processing pull request comment events normally.
We are working to complete our audit of related event schemas, migrate remaining consumers to use
the updated identifier fields, and improve monitoring to detect drops in publishing on critical event topics, to reduce our time to detection and mitigation of issues like this one in the future.
Apr 22, 22:44 UTC
Update -
We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.
Apr 22, 22:09 UTC
Apr 22, 22:09 UTC
Update -
We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.
Apr 22, 20:37 UTC
Apr 22, 20:37 UTC
Update -
Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.
Apr 22, 20:02 UTC
Apr 22, 20:02 UTC
Update -
Issues is experiencing degraded performance. We are continuing to investigate.
Apr 22, 19:55 UTC
Apr 22, 19:55 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 22, 19:53 UTC
Apr 22, 19:53 UTC
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 22, 19:18 UTC
Apr 22, 19:18 UTC
Update -
Copilot cloud agent and chat are mitigated for github.com.
Apr 22, 18:05 UTC
Apr 22, 18:05 UTC
Update -
We are now seeing recovery for Copilot cloud agent.
Apr 22, 17:49 UTC
Apr 22, 17:49 UTC
Update -
Mitigation is progressing for Copilot chat and cloud agent recovery.
Apr 22, 17:40 UTC
Apr 22, 17:40 UTC
Update -
Mitigation is progressing for Copilot chat and cloud agent.
Apr 22, 16:58 UTC
Apr 22, 16:58 UTC
Update -
We continue to work on mitigation for Copilot chat and cloud agent.
Apr 22, 16:24 UTC
Apr 22, 16:24 UTC
Update -
We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.
Apr 22, 15:43 UTC
Apr 22, 15:43 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Apr 22, 15:35 UTC
Apr 22, 15:35 UTC
Apr 21, 2026
No incidents reported.
Apr 20, 2026
No incidents reported.
Apr 19, 2026
No incidents reported.
Apr 18, 2026
No incidents reported.
Apr 17, 2026
No incidents reported.
Apr 16, 2026
No incidents reported.
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, 02:16 UTC
Apr 14, 02:16 UTC
Apr 13, 2026
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe