GitHub Status

Resolved: From Nov 18, 2025 20:30 UTC to Nov 18, 2025 21:34 UTC we experienced failures on all Git operations, including both SSH and HTTP Git client interactions, as well as raw file access. These failures also impacted products that rely on Git operations.

The root cause was an expired TLS certificate used for internal service-to-service communication. We mitigated the incident by replacing the expired certificate and restarting impacted services. Once those services were restarted we saw a full recovery.

We have updated our alerting to cover the expired certificate and are performing an audit of other certificates in this area to ensure they also have the proper alerting and automation before expiration. In parallel, we are accelerating efforts to eliminate our remaining manually managed certificates, ensuring all service-to-service communication is fully automated and aligned with modern security practices.

Investigating: Git Operations is operating normally.

Investigating: We are seeing full recovery after rolling out the fix and all services are operational.

Investigating: Codespaces is operating normally.

Investigating: We have shipped a fix and are seeing recovery in some areas and will continue to provide updates.

Investigating: We have identified the likely cause of the incident and are working on a fix. We will provide another update as we get closer to deploying the fix.

Investigating: Codespaces is experiencing degraded availability. We are continuing to investigate.

Investigating: We are currently investigating failures on all Git operations, including both SSH and HTTP.

Investigating: We are seeing failures for some git http operations and are investigating

Investigating: Git Operations is experiencing degraded availability. We are continuing to investigate.

Investigating: We are currently investigating this issue.

Resolved: On November 19, between 17:36 UTC and 18:04 UTC, GitHub Actions service experienced degraded performance that caused excessive latency in queueing and updating workflow runs and job statuses. Operations related to artifacts, cache, job steps and logs also had significantly increased latency. At peak, 67% of workflow jobs queued during that timeframe were impacted, and the median latency for impacted operations increased by up to 35x.

This was caused by a significant change in load pattern on Actions Cache-related operations, leading to a saturated shared resource on the backend. The impact was mitigated by mitigating the new load pattern.

To reduce the likelihood of a recurrence, we are improving rate-limiting measures in this area to ensure a more consistent experience for all customers. We are also evaluating changes to reduce the scope of impact.

Investigating: We have applied mitigation and are seeing recovery

Investigating: We are investigating delays in actions runs and possible errors in artifact and cache creation.

Investigating: We are investigating reports of degraded performance for Actions

Resolved: From Nov 18, 2025 20:30 UTC to Nov 18, 2025 21:34 UTC we experienced failures on all Git operations, including both SSH and HTTP Git client interactions, as well as raw file access. These failures also impacted products that rely on Git operations.

The root cause was an expired TLS certificate used for internal service-to-service communication. We mitigated the incident by replacing the expired certificate and restarting impacted services. Once those services were restarted we saw a full recovery.

We have updated our alerting to cover the expired certificate and are performing an audit of other certificates in this area to ensure they also have the proper alerting and automation before expiration. In parallel, we are accelerating efforts to eliminate our remaining manually managed certificates, ensuring all service-to-service communication is fully automated and aligned with modern security practices.

Investigating: Git Operations is operating normally.

Investigating: We are seeing full recovery after rolling out the fix and all services are operational.

Investigating: Codespaces is operating normally.

Investigating: We have shipped a fix and are seeing recovery in some areas and will continue to provide updates.

Investigating: We have identified the likely cause of the incident and are working on a fix. We will provide another update as we get closer to deploying the fix.

Investigating: Codespaces is experiencing degraded availability. We are continuing to investigate.

Investigating: We are currently investigating failures on all Git operations, including both SSH and HTTP.

Investigating: We are seeing failures for some git http operations and are investigating

Investigating: Git Operations is experiencing degraded availability. We are continuing to investigate.

Investigating: We are currently investigating this issue.