Is GitHub Actions Down? Check the current GitHub Actions status

GitHub Actions is operational

Updated

GitHub Actions not working for you?

Monitoring GitHub since April 2020. Learn more

11 incidents in 2025

Current GitHub official ongoing incidents

No incidents reported in GitHub's status page

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.

GitHub Actions issues reported by users in the last 24 hours

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.

Latest user comments about GitHub Actions problems

  • A

    Alejandro

    about 15 hours ago

    self-hosted runner not taking jobs even when restarted

  • M

    Mohamad

    4 days ago

    The Workflow keeps running and unable to be cancelled

  • I

    Isak

    5 days ago

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

  • J

    Joshua

    about 1 month ago

    Large runners not being assigned

  • I

    Ivan

    2 months ago

    Jobs are not getting picked up on GitHub hosted runners

  • A

    Amber

    2 months ago

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

  • S

    Seb

    3 months ago

    Not getting an action runner assigned

  • C

    Can

    3 months ago

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

  • D

    DimaO

    3 months ago

    Github actions are now getting bigger runners and getting queued forever

  • G

    GitHubUser3

    4 months ago

    Jobs triggered are not reflecting on GitHub Actions page.

  • J

    J

    4 months ago

    Can't find runner or stop action.

  • D

    Dom

    4 months ago

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

  • R

    Roger

    4 months ago

    Github actions stuck on queue

  • S

    siddharth

    4 months ago

    All my workflows are getting queued.....

  • A

    Akhil

    4 months ago

    Github actions are in pending state

  • M

    Mukul

    4 months ago

    Action is queued for very long

  • W

    Will

    4 months ago

    Github action are stuck queueing

  • R

    Regan

    4 months ago

    Github actions stuck in initialization state

  • E

    E

    4 months ago

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

  • S

    steven

    4 months ago

    github action jobs are pending

  • G

    Gary

    4 months ago

    Takes over 30 minutes to execute

  • G

    geoffrey

    4 months ago

    all workflow actions pending and cannot be cancelled

  • M

    Mr.V

    4 months ago

    All workflows across repos are frozen with "Queued" jobs

  • A

    Anon

    4 months ago

    Shows action queued; frozen

  • R

    RK

    4 months ago

    Actions are queued waiting for hosted, selfhosted runners

  • M

    Max

    4 months ago

    Actions stuck in queue mode

  • J

    Joshua

    4 months ago

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

  • G

    grif

    4 months ago

    actions endlessly queuing

  • R

    raj

    4 months ago

    github runners are queued

  • R

    Ry

    4 months ago

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

  • K

    Kathirvelu

    4 months ago

    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

    7 months ago

    JSON parsing is randomly failing

  • V

    VJ

    7 months ago

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

  • K

    kevin

    8 months ago

    actions failing due to unknown errors

  • O

    Ostone

    10 months ago

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

  • A

    AtoLrn

    10 months ago

    Github Actions not showing properly and never ending

  • D

    Dmytro

    10 months ago

    Simply queued all jobs and stop deploying

  • A

    Austin

    11 months ago

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

  • S

    Sajag

    12 months ago

    Github action stuck in queue

  • A

    Alaa

    about 1 year ago

    Github actions doesn't trigger

  • H

    Hassan

    over 1 year ago

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

  • A

    Anonymous

    over 1 year ago

    Self-hosted runners not picking up jobs

  • V

    Vic

    over 1 year ago

    Not triggering on push to main

  • R

    Rodrigo

    over 1 year ago

    doesnt trigger new builds

GitHub Actions outage history

IsDown has tracked 137 incidents for GitHub Actions since started monitoring GitHub status in April 2020.

Sign up and check all outage history

GitHub Actions outages in the last 30 days

Number of Incidents

5 issues

Last incident

2 days ago

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

    • 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. Service has recovered?

    • 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.
  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 monitoring them for you and alerting you if they are having issues, and create status pages to communicate with your team and users.
Official Status Pages + User Reports

The best way to monitor GitHub and other dependencies

Get instant alerts when your critical services go down. One dashboard to monitor all your vendors' status pages.

Start Your Free Trial
14-day free trial No credit card required Cancel anytime
Don't be the last to know when your dependencies go down

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.

Start Free Trial 14-day free trial · No credit card required · 3200+ cloud vendors available

Stay 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.

Frequently Asked Questions

Is GitHub Actions down today?

GitHub Actions isn't down. You can check GitHub Actions status and incident details on the top of the page. IsDown continuously monitors GitHub Actions official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current GitHub Actions status?

GitHub Actions is currently operational. You can check GitHub Actions status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.

Is there a GitHub Actions outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

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 March 08, 2025 with the title "Incident with Actions and Pages"

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.

Latest Articles from our Blog

See all the blog articles

Never again lose time looking in the wrong place

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