GitHub Status Watch

Status board

Components

The last 90 days

to . Of these 90 days, 26 days had an incident, 31 days had no incident reported, and 33 days have no data.

Past incidents

Incident with Git Operations, Issues, Actions and Pull Requests

Critical impact GitHub |

  1. 17:17 UTC Investigating: We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
  2. 17:25 UTC Investigating: We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause.
  3. 17:27 UTC Monitoring: The degradation has been mitigated.
  4. 18:04 UTC Resolved: This incident has been resolved.

Incident with Git Operations, Pull Requests and Actions

Critical impact GitHub |

  1. 15:14 UTC Investigating: We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
  2. 15:14 UTC Investigating: Webhooks is experiencing degraded performance.
  3. 15:15 UTC Investigating: Issues is experiencing degraded performance.
  4. 16:25 UTC Resolved: This incident has been resolved.

Several services are degraded

Critical impact GitHub |

  1. 19:57 UTC Investigating: We are investigating reports of degraded performance for Pull Requests and Webhooks
  2. 20:04 UTC Investigating: Webhooks is operating normally.
  3. 20:12 UTC Investigating: Pull Requests is operating normally.
  4. 23:40 UTC Resolved: This incident has been resolved.

Disruption with some GitHub services

Major impact GitHub |

  1. 23:47 UTC Investigating: We are investigating reports of impacted performance for some GitHub services.
  2. 00:05 UTC Investigating: Users may experience issues accessing organization and enterprise billing and licensing pages.
  3. 01:32 UTC Resolved: This incident has been resolved.

Incident with Actions

Critical impact GitHub |

  1. 19:11 UTC Investigating: We are investigating reports of degraded performance for Actions
  2. 19:15 UTC Investigating: We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs.
  3. 19:50 UTC Investigating: We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations.
  4. 22:49 UTC Resolved: On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance.

No incidents reported.

No incidents reported.

No incidents reported.

Actions Job Delays

Minor impact GitHub |

  1. 14:47 UTC Investigating: We are investigating reports of degraded performance for Actions
  2. 14:54 UTC Investigating: We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix.
  3. 15:02 UTC Investigating: Run-start delays on Ubuntu runners have been resolved.
  4. 17:56 UTC Resolved: This incident has been resolved.

Elevated request latency

Minor impact GitHub |

  1. 13:37 UTC Investigating: We are investigating reports of impacted performance for some GitHub services.
  2. 13:39 UTC Investigating: We are investigating recurrent periods of elevated latency affecting web requests.
  3. 13:51 UTC Monitoring: The degradation has been mitigated.
  4. 13:57 UTC Resolved: On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com.

No incidents reported.

No incidents reported.

Copilot Code Review is unable to complete reviews

Critical impact GitHub |

  1. 21:16 UTC Investigating: We are investigating reports of impacted performance for some GitHub services.
  2. 21:23 UTC Investigating: Revert of the impacted change is in flight, expect full recovery once the deployment is done.
  3. 22:08 UTC Investigating: Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.
  4. 22:08 UTC Resolved: On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environment

No incidents reported.

No incidents reported.

No incidents reported.

Disruption with billing information updates

Minor impact GitHub |

  1. 16:51 UTC Investigating: We are investigating reports of impacted performance for some GitHub services.
  2. 16:51 UTC Investigating: We are investigating failures on billing information updates.
  3. 17:40 UTC Investigating: We have identified the problem and are actively working on mitigation.
  4. 20:41 UTC Resolved: Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information becaus

Earlier incidents

Where this comes from

Every state and incident here is the operator's own, as published on:

Covers 12 August to 7 October 2026; sources read up to Wednesday 7 October 2026, UTC.
How this page is made: a HiveBoss Bee gathers the operator's own status page, and every entry links to its source.
The words were written by AI; check the original before relying on them.