GitHub Status

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.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.

Investigating: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Issues and Webhooks

Resolved: Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.

Monitoring: Actions has fully recovered, and we will continue to monitor the platform to ensure stability.

Monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.

Investigating: API Requests is operating normally.

Investigating: Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.

Investigating: API Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: Issues is operating normally.

Investigating: Pages is operating normally.

Investigating: We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.

A separate incident was opened before we understood they were related. We will continue to post updates on this incident.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions and Pages are experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

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

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

Investigating: We have identified the cause of failures in GitHub Actions and are working to restore service.

Investigating: We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.

Investigating: We are investigating reports of degraded performance for Actions

Resolved: Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.

Monitoring: Actions has fully recovered, and we will continue to monitor the platform to ensure stability.

Monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.

Investigating: API Requests is operating normally.

Investigating: Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.

Investigating: API Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: Issues is operating normally.

Investigating: Pages is operating normally.

Investigating: We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.

A separate incident was opened before we understood they were related. We will continue to post updates on this incident.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions and Pages are experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

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

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

Investigating: We have identified the cause of failures in GitHub Actions and are working to restore service.

Investigating: We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.

Investigating: We are investigating reports of degraded performance for Actions

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.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.

Investigating: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Issues and Webhooks

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.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.

Investigating: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Issues and Webhooks

Resolved: Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.

Monitoring: Actions has fully recovered, and we will continue to monitor the platform to ensure stability.

Monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.

Investigating: API Requests is operating normally.

Investigating: Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.

Investigating: API Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: Issues is operating normally.

Investigating: Pages is operating normally.

Investigating: We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.

A separate incident was opened before we understood they were related. We will continue to post updates on this incident.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions and Pages are experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

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

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

Investigating: We have identified the cause of failures in GitHub Actions and are working to restore service.

Investigating: We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.

Investigating: We are investigating reports of degraded performance for Actions

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.

Monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.

Investigating: We are investigating reports of degraded performance for Actions

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.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.

Investigating: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Issues and Webhooks

Resolved: Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.

Monitoring: Actions has fully recovered, and we will continue to monitor the platform to ensure stability.

Monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Investigating: We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.

Investigating: API Requests is operating normally.

Investigating: Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.

Investigating: API Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: Issues is operating normally.

Investigating: Pages is operating normally.

Investigating: We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.

A separate incident was opened before we understood they were related. We will continue to post updates on this incident.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions and Pages are experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

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

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

Investigating: We have identified the cause of failures in GitHub Actions and are working to restore service.

Investigating: We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.

Investigating: We are investigating reports of degraded performance for Actions

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.

Investigating: We are seeing signs of sustained recovery from the upstream provider for GPT 5.3 Codex requests. Requests are succeeding as expected. We are awaiting confirmation from the provider that the issue is fully mitigated before resolving this incident.

Investigating: The upstream provider continues to return intermittent errors for GPT 5.3 Codex requests. Some users may experience failed or interrupted responses when using this model. Traffic continues to be automatically rerouted to reduce impact, and we are actively working with the upstream provider on a resolution. In the meantime, selecting an alternative model will avoid disruption.

Investigating: We identified that an upstream provider is returning errors for GPT 5.3 Codex requests, causing some users to experience failed or interrupted responses. Traffic is being automatically rerouted to mitigate impact. We are working with the upstream provider to resolve the underlying issue. We recommend using a different model at this time while we resolve the problem.

Investigating: We are investigating GPT Codex 5.3 performance.

Investigating: We are investigating reports of degraded performance for Copilot AI Model Providers