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 14, 2024
We are investigating reports of degraded performance.
Resolved - This incident has been resolved.
May 14, 21:04 UTC
Update - We are seeing recovery for queue times on Actions Larger Runners and are continuing to monitor full recovery.
May 14, 20:47 UTC
Update - We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
May 14, 20:09 UTC
Update - We are continuing to investigate long queue times for Actions Larger Runners
May 14, 19:16 UTC
Update - We are investigating long queue times for Actions Larger Runners
May 14, 18:40 UTC
Investigating - We are currently investigating this issue.
May 14, 18:37 UTC
May 13, 2024
Incident with Actions
Resolved - On May 13, 2024, between 19:03 UTC and 19:57 UTC, some customers experienced delays in receiving status updates for in-progress GitHub Actions workflow runs. The root cause was identified to be a bug in the logic for checking the state of a configuration which would only manifest under very specific conditions and cause exceptions. These exceptions impacted the backend process for handling workflow run status updates and caused jobs with any annotations to not get updated properly. Jobs without any annotations were not affected. The affected jobs during the incident will get marked as failed after 24 hours, and affected customers will need to manually retry the jobs they want to execute.

We resolved the incident by reverting the problematic change. We are enhancing our process for deploying changes and reassessing our monitoring of relevant subsystems to prevent similar issues in the future.
May 13, 20:10 UTC
Update - We are seeing signs of recovery for actions jobs
May 13, 20:10 UTC
Investigating - We are investigating reports of degraded performance for Actions
May 13, 19:51 UTC
Incident with Copilot
Resolved - This incident has been resolved.
May 13, 15:44 UTC
Update - We are applying configuration changes to mitigate impact to Copilot Chat users.
May 13, 14:56 UTC
Update - We continue to investigate the root cause of elevated errors in Copilot Chat.
May 13, 14:13 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
May 13, 13:27 UTC
Update - We are investigating an increase in exceptions impacting Copilot Chat usage from IDEs.
May 13, 13:24 UTC
Investigating - We are currently investigating this issue.
May 13, 13:23 UTC
May 12, 2024

No incidents reported.

May 11, 2024

No incidents reported.

May 10, 2024

No incidents reported.

May 9, 2024

No incidents reported.

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.

← Incident History Powered by Atlassian Statuspage