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
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
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.66 % 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 26, 2026

No incidents reported today.

Mar 25, 2026

No incidents reported.

Mar 24, 2026
US - Teams Github Notifications App is down
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 24, 19:51 UTC
Update - We are experiencing degraded availability from Azure Teams APIs, which is impacting notifications from GitHub to Microsoft Teams. We are awaiting resolution from Azure.
Mar 24, 18:51 UTC
Update - We are experiencing degraded availability from Azure APIs, which is impacting notifications from GitHub to Microsoft Teams. We are working with Azure to resolve the issue.
Mar 24, 17:43 UTC
Update - We found an issue impacting notifications from GitHub to Microsoft Teams. We are working on mitigation and will keep users updated on progress towards mitigation.
Mar 24, 17:09 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 24, 17:00 UTC
Mar 23, 2026

No incidents reported.

Mar 22, 2026

No incidents reported.

Mar 21, 2026

No incidents reported.

Mar 20, 2026
US - Disruption with Copilot Coding Agent Sessions
Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and
peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its
backing datastore.

We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first.

We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.
Mar 20, 01:58 UTC
Update - We are rolling out our mitigation and are seeing recovery.
Mar 20, 01:26 UTC
Update - We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation.
Mar 20, 01:00 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 20, 00:58 UTC
Mar 19, 2026
US - Issues with Copilot Coding Agent
Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and
peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its
backing datastore.

We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first.

We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.
Mar 19, 14:32 UTC
Monitoring - Copilot is operating normally.
Mar 19, 14:32 UTC
Update - We are investigating reports that Copilot Coding Agent session logs are not available in the UI.
Mar 19, 14:02 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Mar 19, 13:45 UTC
Update - We are investigating reports of Copilot coding agent session logs not loading and sessions intermittently not starting. Users are able to see their tasks and create new ones.
Mar 19, 12:32 UTC
Update - We have resolved the underlying credential issue and have verified that users can see and interact with their Copilot Coding Agent tasks.

We are now investigating issues with some Coding Agent tasks completing successfully.
Mar 19, 12:00 UTC
Update - We believe we have identified an underlying credential issue and are working to resolve that across impacted environments.
Mar 19, 11:19 UTC
Update - We are investigating reports of errors when accessing Copilot Coding Agent features. Users may be unable to view or start coding agent tasks through the Agents interface. Our engineers are actively working to restore full functionality.
Mar 19, 10:43 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 19, 10:41 UTC
Mar 18, 2026

No incidents reported.

Mar 17, 2026

No incidents reported.

Mar 16, 2026
US - Disruption with some GitHub services
Resolved - On 16 March 2026, between 14:16 UTC and 15:18 UTC, Codespaces users encountered a download failure error message when starting newly created or resumed codespaces. At peak, 96% of the created or resumed codespaces were impacted. Active codespaces with a running VSCode environment were not affected.

The error was a result of an API deployment issue with our VS Code remote experience dependency and was resolved by rolling back that deployment. We are working with our partners to reduce our incident engagement time, improve early detection before they impact our customers, and ensure safe rollout of similar changes in the future.
Mar 16, 15:28 UTC
Update - Errors starting or resuming Codespaces have resolved.
Mar 16, 15:27 UTC
Update - We are investigating reports of users experiencing errors when starting or connecting to Codespaces. Some users may be unable to access their development environments during this time. We are working to identify the root cause and will implement a fix as soon as possible.
Mar 16, 15:06 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 16, 15:01 UTC
Mar 15, 2026

No incidents reported.

Mar 14, 2026

No incidents reported.

Mar 13, 2026

No incidents reported.

Mar 12, 2026
US - Copilot Metrics unaccessible
Resolved - GitHub Enterprise cloud customers with data residency in the Central US region were unable to access Copilot usage metrics, billing usage reports, Actions usage metrics, and API Insights data between March 12 at 13:09 UTC through March 12 at 16:14 UTC. We fully mitigated the issue on March 12 at 16:14 UTC after an outage that affected our data analytics infrastructure in this region was fixed. Most services recovered by 16:07 UTC, with full resolution at 16:14 UTC. The total impact duration was approximately 3 hours.

Our investigation determined the incident was caused by an infrastructure outage affecting our data analytics infrastructure in the Central US region. Beginning at approximately 13:09 UTC, keepalive signals dropped to zero across our affected clusters. Our services recovered progressively as the affected infrastructure came back online.

We understand this disruption impacted visibility into Copilot usage, billing usage, and Actions metrics for customers who rely on this data to manage their organizations and businesses. We have taken the following immediate steps:

- Engaged our infrastructure provider to improve resilience against similar regional outages.
- Evaluated our monitoring coverage to reduce detection time for infrastructure dependencies.
- Identified graceful degradation options to be implemented to mitigate in the future.

GitHub is critical infrastructure for your work, your teams, and your businesses. We are focused on these mitigations and continued improvements so usage metrics and dependent services remain reliably available.
Mar 12, 16:14 UTC
Update - Our database infrastructure has recovered and affected services are now operational. Users can access Copilot usage metrics, billing usage reports, action usage metrics, and API Insights. We are continuing to monitor service stability closely.
Mar 12, 16:14 UTC
Update - Beginning at approximately 1:20pm UTC, users are unable to access Copilot usage metrics, billing usage reports, action usage metrics, and API Insights due to database infrastructure issues. Recovery is in progress. We are monitoring progress closely. We'll post another update by 5:30pm UTC.
Mar 12, 15:52 UTC
Update - Beginning at approximately 1:20pm UTC, users are unable to access Copilot usage metrics and dashboards. We are investigating the root cause and working to restore service. We'll post another update by 3:30pm UTC.
Mar 12, 15:00 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 12, 14:58 UTC
← Incident History Powered by Atlassian Statuspage