Depot - Notice history

GitHub have marked the incident as resolved.

We are observing all jobs able to successfully start. GitHub is still reporting that status updates are delayed for all Actions customers. https://www.githubstatus.com/incidents/nj47vccwm2zj

While GitHub are still investigating the incident, we are seeing some jobs able to complete, though their status is often not reflected correctly in the GitHub UI. https://www.githubstatus.com/incidents/nj47vccwm2zj

GitHub have identified the cause as network connectivity issues on their end, they are continuing to investigate: https://www.githubstatus.com/incidents/nj47vccwm2zj

GitHub have just opened an incident of their own for this outage: https://www.githubstatus.com/incidents/nj47vccwm2zj

This appears to be a GitHub Actions outage - both GitHub-hosted runners and Depot-hosted runners are currently experiencing issues starting jobs.

GitHub has opened an outage of its own that we are now monitoring https://www.githubstatus.com/incidents/2bglpcjvg7xb

We have identified the issue as being on GitHub's end. They are either not releasing jobs in a timely manner to online runners or not sending webhook events when jobs are in progress. We will continue to monitor queue times on our side.

GitHub has cleared their outage, but we are monitoring webhook delivery times from their side.

We are still monitoring webhook flakiness due to the ongoing GitHub outage: https://www.githubstatus.com/incidents/7txcg0j03kkg. This is surfacing as longer than normal queue times while we wait for GitHub to pass the job to an online runner.

We are monitoring the rollback GitHub has performed and are observing jobs being processed: https://www.githubstatus.com/