Is GitHub Actions down? Check the current status
GitHub Actions is operational
Updated
GitHub Actions is operational
Updated
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
IsDown pulls data from GitHub's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.
This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.
Peter
4 days agoGithub action stuck queued for runner for 20 minutes
Jamie
22 days agoGitActions syn/push is stalling / looking for runner
Alejandro
about 1 month agoself-hosted runner not taking jobs even when restarted
Mohamad
about 1 month agoThe Workflow keeps running and unable to be cancelled
Isak
about 1 month agoBlank screen, does not start, says started 4m ago but I cannot see anything?
Joshua
2 months agoLarge runners not being assigned
Ivan
3 months agoJobs are not getting picked up on GitHub hosted runners
Amber
4 months agoAll actions are stuck in queue. "Waiting for a runner to pick up this job..."
Seb
4 months agoNot getting an action runner assigned
Can
5 months agoQueued forever. Facing in last 3 days. Sometimes it runs first jobs but after that queues the others.. Stuck.
DimaO
5 months agoGithub actions are now getting bigger runners and getting queued forever
GitHubUser3
5 months agoJobs triggered are not reflecting on GitHub Actions page.
J
5 months agoCan't find runner or stop action.
Dom
6 months agocheckout inconsistently takes 10minutes+ to complete rather than the usual few seconds
Roger
6 months agoGithub actions stuck on queue
siddharth
6 months agoAll my workflows are getting queued.....
Akhil
6 months agoGithub actions are in pending state
Mukul
6 months agoAction is queued for very long
Will
6 months agoGithub action are stuck queueing
Regan
6 months agoGithub actions stuck in initialization state
E
6 months agoGithub actions seems to be stuck, all jobs are either queued or cannot be cancelled
steven
6 months agogithub action jobs are pending
Gary
6 months agoTakes over 30 minutes to execute
geoffrey
6 months agoall workflow actions pending and cannot be cancelled
Mr.V
6 months agoAll workflows across repos are frozen with "Queued" jobs
Anon
6 months agoShows action queued; frozen
RK
6 months agoActions are queued waiting for hosted, selfhosted runners
Max
6 months agoActions stuck in queue mode
Joshua
6 months ago> Waiting for a runner to pick up this job... Job is waiting for a hosted runner to come online. And nothing happens
grif
6 months agoactions endlessly queuing
raj
6 months agogithub runners are queued
Ry
6 months agoJobs is endlessly queued with the message Waiting for a runner to pick up this job...
Kathirvelu
6 months agoAfter pushing the code. The github action shows in queed status for long time. And even it seems to be slower than usual.
B
8 months agoJSON parsing is randomly failing
VJ
8 months agodocker-compose: command not found Error: Process completed with exit code 127.
kevin
9 months agoactions failing due to unknown errors
Ostone
11 months agoGithub actions are never ending and their display is not split by step.
AtoLrn
11 months agoGithub Actions not showing properly and never ending
Dmytro
11 months agoSimply queued all jobs and stop deploying
Austin
about 1 year agoBuild job stuck in queue. Attempts to cancel and then subsequently re-rerun the build resulted in numerous request timeouts ("Unicorn!" page).
Sajag
about 1 year agoGithub action stuck in queue
Alaa
about 1 year agoGithub actions doesn't trigger
Hassan
over 1 year agoAutomatic Triggering of GitHub Actions is not working when I push my changes
Anonymous
over 1 year agoSelf-hosted runners not picking up jobs
Vic
over 1 year agoNot triggering on push to main
Rodrigo
over 1 year agodoesnt trigger new builds
IsDown has tracked 140 incidents for GitHub Actions since started monitoring GitHub status in April 2020.
29 days ago · lasted about 3 hours
We are investigating reports of degraded performance for Actions More details
about 1 month ago · lasted about 1 hour
We are investigating reports of degraded performance for Actions More details
about 1 month ago · lasted 39 minutes
We are investigating reports of degraded performance for Actions More details
We've tracked and collected 140 incidents for GitHub Actions since started monitoring GitHub status
Actions is part of GitHub. Check the GitHub's status.
14 incidents in 2025
Number of Incidents
1 issues
Last incident
29 days ago
AWS
Google Cloud
Google Workspace
Azure
Cloudflare
Slack
Zoom
Datadog US1
Figma
Adobe
HubSpot
Microsoft 365
Aircall
Stripe
Airtable
Why teams choose IsDown:
14-day free trial • No credit card required
Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.
GitHub Actions integrates with the GitHub API to automate repository tasks, trigger workflow runs, and manage job execution. Developers can use the REST API and GraphQL API to query job statuses, retrieve logs, and debug workflows efficiently.
Required status checks ensure that workflows meet predefined conditions before allowing a merge. If a check fails, GitHub prevents the PR from merging until the issue is resolved. These checks enhance code quality, repository security, and workflow reliability.
When a pull request (PR) is created, GitHub Actions can automatically validate code changes. This includes running tests, checking repository configurations, and enforcing branch protections like required status checks and automatic approvals before merging.
Common failures in GitHub Actions may be due to misconfigurations, missing dependencies, API rate limits, or permission restrictions. Checking workflow runs, adjusting configuration settings, and reviewing log outputs in the Actions tab can help diagnose and fix problems.
The dashboard provides a central view of running workflows, failed jobs, and execution logs. Developers can track workflow progress, restart failed jobs, and analyze logs for debugging to improve automation and reliability.
GitHub Actions automates deployment by integrating with cloud providers, running custom scripts, and validating commit histories. Using webhooks and environment protection rules, workflows can be triggered automatically upon code changes, ensuring seamless rollouts.
Currently there's no report of GitHub Actions being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the GitHub Actions official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
GitHub Actions last outage was on March 21, 2025 with the title "Intermittent GitHub Actions workflow failures"
IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
IsDown offers an easy way to monitor GitHub with maximum flexibility
IsDown monitors Actions for major outages. A major outage is when Actions experiences a critical issue that severely affects one or more services/regions. When GitHub marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors GitHub status page for minor outages. A minor outage is when Actions experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in GitHub status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
GitHub publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.
IsDown monitors GitHub and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
GitHub and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
14-day free trial · No credit card required · No code required
