GitHub header
All Systems Operational
Git Operations ? Operational
API Requests ? Operational
Webhooks ? Operational
Visit www.githubstatus.com for more information 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
Feb 13, 2024

No incidents reported today.

Feb 12, 2024
Incident with Copilot
Resolved - This incident has been resolved.
Feb 12, 18:14 UTC
Update - Code completion response times have returned to normal.
Feb 12, 18:13 UTC
Update - We’re still continuing to investigate slower than expected code completions for a subset of users in Europe. Next update to be provided in 30 minutes.
Feb 12, 17:30 UTC
Update - We’re continuing to investigate slower than expected code completions for a subset of users in Europe. Next update to be provided in 30 minutes.
Feb 12, 17:01 UTC
Update - We're continuing to investigate slower than expected code completions for a subset of users in Europe. Next update to be provided in 30 minutes.
Feb 12, 16:26 UTC
Update - Code completions are now working for the impacted users, but completing more slowly than expected. Investigation continues to completely mitigate the issue and restore Copilot code completion functionality to normal.
Feb 12, 15:51 UTC
Update - Following mitigation steps taken, we have reduced the impact to a more narrow subset of users. Investigation continues to completely mitigate the issue and restore Copilot code completion functionality.
Feb 12, 15:16 UTC
Update - We are continuing to investigate the issues with Copilot code completion currently impacting some users in Europe. We will provide further details as we have them.
Feb 12, 14:36 UTC
Update - We have confirmed that this is a reoccurrence of the earlier issue. Impact is currently limited to some European users. The team is working through alternative mitigation strategies to resolve the issue and return normal service.
Feb 12, 14:04 UTC
Update - We are investigating reports that the earlier problem with Copilot code completions is reoccurring.
Feb 12, 13:28 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 12, 13:28 UTC
Incident with Copilot
Resolved - This incident has been resolved.
Feb 12, 12:39 UTC
Update - We are starting to see recovery based on the signals that the team have been monitoring, following mitigation steps being taken. When confident that recovery is complete, we will resolve this incident.
Feb 12, 12:29 UTC
Update - We are continuing to investigate increased failure rates for Copilot code completion for some users in Europe.
Feb 12, 12:00 UTC
Update - We are investigating reports that GitHub Copilot code completions are not working for some users in Europe.
Feb 12, 11:38 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 12, 11:38 UTC
Feb 11, 2024

No incidents reported.

Feb 10, 2024

No incidents reported.

Feb 9, 2024
Incident with Webhooks
Resolved - This incident has been resolved.
Feb 9, 11:28 UTC
Update - Webhooks is operating normally.
Feb 9, 11:25 UTC
Update - We are investigating latency in processing webhooks. Customers may see a delay of around 5 minutes at this time. We will continue to keep users updated on progress towards mitigation.
Feb 9, 11:11 UTC
Investigating - We are investigating reports of degraded performance for Webhooks
Feb 9, 11:09 UTC
Feb 8, 2024

No incidents reported.

Feb 7, 2024

No incidents reported.

Feb 6, 2024

No incidents reported.

Feb 5, 2024
Incident with Git Operations
Resolved - On 2024-02-05, from 09:26 to 13:20 UTC some GitHub customers experienced errors when trying to download raw files. An overloaded server exposed a bug, causing us to return HTTP 500 error codes.

The issue was mitigated by disabling the server and re-routing traffic. We are implementing improvements to our routing logic to more quickly avoid troublesome hosts in the future.

Feb 5, 09:53 UTC
Investigating - We are investigating reports of degraded performance for Git Operations
Feb 5, 09:40 UTC
Feb 4, 2024

No incidents reported.

Feb 3, 2024

No incidents reported.

Feb 2, 2024

No incidents reported.

Feb 1, 2024
We are investigating reports of degraded performance.
Resolved - An update to our design system caused issues loading dynamic content in the global side navigation menu and in other page-specific sidebar navigation elements. Impacted users saw continuous loading spinners in place of dynamic menu content. User impact lasted from 0:55 UTC to 4:41 UTC on February 1st.

We are working on a number of improvements in response to this incident. We are adding request volume monitors to sidebar navigation endpoints and making changes to our front end escalation paths to improve our time to detect and time to recovery for incidents of this nature. We have also begun work to improve both automated and manual testing for these types of changes in order to prevent recurrence.
Feb 1, 04:41 UTC
Update - This issue has been resolved. A reload of your browser window/tab may be required if you continue to experience issues with the collapsable navigation sidebars not loading.
Feb 1, 04:41 UTC
Update - We are in the process of deploying a remediation, and expect to see restoration of impacted functionality within the next hour.
Feb 1, 04:21 UTC
Update - We have identified an issue that is preventing some navigation components from loading while browsing GitHub.com, and are testing a remediation prior to deployment.
Feb 1, 03:55 UTC
Update - We are currently investigating reports of some components of the GitHub.com website not loading for some users.
Feb 1, 03:14 UTC
Investigating - We are currently investigating this issue.
Feb 1, 03:13 UTC
Jan 31, 2024
We are investigating reports of degraded performance.
Resolved - This incident was the result of an infrastructure change that was made to our load balancers to prepare us for IPv6 enablement of GitHub.com. This change was deployed to a subset of our global edge sites.

The change had the unintended consequence of causing IPv4 addresses to start being passed as an IPv4-mapped IPv6-compatible address to our IP Allow List functionality.

For example 10.1.2.3 became ::ffff:10.1.2.3. While our IP Allow List functionality was developed with IPv6 in mind, it wasn't developed to handle these mapped addresses, and hence started blocking requests as it deemed these to be not in the defined list of allowed addresses. Request error rates peaked at 0.23% of all requests.

We have so far identified three remediation items here:

- Update the IP Allow List functionality to handle IPv4-mapped addresses.
- Audit the rest of our stack to confirm there are no further places this IPv4-mapped IPv6 addresses flaw exists.
- Improve our testing and monitoring processes to better catch these issues in the future.
Jan 31, 14:57 UTC
Update - We have resolved the issue and confirmed all regions are now operating as expected.
Jan 31, 14:56 UTC
Update - The fix for ip allow lists is currently rolling out; and we are awaiting confirmation from specific geographic regions.
Jan 31, 14:49 UTC
Update - We are rolling out a fix to resolve the issues with IP allow lists. This should be resolved shortly.
Jan 31, 14:33 UTC
Update - Some customers are experiencing issues with IP allow lists.
Jan 31, 14:14 UTC
Investigating - We are currently investigating this issue.
Jan 31, 14:14 UTC
Jan 30, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage