[2025-07-28] Incident Thread #167894
Replies: 7 comments
-
UpdateSome GitHub services are experiencing degraded performance. Team is currently investigating to determine a cause and mitigation. |
Beta Was this translation helpful? Give feedback.
-
UpdateSome GitHub services continue to experience degraded performance. Team is looking into networking issues. We will continue to keep users updated on progress towards mitigation. |
Beta Was this translation helpful? Give feedback.
-
UpdateApproximately 4% of requests to impacted services continue to error. The team is continuing its work to mitigate this incident. |
Beta Was this translation helpful? Give feedback.
-
UpdateTeam is deploying a mitigation for this incident. We will update again once we have verified the fix. |
Beta Was this translation helpful? Give feedback.
-
UpdateMitigation has deployed. We are seeing recovery across all impacted services. |
Beta Was this translation helpful? Give feedback.
-
Incident ResolvedThis incident has been resolved. |
Beta Was this translation helpful? Give feedback.
-
Incident SummaryBetween July 28, 2025, 22:23:00 UTC and July 29, 2025 02:06:00 UTC, GitHub experienced degraded performance across multiple services including API, Issues, GraphQ and Pull Requests. During this time, approximately 4% of Web and API requests resulted in 500 errors. This incident was caused by DNS resolution failure while decommissioning infrastructure hosts. We resolved the incident by removing references to the stale hosts. We are working to improve our host replacement process by correcting our automatic host ejection behavior and by ensuring configuration is updated before hosts are decommissioned. This will prevent similar issues in the future. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
❗ An incident has been declared:
Incident with Issues, API Requests and Pull Requests
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.
All reactions