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 9, 2024

No incidents reported today.

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.

Jan 29, 2024

No incidents reported.

Jan 28, 2024
We are investigating reports of degraded performance.
Resolved - On January 28, 2024, between 01:00 UTC and 14:00 UTC the Avatars service was degraded and could not return all avatar images requested by users, instead it would return a default, fallback avatar image. This incident impacted, at peak time 6% of the requests for viewing Avatars. Requests that were impacted did not prevent the users from continuing to use any GitHub services. This was due to an issue with the Avatars service connecting to a database host.

We mitigated the incident by restarting the malfunctioning hosts that were not able to return the user avatar images.

We are working to improve alerting and monitoring of our services to reduce our time to detection and mitigation.
Jan 28, 14:42 UTC
Update - We have mitigated all customer impact. We are no longer serving fallback avatar icons when loading web pages for some customers. We continue to monitor the results.
Jan 28, 14:27 UTC
Update - A fix has been implemented for customers seeing the default avatar (octocat) when loading web pages and we are monitoring the results.
Jan 28, 13:57 UTC
Update - Some requests for getting the Avatars are returning the fallback response instead of the asked avatar since they are having issues connecting to the Mysql host
Jan 28, 13:20 UTC
Investigating - We are currently investigating this issue.
Jan 28, 13:20 UTC
Jan 27, 2024

No incidents reported.

Jan 26, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage