GitHub header

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
99.99 % 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
100.0 % uptime
Today
Pull Requests Operational
90 days ago
99.99 % uptime
Today
Actions Operational
90 days ago
99.83 % uptime
Today
Packages Operational
90 days ago
100.0 % uptime
Today
Pages Operational
90 days ago
99.95 % uptime
Today
Copilot Operational
90 days ago
99.71 % 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.

No incidents or maintenance related to this downtime.

Feb 20, 2026
US - Incident with Copilot GPT-5.1-Codex
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.
Feb 20, 11:41 UTC
Update - The issues with our upstream model provider have been resolved, and GPT 5.1 Codex is once again available in Copilot Chat and across IDE integrations [VSCode, Visual Studio, JetBrains].
We will continue monitoring to ensure stability, but mitigation is complete.
Feb 20, 11:19 UTC
Update - We are still experiencing degraded availability for the GPT 5.1 Codex 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.
Feb 20, 10:36 UTC
Update - We are experiencing degraded availability for the GPT 5.1 Codex 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.
Other models are available and working as expected.
Feb 20, 10:02 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 20, 10:02 UTC
Feb 19, 2026

No incidents reported.

Feb 18, 2026

No incidents reported.

Feb 17, 2026

No incidents reported.

Feb 16, 2026

No incidents reported.

Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026
US - Disruption with some GitHub services regarding file upload
Resolved - On February 13, 2026, between 21:46 UTC and 22:58 UTC (72 minutes), the GitHub file upload service was degraded and users uploading from a web browser on GitHub.com were unable to upload files to repositories, create release assets, or upload manifest files. During the incident, successful upload completions dropped by ~85% from baseline levels. This was due to a code change that inadvertently modified browser request behavior and violated CORS (Cross-Origin Resource Sharing) policy requirements, causing upload requests to be blocked before reaching the upload service.

We mitigated the incident by reverting the code change that introduced the issue.

We are working to improve automated testing for browser-side request changes and to add monitoring/automated safeguards for upload flows to reduce our time to detection and mitigation of similar issues in the future.
Feb 13, 22:58 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 13, 22:30 UTC
Feb 12, 2026
US - Intermittent disruption with Copilot completions and inline suggestions
Resolved - Between February 11th 21:30 UTC and February 12th 15:40 UTC, users in Western Europe experienced degraded quality for all Next Edit Suggestions requests. Additionally, on February 12th, between 18:40 UTC and 20:30 UTC, users in Australia and South America experienced degraded quality and increased latency of up to 500ms for all Next Edit Suggestions requests. The root cause was a newly introduced regression in an upstream service dependency.

The incident was mitigated by failing over Next Edit Suggestions traffic to unaffected regions, which caused the increased latency. Once the regression was identified and rolled back, we restored the impacted capacity. We have improved our quality analysis tooling and are working on more robust quality impact alerting to accelerate detection of these issues in the future.
Feb 12, 16:50 UTC
Update - We are experiencing degraded availability in Western Europe for Copilot completions and suggestions. We are working to resolve the issue.
Feb 12, 15:33 UTC
Update - We are experiencing degraded availability in some regions for Copilot completions and suggestions. We are working to resolve the issue.
Feb 12, 14:08 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 12, 14:06 UTC
US - Disruption with some GitHub services
Resolved - From Feb 12, 2026 09:16:00 UTC to Feb 12, 2026 11:01 UTC, users attempting to download repository archives (tar.gz/zip) that include Git LFS objects received errors. Standard repository archives without LFS objects were not affected. On average, the archive download error rate was 0.0042% and peaked at 0.0339% of requests to the service. This was caused by deploying a corrupt configuration bundle, resulting in missing data used for network interface connections by the service.

We mitigated the incident by applying the correct configuration to each site. We have added checks for corruption in this deployment, and will add auto-rollback detection for this service to prevent issues like this in the future.
Feb 12, 11:12 UTC
Update - We have resolved the issue and are seeing full recovery.
Feb 12, 11:01 UTC
Update - We are investigating an issue with downloading repository archives that include Git LFS objects.
Feb 12, 10:39 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 12, 10:38 UTC
Feb 11, 2026

No incidents reported.

Feb 10, 2026
US - Copilot Policy Propagation Delays
Resolved - This incident has been resolved.
Feb 10, 10:01 UTC
Update - Copilot is operating normally.
Feb 10, 00:52 UTC
Update - We're continuing to address an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them.

This issue is understand and we are working to get the mitigation applied. Next update in one hour.
Feb 10, 00:26 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.

Next update in two hours.
Feb 9, 22:10 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.

Next update in two hours.
Feb 9, 20:39 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.

Next update in two hours.
Feb 9, 18:49 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.
Feb 9, 18:06 UTC
Update - We're continuing to investigate a an issue where Copilot policy updates are not propagating correctly for all customers.

This may prevent newly enabled models from appearing when users try to access them.
Feb 9, 17:24 UTC
Update - We’ve identified an issue where Copilot policy updates are not propagating correctly for some customers. This may prevent newly enabled models from appearing when users try to access them.

The team is actively investigating the cause and working on a resolution. We will provide updates as they become available.
Feb 9, 16:30 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 9, 16:29 UTC
Feb 9, 2026
Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026
US - Incident with Pull Requests
Resolved - On February 6, 2026, between 17:49 UTC and 18:36 UTC, the GitHub Mobile service was degraded, and some users were unable to create pull request review comments on deleted lines (and in some cases, comments on deleted files). This impacted users on the newer comment-positioning flow available in version 1.244.0 of the mobile apps. Telemetry indicated that the failures increased as the Android rollout progressed. This was due to a defect in the new comment-positioning workflow that could result in the server rejecting comment creation for certain deleted-line positions.

We mitigated the incident by halting the Android rollout and implementing interim client-side fallback behavior while a platform fix is in progress. The client-side fallback is scheduled to be published early this week. We are working to (1) add clearer client-side error handling (avoid infinite spinners), (2) improve monitoring/alerting for these failures, and (3) adopt stable diff identifiers for diff-based operations to reduce the likelihood of recurrence.
Feb 6, 18:36 UTC
Update - Some GitHub Mobile app users may be unable to add review comments on deleted lines in pull requests. We're working on a fix and expect to release it early next week.
Feb 6, 18:36 UTC
Update - Pull Requests is operating normally.
Feb 6, 18:04 UTC
Update - We're currently investigating an issue affecting the Mobile app that can prevent review comments from being posted on certain pull requests when commenting on deleted lines.
Feb 6, 18:01 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Feb 6, 17:49 UTC
← Incident History Powered by Atlassian Statuspage