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

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

Mar 14, 2025

No incidents reported today.

Mar 13, 2025

No incidents reported.

Mar 12, 2025

Some Actions users are seeing their workflow jobs failing to start

Resolved - On March 12, 2025, between 13:28 UTC and 14:07 UTC, the Actions service experienced degradation leading to run start delays. During the incident, about 0.6% of workflow runs failed to start, 0.8% of workflow runs were delayed by an average of one hour, and 0.1% of runs ultimately ended with an infrastructure failure. The issue stemmed from connectivity problems between the Actions services and certain nodes within one of our Redis clusters. The service began recovering once connectivity to the Redis cluster was restored at 13:41 UTC. These connectivity issues are typically not a concern because we can fail over to healthier replicas. However, due to an unrelated issue, there was a replication delay at the time of the incident, and failing over would have caused a greater impact on our customers. We are working on improving our resiliency and automation processes for this infrastructure to improve the speed of diagnosing and resolving similar issues in the future.
Mar 12, 14:07 UTC

Update - We have applied a mitigation for the affected Redis node, and are starting to see recovery with Action workflow executions.
Mar 12, 13:55 UTC

Investigating - We are investigating reports of degraded performance for Actions
Mar 12, 13:28 UTC

Mar 11, 2025

No incidents reported.

Mar 10, 2025

No incidents reported.

Mar 9, 2025

No incidents reported.

Mar 8, 2025

Incident with Actions and Pages

Resolved - On March 8, 2025, between 17:16 UTC and 18:02 UTC, GitHub Actions and Pages services experienced degraded performance leading to delays in workflow runs and Pages deployments. During this time, 34% of Actions workflow runs experienced delays, and a small percentage of runs using GitHub-hosted runners failed to start. Additionally, Pages deployments for sites without a custom Actions workflow (93% of them) did not run, preventing new changes from being deployed.

An unexpected data shape led to crashes in some of our pods. We mitigated the incident by excluding the affected pods and correcting the data that led to the crashes. We’ve fixed the source of the unexpected data shape and have improved the overall resilience of our service against such occurrences.
Mar 8, 18:11 UTC

Update - Actions is operating normally.
Mar 8, 18:11 UTC

Update - Actions run start delays are mitigated. Actions runs that failed will need to be re-run. Impacted Pages updates will need to re-run their deployments.
Mar 8, 18:10 UTC

Update - Pages is operating normally.
Mar 8, 18:00 UTC

Update - We are investigating impact to Actions run start delays, about 40% of runs are not starting within five minutes and Pages deployments are impacted for GitHub hosted runners.
Mar 8, 17:50 UTC

Investigating - We are investigating reports of degraded performance for Actions and Pages
Mar 8, 17:45 UTC

Mar 7, 2025

Disruption with some GitHub services

Resolved - On March 7, 2025, from 09:30 UTC to 11:07 UTC, we experienced a networking event that disrupted connectivity to our search infrastructure, impacting about 25% of search queries and indexing attempts. Searches for PRs, Issues, Actions workflow runs, Packages, Releases, and other products were impacted, resulting in failed requests or stale data. The connectivity issue self-resolved after 90 minutes. The backlog of indexing jobs was fully processed and saw recovery soon after, and queries to all indexes also saw an immediate return to normal throughput.

We are working with our cloud provider to identify the root cause and are researching additional layers of redundancy to reduce customer impact in the future for issues like this one. We are also exploring mitigation strategies for faster resolution.
Mar 7, 11:24 UTC

Update - We continue investigating degraded experience with searching for issues, pull, requests and actions workflow runs.
Mar 7, 10:54 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Mar 7, 10:27 UTC

Update - Searches for issues and pull-requests may be slower than normal and timeout for some users
Mar 7, 10:12 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Mar 7, 10:06 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Mar 7, 10:05 UTC

Investigating - We are currently investigating this issue.
Mar 7, 10:03 UTC

Mar 6, 2025

No incidents reported.

Mar 5, 2025

No incidents reported.

Mar 4, 2025

No incidents reported.

Mar 3, 2025

Incident with Issues, Git Operations and API Requests

Resolved - On March 3rd 2025 between 04:07 UTC and 09:36 UTC various GitHub services were degraded with an average error rate of 0.03% and peak error rate of 9%. This issue impacted web requests, API requests, and git operations.

This incident was triggered because a network node in one of GitHub's datacenter sites partially failed, resulting in silent packet drops for traffic served by that site. At 09:22 UTC, we identified the failing network node, and at 09:36 UTC we addressed the issue by removing the faulty network node from production.

In response to this incident, we are improving our monitoring capabilities to identify and respond to similar silent errors more effectively in the future.
Mar 3, 05:31 UTC

Update - We have seen recovery across our services and impact is mitigated.
Mar 3, 05:30 UTC

Update - Git Operations is operating normally.
Mar 3, 05:20 UTC

Update - Webhooks is operating normally.
Mar 3, 05:20 UTC

Update - We are investigating intermittent connectivity issues between our backend and databases and will provide further updates as we have them. The current impact is you may see elevated latency while using our services.
Mar 3, 04:54 UTC

Update - We are seeing intermittent timeouts across our various services. We are currently investigating and will provide updates.
Mar 3, 04:23 UTC

Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Mar 3, 04:21 UTC

Investigating - We are investigating reports of degraded performance for API Requests, Git Operations and Issues
Mar 3, 04:20 UTC

Mar 2, 2025

No incidents reported.

Mar 1, 2025

Scheduled Codespaces Maintenance

Completed - The scheduled maintenance has been completed.
Mar 1, 02:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 28, 17:00 UTC

Scheduled - Codespaces will be undergoing maintenance in Europe and Southeast Asia from 17:00 UTC Friday February 28 to 02:00 UTC Saturday March 1. Maintenance will begin in North Europe at 17:00 UTC Friday February 28, followed by Southeast Asia, concluding in UK South. Each region will take 2-3 hours to complete.

During this time period, users may experience connectivity issues with new and existing Codespaces.

Please ensure that any uncommitted changes that you may need during the maintenance window are committed and pushed. Codespaces with any uncommitted changes will be accessible as usual once maintenance is complete.

Thank you for your patience as we work to improve our systems.
Feb 27, 21:09 UTC

Feb 28, 2025

Elevated Request Latency for Write operations on github.com and api.github.com

Resolved - On February 28th, 2025, between 05:49 UTC and 06:55 UTC, a newly deployed background job caused increased load on GitHub’s primary database hosts, resulting in connection pool exhaustion. This led to degraded performance, manifesting as increased latency for write operations and elevated request timeout rates across multiple services.

The incident was mitigated by halting execution of the problematic background job and disabling the feature flag controlling the job execution. To prevent similar incidents in the future, we are collaborating on a plan to improve our production signals to better detect and respond to query performance issues.
Feb 28, 06:55 UTC

Update - Issues and Pull Requests are experiencing degraded performance. We are continuing to investigate.
Feb 28, 06:29 UTC

Investigating - We are currently investigating this issue.
Feb 28, 06:12 UTC