GitHub Community
[2025-08-27] Incident Thread #171346
-
|
❗ An incident has been declared:Disruption with some GitHub services Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page. |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 2 replies
-
|
Yeah, copilot seams to be completely broken for me right now! Even the Copilot Settings page (https://github.com/settings/copilot/features) returns nothing but a 500 error. |
Beta Was this translation helpful? Give feedback.
-
|
GitHub Copilot is returning a 500 Internal Server Error 
|
Beta Was this translation helpful? Give feedback.
-
|
eu tava mexendo no meu code, previsão para retorno? |
Beta Was this translation helpful? Give feedback.
-
UpdateThe team is aware of the root cause of this issue and is working to mitigate the issue quickly. |
Beta Was this translation helpful? Give feedback.
-
|
Folks, it's end of the month and GitHub just ran out of Claude and GPT credits. We all know how that happens... They are reloading now. The CFO just needs to enter credit card number correctly. Have some patience! |
Beta Was this translation helpful? Give feedback.
-
|
😂 |
Beta Was this translation helpful? Give feedback.
-
|
Alrighty, Claude Code it is. |
Beta Was this translation helpful? Give feedback.
-
|
Phew, I thought that I may have reached my Pro limit > I just upgraded 2 days ago lol. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe've discovered the cause of the service disruption and applied a mitigation. |
Beta Was this translation helpful? Give feedback.
-
Incident ResolvedThis incident has been resolved. |
Beta Was this translation helpful? Give feedback.
-
Incident SummaryOn August 27, 2025 between 20:35 and 21:17 UTC, Copilot, Web and REST API traffic experienced degraded performance. Copilot saw an average of 36% of requests fail with a peak failure rate of 77%. Approximately 2% of all non-Copilot Web and REST API traffic requests failed. This incident occurred after a stale schema cache was used following a database migration. This led to a large number of failed queries. At 21:15 UTC, we applied a fix and by 21:17 UTC, all services had fully recovered. We have implemented a block for this failure mode as an immediate solution and are actively working to add safeguards to prevent similar issues from occurring in the future. |
Beta Was this translation helpful? Give feedback.
Incident Summary
On August 27, 2025 between 20:35 and 21:17 UTC, Copilot, Web and REST API traffic experienced degraded performance. Copilot saw an average of 36% of requests fail with a peak failure rate of 77%. Approximately 2% of all non-Copilot Web and REST API traffic requests failed.
This incident occurred after a stale schema cache was used following a database migration. This led to a large number of failed queries. At 21:15 UTC, we applied a fix and by 21:17 UTC, all services had fully recovered.
We have implemented a block for this failure mode as an immediate solution and are actively working to add safeguards to prevent similar issues from occurring in the future.