Is GitHub Pages down?

We are investigating reports of degraded performance for Actions

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.

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

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

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

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

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

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

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.

Pages is operating normally.

Issues is operating normally.

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

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

API Requests is operating normally.

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

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

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

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.

We are investigating reports of degraded availability for Actions

Pages is experiencing degraded performance. We are continuing to investigate.

The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

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.

We are investigating reports of degraded performance for Actions

Approximately 5% 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.

We are continuing to work on a mitigation.

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

Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.

Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start. This has caused some customers to exceed their hosted compute concurrency and experience increased impact. We are continuing to working on infrastructure mitigations. Next update in one hour.

Pages is experiencing degraded performance. We are continuing to investigate.

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

We're seeing Actions and Pages recovery. For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing. GitHub pages builds were also failing during that period, but Pages are still accessible. We are continuing to monitor for full recovery.

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

We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog. Customers may see a small rate of  API and job failures as the system is recovering. Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery. Pages were accessible throughout the incident.

The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated. We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.

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.

We are investigating reports of degraded performance for Pages

We are investigating reports of slow and failing Pages deployments. Access to Pages is unaffected.

Pages deployment latency is recovering. The team continues working toward full mitigation and a return to nominal state.

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.

We are investigating reports of degraded performance for Actions and Pages

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

We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.

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

We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation

The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

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

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.