GitHub Status

All Systems Operational

About This Site

For the status of GitHub Enterprise Cloud - EU, please visit: eu.githubstatus.com
For the status of GitHub Enterprise Cloud - Australia, please visit: au.githubstatus.com
For the status of GitHub Enterprise Cloud - US, please visit: us.githubstatus.com

Git Operations Operational

Webhooks Operational

Visit www.githubstatus.com for more information Operational

API Requests Operational

Issues Operational

Pull Requests Operational

Actions Operational

Packages Operational

Pages Operational

Codespaces Operational

Copilot Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Sep 16, 2025

No incidents reported today.

Sep 15, 2025

Repository search is degraded

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.
Sep 15, 21:01 UTC

Update - Most searchable repositories should again be visible in search results. Up to 1.5% of repositories may still be missing from search results.

Many different actions synchronize the repository state with the search index, so we expect natural recovery for repositories that see more frequent user and API-driven interactions.

A complete index reconciliation is underway to restore stagnant repositories that were deleted from the index. We will update again once we have a clear timeline of when we expect full recovery for those missing search results.
Sep 13, 22:39 UTC

Update - Customers are not seeing repositories they expect to see in search results. We have restored a snapshot of this search index from Fri 12 Sep at 21:00 UTC. Changes made since then will be unavailable while we work to backfill the rest of the search index. Any new changes will be available in near-real time as expected.
Sep 13, 12:49 UTC

Investigating - We are currently investigating this issue.
Sep 13, 12:44 UTC

Disruption with some GitHub services

Investigating - We are currently investigating this issue.
Sep 15, 18:21 UTC

Sep 14, 2025

No incidents reported.

Sep 13, 2025

Sep 12, 2025

No incidents reported.

Sep 11, 2025

No incidents reported.

Sep 10, 2025

Incident with Actions

Resolved - On September 10, 2025 between 13:00 and 14:15 UTC, Actions users experienced failed jobs and run start delays for Ubuntu 24 and Ubuntu 22 jobs on standard runners in private repositories. Additionally, larger runner customers experienced run start delays for runner groups with private networking configured in the eastus2 region. This was due to an outage in an underlying compute service provider in eastus2. 1.06% of Ubuntu 24 jobs and 0.16% of Ubuntu 22 jobs failed during this period. Jobs for larger runners using private networking in the eastus2 region were unable to start for the duration of the incident.

We have identified and are working on improvements in our resilience to single partner region outages for standard runners so impact is reduced in similar scenarios in the future.
Sep 10, 14:02 UTC

Update - Actions hosted runners are taking longer to come online, leading to high wait times or job failures.
Sep 10, 13:31 UTC

Investigating - We are investigating reports of degraded performance for Actions
Sep 10, 13:23 UTC

Sep 9, 2025

No incidents reported.

Sep 8, 2025

No incidents reported.

Sep 7, 2025

No incidents reported.

Sep 6, 2025

No incidents reported.

Sep 5, 2025

No incidents reported.

Sep 4, 2025

Degraded REST API success rates for some customers

Resolved - On September 4, 2025 between 15:30 UTC and 20:00 UTC the REST API endpoints git/refs, git/refs/*, and git/matching-refs/* were degraded and returned elevated errors for repositories with reference counts over 22k. On average, the request error rate to these specific endpoints was 0.5%. Overall REST API availability remained 99.9999%. This was due to the introduction of a code change that added latency to reference evaluations and overly affected repositories with many branches, tags, or other references.

We mitigated the incident by reverting the new code.

We are working to improve performance testing and to reduce our time to detection and mitigation of issues like this one in the future.
Sep 4, 20:25 UTC

Update - The deployment has completed and we expect customers who have been impacted to see recovery. We are continuing to monitor.
Sep 4, 20:05 UTC

Update - We are in the process of deploying the PR to revert the change that was causing timeouts to this endpoint. We will update again once that deployment is complete.
Sep 4, 19:28 UTC

Update - We have identified a deployed change that correlates with the increase in 5XX errors to the GitRefs REST API. This is particularly affecting requests for repos with very large numbers of commits. We are working on rolling back this change which we expect will resolve the issue.
Sep 4, 18:57 UTC

Update - API Requests is experiencing degraded performance. We are continuing to investigate.
Sep 4, 18:52 UTC

Update - Customers are experiencing 504 responses for some API requests for regarding repo refs/tags. We are investigating.
Sep 4, 18:18 UTC

Investigating - We are currently investigating this issue.
Sep 4, 18:16 UTC

Sep 3, 2025

No incidents reported.

Sep 2, 2025

Loading avatars might fail for a 0.5% of total users and 100% users around the Arabian Peninsula. We are investigating.

Resolved - Between August 21, 2025 at 15:00 UTC, and September 2, 2025 at 15:22 UTC the avatars.githubusercontent.com image service was degraded and failed to display user avatars for users in the Middle East. During this time, avatar images appeared broken on github.com for affected users. On average, this impacted about 82% of users routed through one of our Middle East-based points-of-presence, which represents about 0.14% of global users.

This was due to a configuration change within GitHub's edge infrastructure in the affected region, causing HTTP requests to fail. As a result, image requests returned HTTP 503 errors. The failure to detect the issues was the result of an alerting threshold set too low.

We mitigated the incident by removing the affected site from service, which restored avatar serving for impacted users.

To prevent this from recurring, we have tuned configuration defaults for graceful degradation. We also added new health checks to automatically shift traffic from impacted sites. We are updating our monitoring to prevent undetected errors like this in the future.
Sep 2, 15:44 UTC

Investigating - We are currently investigating this issue.
Sep 2, 15:17 UTC