GitHubStatus
@githubstatus.grf.xyz
This profile is not officially endorsed or managed by GitHub.
@gabrf.bsky.social
@gabrf.bsky.social
Disruption with some GitHub services - Resolved
On January 22, 2026, our authentication service experienced an issue between 14:00 UTC and 14:50 UTC, resulting in downstream disruptions for users.
#cqb5hcy0gx18
On January 22, 2026, our authentication service experienced an issue between 14:00 UTC and 14:50 UTC, resulting in downstream disruptions for users.
#cqb5hcy0gx18
January 27, 2026 at 8:30 PM
Disruption with some GitHub services - Resolved
On January 22, 2026, our authentication service experienced an issue between 14:00 UTC and 14:50 UTC, resulting in downstream disruptions for users.
#cqb5hcy0gx18
On January 22, 2026, our authentication service experienced an issue between 14:00 UTC and 14:50 UTC, resulting in downstream disruptions for users.
#cqb5hcy0gx18
Disruption with repo creation - Resolved
Between January 24, 2026,19:56 UTC and January 25, 2026, 2:50 UTC repository creation and clone were degraded. On average, the error rate was 25% and peaked at 55% of requests for repository creation.
#g697qcy5dsks
Between January 24, 2026,19:56 UTC and January 25, 2026, 2:50 UTC repository creation and clone were degraded. On average, the error rate was 25% and peaked at 55% of requests for repository creation.
#g697qcy5dsks
January 27, 2026 at 1:48 AM
Disruption with repo creation - Resolved
Between January 24, 2026,19:56 UTC and January 25, 2026, 2:50 UTC repository creation and clone were degraded. On average, the error rate was 25% and peaked at 55% of requests for repository creation.
#g697qcy5dsks
Between January 24, 2026,19:56 UTC and January 25, 2026, 2:50 UTC repository creation and clone were degraded. On average, the error rate was 25% and peaked at 55% of requests for repository creation.
#g697qcy5dsks
Regression in windows runners for public repositories - 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.
#90hj03y5tj3c
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.
#90hj03y5tj3c
January 26, 2026 at 11:54 PM
Regression in windows runners for public repositories - 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.
#90hj03y5tj3c
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.
#90hj03y5tj3c
Regression in windows runners for public repositories - Update
At 23:45 UTC we applied a mitigation to take remaining impacted capacity offline and are seeing improvement. We will update again once we've confirmed the issue is resolved.
#90hj03y5tj3c
At 23:45 UTC we applied a mitigation to take remaining impacted capacity offline and are seeing improvement. We will update again once we've confirmed the issue is resolved.
#90hj03y5tj3c
January 26, 2026 at 11:51 PM
Regression in windows runners for public repositories - Update
At 23:45 UTC we applied a mitigation to take remaining impacted capacity offline and are seeing improvement. We will update again once we've confirmed the issue is resolved.
#90hj03y5tj3c
At 23:45 UTC we applied a mitigation to take remaining impacted capacity offline and are seeing improvement. We will update again once we've confirmed the issue is resolved.
#90hj03y5tj3c
Regression in windows runners for public repositories - Update
Our investigation into GitHub Actions 4 Core Windows runner failures in public repositories is ongoing.
#90hj03y5tj3c
Our investigation into GitHub Actions 4 Core Windows runner failures in public repositories is ongoing.
#90hj03y5tj3c
January 26, 2026 at 11:06 PM
Regression in windows runners for public repositories - Update
Our investigation into GitHub Actions 4 Core Windows runner failures in public repositories is ongoing.
#90hj03y5tj3c
Our investigation into GitHub Actions 4 Core Windows runner failures in public repositories is ongoing.
#90hj03y5tj3c
Regression in windows runners for public repositories - Update
We're continuing to investigate failures in GitHub Actions 4 Core Windows runners in public repositories.
#90hj03y5tj3c
We're continuing to investigate failures in GitHub Actions 4 Core Windows runners in public repositories.
#90hj03y5tj3c
January 26, 2026 at 10:03 PM
Regression in windows runners for public repositories - Update
We're continuing to investigate failures in GitHub Actions 4 Core Windows runners in public repositories.
#90hj03y5tj3c
We're continuing to investigate failures in GitHub Actions 4 Core Windows runners in public repositories.
#90hj03y5tj3c
Regression in windows runners for public repositories - Update
Rollback has been completed, but we are still seeing failures on about 11% of GitHub Actions runs on 4 Core Windows runners in public repositories.
#90hj03y5tj3c
Rollback has been completed, but we are still seeing failures on about 11% of GitHub Actions runs on 4 Core Windows runners in public repositories.
#90hj03y5tj3c
January 26, 2026 at 9:21 PM
Regression in windows runners for public repositories - Update
Rollback has been completed, but we are still seeing failures on about 11% of GitHub Actions runs on 4 Core Windows runners in public repositories.
#90hj03y5tj3c
Rollback has been completed, but we are still seeing failures on about 11% of GitHub Actions runs on 4 Core Windows runners in public repositories.
#90hj03y5tj3c
Regression in windows runners for public repositories - Update
Mitigation for failing GitHub Actions jobs on 4-Core Windows runners is still being mitigated. You should start to see more runs succeeding.
#90hj03y5tj3c
Mitigation for failing GitHub Actions jobs on 4-Core Windows runners is still being mitigated. You should start to see more runs succeeding.
#90hj03y5tj3c
January 26, 2026 at 8:12 PM
Regression in windows runners for public repositories - Update
Mitigation for failing GitHub Actions jobs on 4-Core Windows runners is still being mitigated. You should start to see more runs succeeding.
#90hj03y5tj3c
Mitigation for failing GitHub Actions jobs on 4-Core Windows runners is still being mitigated. You should start to see more runs succeeding.
#90hj03y5tj3c
Regression in windows runners for public repositories - Update
We've applied a mitigation to unblock running Actions. A regression occurred for Windows runners in public repositories which caused Actions workflows to fail. A mitigation is in place and customers s
#90hj03y5tj3c
We've applied a mitigation to unblock running Actions. A regression occurred for Windows runners in public repositories which caused Actions workflows to fail. A mitigation is in place and customers s
#90hj03y5tj3c
January 26, 2026 at 7:33 PM
Regression in windows runners for public repositories - Update
We've applied a mitigation to unblock running Actions. A regression occurred for Windows runners in public repositories which caused Actions workflows to fail. A mitigation is in place and customers s
#90hj03y5tj3c
We've applied a mitigation to unblock running Actions. A regression occurred for Windows runners in public repositories which caused Actions workflows to fail. A mitigation is in place and customers s
#90hj03y5tj3c
Regression in windows runners for public repositories - Investigating
We are investigating reports of impacted performance for some GitHub services.
#90hj03y5tj3c
We are investigating reports of impacted performance for some GitHub services.
#90hj03y5tj3c
January 26, 2026 at 7:27 PM
Regression in windows runners for public repositories - Investigating
We are investigating reports of impacted performance for some GitHub services.
#90hj03y5tj3c
We are investigating reports of impacted performance for some GitHub services.
#90hj03y5tj3c
Disruption with repo creation - 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.
#g697qcy5dsks
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.
#g697qcy5dsks
January 25, 2026 at 3:09 AM
Disruption with repo creation - 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.
#g697qcy5dsks
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.
#g697qcy5dsks
Disruption with repo creation - Update
The issue has been resolved. We will continue to monitor to ensure stability.
#g697qcy5dsks
The issue has been resolved. We will continue to monitor to ensure stability.
#g697qcy5dsks
January 25, 2026 at 3:09 AM
Disruption with repo creation - Update
The issue has been resolved. We will continue to monitor to ensure stability.
#g697qcy5dsks
The issue has been resolved. We will continue to monitor to ensure stability.
#g697qcy5dsks
Disruption with repo creation - Update
Repo creation failure rate increased above 50%. We have mitigated the problem and are monitoring for recovery.
#g697qcy5dsks
Repo creation failure rate increased above 50%. We have mitigated the problem and are monitoring for recovery.
#g697qcy5dsks
January 25, 2026 at 3:00 AM
Disruption with repo creation - Update
Repo creation failure rate increased above 50%. We have mitigated the problem and are monitoring for recovery.
#g697qcy5dsks
Repo creation failure rate increased above 50%. We have mitigated the problem and are monitoring for recovery.
#g697qcy5dsks
Disruption with repo creation - Investigating
We are investigating reports of impacted performance for some GitHub services.
#g697qcy5dsks
We are investigating reports of impacted performance for some GitHub services.
#g697qcy5dsks
January 25, 2026 at 2:45 AM
Disruption with repo creation - Investigating
We are investigating reports of impacted performance for some GitHub services.
#g697qcy5dsks
We are investigating reports of impacted performance for some GitHub services.
#g697qcy5dsks
Policy pages for Copilot are timing out - Resolved
On January 21, between 17:50 and 20:53 UTC, around 350 enterprises and organizations experienced slower load times or timeouts when viewing Copilot policy pages. The issue was traced to performance de
#6d5kv6l8d8q3
On January 21, between 17:50 and 20:53 UTC, around 350 enterprises and organizations experienced slower load times or timeouts when viewing Copilot policy pages. The issue was traced to performance de
#6d5kv6l8d8q3
January 24, 2026 at 12:33 AM
Policy pages for Copilot are timing out - Resolved
On January 21, between 17:50 and 20:53 UTC, around 350 enterprises and organizations experienced slower load times or timeouts when viewing Copilot policy pages. The issue was traced to performance de
#6d5kv6l8d8q3
On January 21, between 17:50 and 20:53 UTC, around 350 enterprises and organizations experienced slower load times or timeouts when viewing Copilot policy pages. The issue was traced to performance de
#6d5kv6l8d8q3
Disruption with some GitHub services - 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.
#cqb5hcy0gx18
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.
#cqb5hcy0gx18
January 22, 2026 at 3:24 PM
Disruption with some GitHub services - 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.
#cqb5hcy0gx18
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.
#cqb5hcy0gx18
Disruption with some GitHub services - Update
We have identified an issue in one of our services and have mitigated it. Services have recovered and we have a mitigation but we are working on a longer term solution.
#cqb5hcy0gx18
We have identified an issue in one of our services and have mitigated it. Services have recovered and we have a mitigation but we are working on a longer term solution.
#cqb5hcy0gx18
January 22, 2026 at 3:24 PM
Disruption with some GitHub services - Update
We have identified an issue in one of our services and have mitigated it. Services have recovered and we have a mitigation but we are working on a longer term solution.
#cqb5hcy0gx18
We have identified an issue in one of our services and have mitigated it. Services have recovered and we have a mitigation but we are working on a longer term solution.
#cqb5hcy0gx18
January 22, 2026 at 2:30 PM
Disruption with some GitHub services - Update
Issues is experiencing degraded performance. We are continuing to investigate.
#cqb5hcy0gx18
Issues is experiencing degraded performance. We are continuing to investigate.
#cqb5hcy0gx18
January 22, 2026 at 2:24 PM
Disruption with some GitHub services - Update
Issues is experiencing degraded performance. We are continuing to investigate.
#cqb5hcy0gx18
Issues is experiencing degraded performance. We are continuing to investigate.
#cqb5hcy0gx18
Disruption with some GitHub services - Investigating
We are investigating reports of impacted performance for some GitHub services.
#cqb5hcy0gx18
We are investigating reports of impacted performance for some GitHub services.
#cqb5hcy0gx18
January 22, 2026 at 2:15 PM
Disruption with some GitHub services - Investigating
We are investigating reports of impacted performance for some GitHub services.
#cqb5hcy0gx18
We are investigating reports of impacted performance for some GitHub services.
#cqb5hcy0gx18
Policy pages for Copilot are timing out - 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.
#6d5kv6l8d8q3
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.
#6d5kv6l8d8q3
January 21, 2026 at 8:54 PM
Policy pages for Copilot are timing out - 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.
#6d5kv6l8d8q3
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.
#6d5kv6l8d8q3
Policy pages for Copilot are timing out - Update
We are rolling out a fix to reduce latency and timeouts on policy pages and are continuing to monitor impact.
#6d5kv6l8d8q3
We are rolling out a fix to reduce latency and timeouts on policy pages and are continuing to monitor impact.
#6d5kv6l8d8q3
January 21, 2026 at 8:48 PM
Policy pages for Copilot are timing out - Update
We are rolling out a fix to reduce latency and timeouts on policy pages and are continuing to monitor impact.
#6d5kv6l8d8q3
We are rolling out a fix to reduce latency and timeouts on policy pages and are continuing to monitor impact.
#6d5kv6l8d8q3
Policy pages for Copilot are timing out - Update
We are continuing to investigate latency and timeout issues affecting Copilot policy pages.
#6d5kv6l8d8q3
We are continuing to investigate latency and timeout issues affecting Copilot policy pages.
#6d5kv6l8d8q3
January 21, 2026 at 8:15 PM
Policy pages for Copilot are timing out - Update
We are continuing to investigate latency and timeout issues affecting Copilot policy pages.
#6d5kv6l8d8q3
We are continuing to investigate latency and timeout issues affecting Copilot policy pages.
#6d5kv6l8d8q3
Policy pages for Copilot are timing out - Update
We are investigating timeouts for customers visiting the Copilot policy pages for organizations and enterprises.
#6d5kv6l8d8q3
We are investigating timeouts for customers visiting the Copilot policy pages for organizations and enterprises.
#6d5kv6l8d8q3
January 21, 2026 at 7:39 PM
Policy pages for Copilot are timing out - Update
We are investigating timeouts for customers visiting the Copilot policy pages for organizations and enterprises.
#6d5kv6l8d8q3
We are investigating timeouts for customers visiting the Copilot policy pages for organizations and enterprises.
#6d5kv6l8d8q3
Policy pages for Copilot are timing out - Investigating
We are investigating reports of impacted performance for some GitHub services.
#6d5kv6l8d8q3
We are investigating reports of impacted performance for some GitHub services.
#6d5kv6l8d8q3
January 21, 2026 at 7:33 PM
Policy pages for Copilot are timing out - Investigating
We are investigating reports of impacted performance for some GitHub services.
#6d5kv6l8d8q3
We are investigating reports of impacted performance for some GitHub services.
#6d5kv6l8d8q3