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

Apr 1, 2026

No incidents reported today.

Mar 31, 2026
US - Incident with Pull Requests: High percentage of 500s
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 31, 21:23 UTC
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Mar 31, 21:16 UTC
Update - We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.
Mar 31, 21:12 UTC
Update - Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.
Mar 31, 19:28 UTC
Update - We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.
Mar 31, 18:42 UTC
Update - We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.
Mar 31, 17:16 UTC
Update - We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.
Mar 31, 16:35 UTC
Update - We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.
Mar 31, 16:15 UTC
Update - We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.
Mar 31, 15:39 UTC
Update - We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.
Mar 31, 15:06 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Mar 31, 15:05 UTC
Mar 30, 2026

No incidents reported.

Mar 29, 2026

No incidents reported.

Mar 28, 2026

No incidents reported.

Mar 27, 2026

No incidents reported.

Mar 26, 2026

No incidents reported.

Mar 25, 2026

No incidents reported.

Mar 24, 2026
US - Teams Github Notifications App is down
Resolved - On March 24, 2026, between 15:57 UTC and 19:51 UTC, the Microsoft Teams Integration and Teams Copilot Integration services were degraded and unable to deliver GitHub event notifications to Microsoft Teams. On average, the error rate was 37.4% and peaked at 90.1% of requests to the service -- approximately 19% of all integration installs failed to receive GitHub-to-Teams notifications in this time period.

This was due to an outage at one of our upstream dependencies, which caused HTTP 500 errors and connection resets for our Teams integration.

We coordinated with the relevant service teams, and the issue was resolved at 19:51 UTC when the upstream incident was mitigated.

We are working to update observability and runbooks to reduce time to mitigation for issues like this in the future.
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.

← Incident History Powered by Atlassian Statuspage