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

No incidents reported today.

Sep 11, 2024

No incidents reported.

Sep 10, 2024

No incidents reported.

Sep 9, 2024

No incidents reported.

Sep 8, 2024

No incidents reported.

Sep 7, 2024

No incidents reported.

Sep 6, 2024

No incidents reported.

Sep 5, 2024
Disruption with some GitHub services
Resolved - Between August 27, 2024, 15:52 UTC and September 5, 2024, 17:26 UTC the GitHub Connect service was degraded. This specifically impacted GHES customers who were enabling GitHub Connect for the first time on a GHES instance. Previously enabled GitHub Connect GHES instances were not impacted by this issue.

Customers experiencing this issue would have received a 404 response during GitHub Connect enablement and subsequent messages about a failure to connect. This was due to a recent change in configuration to GitHub Connect which has since been rolled back.

Subsequent enablement failures on re-attempts were caused by data corruption which has been remediated. Customers should now be able to enable GitHub Connect successfully.

To reduce our time to detection and mitigation of such issues in the future, we are working to improve observability of GitHub Connect failures. We are also making efforts to prevent future misconfiguration of GitHub Connect.
Sep 5, 17:24 UTC
Update - We continue to work on making GitHub Connect setup available for customers that experienced errors since Sept 2. We will share another update as we make progress.
Sep 5, 16:49 UTC
Update - We've reverted a related change and customers can now setup GitHub Connect again. However, customers who attempted to setup GitHub Connect after September 2nd that saw a 404 will see continued failures until we complete an additional repair step. We will provide additional updates as this work progresses.
Sep 5, 16:15 UTC
Update - Enterprise administrators are seeing failures in the form of 404s when attempting to setup GitHub Connect for the first time. Existing Connect setups are not impacted. We are working on a fix for this issue.
Sep 5, 15:56 UTC
Investigating - We are currently investigating this issue.
Sep 5, 15:55 UTC
Sep 4, 2024

No incidents reported.

Sep 3, 2024

No incidents reported.

Sep 2, 2024

No incidents reported.

Sep 1, 2024

No incidents reported.

Aug 31, 2024

No incidents reported.

Aug 30, 2024

No incidents reported.

Aug 29, 2024
Disruption with some GitHub services
Resolved - On August 29th, 2024, from 16:56 UTC to 21:42 UTC, we observed an elevated rate of traffic on our public edge, which triggered GitHub’s rate limiting protections. This resulted in <0.1% of users being identified as false-positives, which they experienced as intermittent connection timeouts. At 20:59 UTC the engineering team improved the system to remediate the false-positive identification of user traffic, and return to normal traffic operations.
Aug 29, 21:54 UTC
Update - The connectivity issues have been resolved and we are back to normal.
Aug 29, 21:54 UTC
Update - We have implemented a potential fix and are continuing to monitor for success.
Aug 29, 21:45 UTC
Update - We have isolated the symptom of the connectivity issues and are working to trace down the cause.
Aug 29, 21:25 UTC
Update - While we have seen a reduction in reports of users having connectivity issues to GitHub.com, we are still investigating the issue.
Aug 29, 20:43 UTC
Update - We are continuing to investigate issues with customers reporting temporary issues accessing GitHub.com
Aug 29, 20:07 UTC
Update - We are getting reports of users who aren't able to access GitHub.com and are investigating.
Aug 29, 19:29 UTC
Investigating - We are currently investigating this issue.
Aug 29, 19:29 UTC
← Incident History Powered by Atlassian Statuspage