Is GitHub Actions Down?

This page shows the live GitHub Actions status so you can confirm in seconds if GitHub Actions is down.

GitHub Actions current status

Updated

GitHub Actions is operational

IsDown pulls data from the official status page every few minutes and collects user-reported GitHub Actions issues.
Refresh the page to see the latest updates.

GitHub Actions user-reported issues in the last 24 hours

This chart displays the number of user-reported GitHub Actions problems 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.

IsDown Logo Third-party monitoring

All Your Service Status Pages in One Dashboard

Monitoring 4000+ third-party services in real-time
Get custom alerts via Slack, Teams, Datadog, etc.
Create public or private status pages
Start Free Trial
14-day free trial · No credit card required
Trusted by thousands of teams

GitHub Actions outage history

IsDown has tracked 142 incidents for GitHub Actions since started monitoring GitHub downtimes in April 2020. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

Sign up and check all outage history

Latest user comments about GitHub Actions issues

  • P

    Peter

    Github action stuck queued for runner for 20 minutes

  • J

    Jamie

    GitActions syn/push is stalling / looking for runner

  • A

    Alejandro

    self-hosted runner not taking jobs even when restarted

  • M

    Mohamad

    The Workflow keeps running and unable to be cancelled

  • I

    Isak

    Blank screen, does not start, says started 4m ago but I cannot see anything?

  • J

    Joshua

    Large runners not being assigned

  • I

    Ivan

    Jobs are not getting picked up on GitHub hosted runners

  • A

    Amber

    All actions are stuck in queue. "Waiting for a runner to pick up this job..."

  • S

    Seb

    Not getting an action runner assigned

  • C

    Can

    Queued forever. Facing in last 3 days. Sometimes it runs first jobs but after that queues the others.. Stuck.

  • D

    DimaO

    Github actions are now getting bigger runners and getting queued forever

  • G

    GitHubUser3

    Jobs triggered are not reflecting on GitHub Actions page.

  • J

    J

    Can't find runner or stop action.

  • D

    Dom

    checkout inconsistently takes 10minutes+ to complete rather than the usual few seconds

  • R

    Roger

    Github actions stuck on queue

  • S

    siddharth

    All my workflows are getting queued.....

  • A

    Akhil

    Github actions are in pending state

  • M

    Mukul

    Action is queued for very long

  • W

    Will

    Github action are stuck queueing

  • R

    Regan

    Github actions stuck in initialization state

  • E

    E

    Github actions seems to be stuck, all jobs are either queued or cannot be cancelled

  • S

    steven

    github action jobs are pending

  • G

    Gary

    Takes over 30 minutes to execute

  • G

    geoffrey

    all workflow actions pending and cannot be cancelled

  • M

    Mr.V

    All workflows across repos are frozen with "Queued" jobs

  • A

    Anon

    Shows action queued; frozen

  • R

    RK

    Actions are queued waiting for hosted, selfhosted runners

  • M

    Max

    Actions stuck in queue mode

  • J

    Joshua

    > Waiting for a runner to pick up this job... Job is waiting for a hosted runner to come online. And nothing happens

  • G

    grif

    actions endlessly queuing

  • R

    raj

    github runners are queued

  • R

    Ry

    Jobs is endlessly queued with the message Waiting for a runner to pick up this job...

  • K

    Kathirvelu

    After pushing the code. The github action shows in queed status for long time. And even it seems to be slower than usual.

  • B

    B

    JSON parsing is randomly failing

  • V

    VJ

    docker-compose: command not found Error: Process completed with exit code 127.

  • K

    kevin

    actions failing due to unknown errors

  • O

    Ostone

    Github actions are never ending and their display is not split by step.

  • A

    AtoLrn

    Github Actions not showing properly and never ending

  • D

    Dmytro

    Simply queued all jobs and stop deploying

  • A

    Austin

    Build job stuck in queue. Attempts to cancel and then subsequently re-rerun the build resulted in numerous request timeouts ("Unicorn!" page).

  • S

    Sajag

    Github action stuck in queue

  • A

    Alaa

    Github actions doesn't trigger

  • H

    Hassan

    Automatic Triggering of GitHub Actions is not working when I push my changes

  • A

    Anonymous

    Self-hosted runners not picking up jobs

  • V

    Vic

    Not triggering on push to main

  • R

    Rodrigo

    doesnt trigger new builds

GitHub Actions outages in the last 30 days

Number of Incidents

2 issues

Last incident

1 days ago

IsDown Logo Seamless Integrations

Get GitHub outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.
Never miss an outage
Easy setup · No coding required
Works with your existing stack

Having problems with GitHub Actions? What can you do?

  1. First, stay calm.

    • We know it's stressful when GitHub Actions is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.

  2. Make a quick evaluation of the impact of the GitHub Actions outage

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did GitHub Actions already acknowledge the issue? And published a status update? (You can find it in the top of the page or in GitHub Actions status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.

  3. Communicate with your team and users quickly

    • If GitHub Actions is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.

  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.

  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.

  6. Did GitHub Actions recover?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.

  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
    • Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.

  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.
    • For a complete overview of GitHub’s status across all services, including repositories, API requests, and workflows, visit the GitHub Status Page on IsDown

Related Services Dashboard

Services commonly monitored together with GitHub

Create your own dashboard
AWS

AWS

OK
Google Cloud

Google Cloud

OK
Google Workspace

Google Workspace

OK
Cloudflare

Cloudflare

MINOR
Azure

Azure

OK
Slack

Slack

OK
Datadog US1

Datadog US1

OK
Zoom

Zoom

OK
Figma

Figma

OK
Microsoft 365

Microsoft 365

OK
Adobe

Adobe

OK
HubSpot

HubSpot

OK
Aircall

Aircall

OK
Stripe

Stripe

OK
Airtable

Airtable

OK

Want to be informed about GitHub status changes?

IsDown offers an easy way to monitor GitHub with maximum flexibility

Major Outages Notifications

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.

Minor Outages 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.

Outage Details

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.

Maintenance Feed

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.

Component Filtering

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.

Early Outage Indicators

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.

Reports by users in other services in the last 12 hours

Microsoft 365
Microsoft 365 user reports
Roblox https://roblox.com
Roblox user reports
CoinDCX https://coindcx.com
CoinDCX user reports
Meta https://meta.com
Meta user reports
Justworks https://justworks.com
Justworks user reports
Render https://render.com/
Render user reports
Epic Games https://epicgames.com/
Epic Games user reports
ClassApp https://classapp.co
ClassApp user reports
Steam https://store.steampowered.com/?l=portuguese
Steam user reports
Reddit https://www.reddit.com/
Reddit user reports
Gengo https://gengo.com
Gengo user reports
Spectrum https://www.spectrum.net/
Spectrum user reports

Frequently Asked Questions

How does GitHub Actions interact with the GitHub API?

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.

How do status checks impact GitHub Actions workflows?

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.

How do pull requests work with GitHub Actions?

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.

How can I resolve common GitHub Actions failures?

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.

How does the GitHub Actions dashboard help manage workflows?

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.

How can GitHub Actions improve deployment processes?

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.

Is GitHub Actions slow today?

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.

How are GitHub Actions outages detected?

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.

When was the last GitHub Actions outage?

GitHub Actions last outage was on May 08, 2025 with the title "Incident with Git Operations"

GitHub not working for you? How do I know if GitHub is down?

  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.

How IsDown compares to DownDetector?

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.

Never again lose time looking in the wrong place

Start Monitoring in 5 minutes

14-day free trial · No credit card required · No code required