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.65 % 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.

Mar 7, 2026

No incidents reported today.

Mar 6, 2026

No incidents reported.

Mar 5, 2026
US - Disruption with some GitHub services
Resolved - On March 5, 2026, between 12:53 UTC and 13:35 UTC, the Copilot mission control service was degraded. This resulted in empty responses returned for users' agent session lists across GitHub web surfaces. Impacted users were unable to see their lists of current and previous agent sessions in GitHub web surfaces. This was caused by an incorrect database query that falsely excluded records that have an absent field.

We mitigated the incident by rolling back the database query change. There were no data alterations nor deletions during the incident.

To prevent similar issues in the future, we're improving our monitoring depth to more easily detect degradation before changes are fully rolled out.
Mar 5, 01:30 UTC
Update - Copilot coding agent mission control is fully restored. Tasks are now listed as expected.
Mar 5, 01:30 UTC
Update - Users were temporarily unable to see tasks listed in mission control surfaces. The ability to submit new tasks, view existing tasks via direct link, or manage tasks was unaffected throughout. A revert is currently being deployed and we are seeing recovery.
Mar 5, 01:21 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 5, 01:13 UTC
US - Some OpenAI models degraded in Copilot
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.
Mar 5, 01:13 UTC
Update - The issues with our upstream model provider have been resolved, and gpt-5.3-codex is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete.
Mar 5, 01:13 UTC
Update - We are experiencing degraded availability for the gpt-5.3-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.
Mar 5, 00:53 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Mar 5, 00:47 UTC
Mar 4, 2026

No incidents reported.

Mar 3, 2026
US - Claude Opus 4.6 Fast not appearing for some Copilot users
Resolved - On March 3, 2026, between 19:44 UTC and 21:05 UTC, some GitHub Copilot users reported that the Claude Opus 4.6 Fast model was no longer available in their IDE model selection. After investigation, we confirmed that this was caused by enterprise administrators adjusting their organization's model policies, which correctly removed the model for users in those organizations. No users outside the affected organizations lost access.

We confirmed that the Copilot settings were functioning as designed, and all expected users retained access to the model. The incident was resolved once we verified that the change was intentional and no platform regression had occurred.
Mar 3, 21:11 UTC
Update - We believe that all expected users still have access to Claude Opus 4.6. We confirm that no users have lost access.
Mar 3, 21:05 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Mar 3, 20:31 UTC
US - Incident with Copilot and Actions
Resolved - On March 3, 2026, between 18:46 UTC and 20:09 UTC, GitHub experienced a period of degraded availability impacting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other dependent services. At the peak of the incident, GitHub.com request failures reached approximately 40%. During the same period, approximately 43% of GitHub API requests failed. Git operations over HTTP had an error rate of approximately 6%, while SSH was not impacted. GitHub Copilot requests had an error rate of approximately 21%. GitHub Actions experienced less than 1% impact.

This incident shared the same underlying cause as an incident in early February where we saw a large volume of writes to the user settings caching mechanism. While deploying a change to reduce the burden of these writes, a bug caused every user’s cache to expire, get recalculated, and get rewritten. The increased load caused replication delays that cascaded down to all affected services. We mitigated this issue by immediately rolling back the faulty deployment.

We understand these incidents disrupted the workflows of developers. While we have made substantial, long-term investments in how GitHub is built and operated to improve resilience, we acknowledge we have more work to do. Getting there requires deep architectural work that is already underway, as well as urgent, targeted improvements. We are taking the following immediate steps:

- We have added a killswitch and improved monitoring to the caching mechanism to ensure we are notified before there is user impact and can respond swiftly.
- We are moving the cache mechanism to a dedicated host, ensuring that any future issues will solely affect services that rely on it.
Mar 3, 20:09 UTC
Update - Copilot is operating normally.
Mar 3, 19:32 UTC
Update - We've identified the issue and have applied a mitigation. We're seeing recovery of services. We continue to montitor for full recovery.
Mar 3, 19:17 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Mar 3, 18:59 UTC
Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

No incidents reported.

Feb 26, 2026
US - Incident with Copilot
Resolved - On February 26, 2026, between 09:27 UTC and 10:36 UTC, the GitHub Copilot service was degraded and users experienced errors when using Copilot features including Copilot Chat, Copilot Coding Agent and Copilot Code Review. During this time, 5-15% of affected requests to the service returned errors.

The incident was resolved by infrastructure rebalancing.

We are improving observability to detect capacity imbalances earlier and enhancing our infrastructure to better handle traffic spikes.
Feb 26, 11:06 UTC
Update - Copilot is operating normally.
Feb 26, 11:06 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 26, 10:22 UTC
Feb 25, 2026
US - Incident with Copilot Agent Sessions impacting CCA/CCR
Resolved - On February 25, 2026, between 15:05 UTC and 16:34 UTC, the Copilot coding agent service was degraded, resulting in errors for 5% of all requests and impacting users starting or interacting with agent sessions.

This was due to an internal service dependency running out of allocated resources (memory and CPU). We mitigated the incident by adjusting the resource allocation for the affected service, which restored normal operations for the coding agent service.

We are working to implement proactive monitoring for resource exhaustion across our services, review and update resource allocations, and improve our alerting capabilities to reduce our time to detection and mitigation of similar issues in the future.
Feb 25, 16:44 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 25, 16:38 UTC
Feb 24, 2026

No incidents reported.

Feb 23, 2026
US - Incident with Copilot
Resolved - On February 23, 2026, between 14:45 UTC and 16:19 UTC, the Copilot service was degraded for Claude Haiku 4.5 model. On average, 6% of the requests to this model failed due to an issue with an upstream provider. During this period, automated model degradation notifications directed affected users to alternative models. No other models were impacted. The upstream provider identified and resolved the issue on their end.
We are working to improve automatic model failover mechanisms to reduce our time to mitigation of issues like this one in the future.
Feb 23, 16:19 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 23, 14:56 UTC
Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage