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

No incidents reported today.

May 8, 2024

No incidents reported.

May 7, 2024
Incident with Issues, API Requests and Pull Requests
Resolved - Starting on May 7th, 2024 at 14:00 UTC, our elasticsearch cluster that powers Issues and Pull Requests became unresponsive correlating to a spike in usage. This affected GitHub customers who were trying to search issues and pull requests.

We mitigated this incident by adding additional cluster members which increased the resources available to the cluster. We are working to add additional safeguards to our endpoints. We are also continuing to investigate the root cause of the instability and if the index needs to be re-sharded for future risk mitigation.
May 7, 15:55 UTC
Update - We are seeing recovery, and are continuing to monitor issues and pull requests search results.
May 7, 15:25 UTC
Update - We’re investigating problems with our Issues and Pull Requests search cluster that are impacting result list pages and endpoints.
May 7, 15:00 UTC
Update - We're investigating page load problems with issues and pull requests.
May 7, 14:24 UTC
Investigating - We are investigating reports of degraded performance for Issues, API Requests and Pull Requests
May 7, 14:23 UTC
May 6, 2024

No incidents reported.

May 5, 2024

No incidents reported.

May 4, 2024

No incidents reported.

May 3, 2024
We are investigating reports of degraded performance.
Resolved - Starting on May 2, 2024 at 8:00 UTC through May 3 2:45 UTC the GitHub Enterprise Server (GHES) Azure Marketplace offering was degraded and customers were not able to create GHES VMs using our provided GHES images. This affected all GitHub customers that were attempting to deploy VMs in Azure using either the API or the Azure Portal. This was due to an incorrect configuration of our Azure Marketplace offering causing the images to be no longer visible to Azure users.

We mitigated the incident by working with our partners in Azure to restore access to the affected images.

We are working with our partners in Azure to add additional safeguards to ensure our images remain available to customers at all times. In addition, we continue to work with on restoring access to some older patch versions of GHES that remain unavailable at this time.
May 3, 02:45 UTC
Update - Azure Marketplace links have been restored and we are validating the images
May 3, 02:37 UTC
Update - Work is in progress to restore Azure Marketplace.
May 3, 01:44 UTC
Update - GHES Images on Azure are now restored and are available via the Azure CLI. Azure Marketplace listing is still not yet available. We will provide updates on the progress of the Azure Marketplace restoration.
May 3, 01:05 UTC
Update - Work is in progress to restore images. ETA is within 30 minutes.
May 3, 00:32 UTC
Update - Work is in progress to restore images, however there is no ETA yet for when restore will be complete
May 2, 23:58 UTC
Update - Work is in progress to restore images, however there is no ETA yet for when restore will be complete
May 2, 23:17 UTC
Update - Work in progress to restore images
May 2, 22:43 UTC
Update - We have identified the issue and are working to restore GHES VHD images.
May 2, 22:09 UTC
Update - We are actively engaged and working to mitigate the issue.
May 2, 20:26 UTC
Update - We have identified the root cause and are working to mitigate the issue.
May 2, 19:48 UTC
Update - Currently customers who use Azure Marketplace are unable to access GHES VHD images. This prevents customers who use Azure from spinning up new GHES instances (running instances are unaffected and are still able to hotpatch to new versions as well)
May 2, 19:07 UTC
Investigating - We are currently investigating this issue.
May 2, 19:07 UTC
May 2, 2024
May 1, 2024

No incidents reported.

Apr 30, 2024

No incidents reported.

Apr 29, 2024

No incidents reported.

Apr 28, 2024

No incidents reported.

Apr 27, 2024

No incidents reported.

Apr 26, 2024
We are investigating reports of degraded performance.
Resolved - On April 26th, 2024, we received several internal reports of GitHub staff being unable to login using their Passkeys. Out of an abundance of caution, we updated our public status to yellow. Further investigation discovered that a background job intended to clean up stale authenticated device records was mistakenly removing associated passkeys. As a result, some passkey registrations were incorrectly removed from some user accounts.
The impact from the bug in the background job was limited to a small number of passkey users (<0.5%). We have since resolved the bug in question and are working to notify all affected users.
Apr 26, 16:49 UTC
Update - The issue appears to be limited in scope to a few internal users, without any reports of issues from outside GitHub. We are adding additional logging to our WebAuthn flow to detect this in the future. If you cannot use your mobile passkey to sign in, please contact support or reach out to us in https://github.com/orgs/community/discussions/67791
Apr 26, 16:49 UTC
Update - Sign in to GitHub.com using a passkey from a mobile device is currently failing. Users may see an error message saying that passkey sign in failed, or may not see any passkeys available after signing in with their password.
This issue impacts both GitHub.com on mobile devices as well as cross-device authentication where the phone's passkey is used to authenticate on a desktop browser.
To workaround this issue, use your password and the 2FA method you setup prior to setting up your passkey, either TOTP or SMS.
Apr 26, 15:10 UTC
Investigating - We are currently investigating this issue.
Apr 26, 15:10 UTC
Apr 25, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage