Skip to content
compiler.dev
Start free

Is GitHub down right now?

Live status of the GitHub services CI depends on: Actions, Git operations, pull requests and webhooks. Checked every minute against githubstatus.com.

Checking GitHub…

If this does not update, see githubstatus.com.

    Recent GitHub incidents

    Incidents that affected Actions, Git operations, pull requests or webhooks, newest first. Times in your local time zone.

    1. Loading…

    What to do when GitHub Actions is down

    1. Check the scope. An incident often hits one service, such as Actions or webhooks, while Git pushes still work. The list above shows which.
    2. Don't re-run everything at once. Jobs queued during an incident usually start once it is resolved. Mass re-runs add load and can hit API rate limits.
    3. Re-run only failed jobs afterwards. Use "Re-run failed jobs" on each workflow run, or gh run rerun <run-id> --failed.
    4. Check missed webhooks. Integrations that rely on webhooks (deploys, chat notifications, external CI) may have missed events. GitHub App owners can redeliver failed deliveries from the app's advanced settings.
    5. Hold deploys that depend on Actions until the incident is resolved, rather than deploying by hand without your usual checks.

    How compiler.dev handles GitHub outages

    compiler.dev watches this same status feed. When an incident that affected your runs is resolved, it re-delivers the webhooks GitHub failed to send and offers to re-run the jobs that failed because of it, so your pull requests don't stay red. The dashboard stays readable even while GitHub's API is unreachable. See how compiler.dev compares with GitHub-hosted runners.

    FAQ

    Where does this data come from?

    From GitHub's official status page, githubstatus.com, polled every minute. We only list incidents that touched Actions, Git operations, pull requests or webhooks.

    Why are my GitHub Actions jobs stuck on "Queued"?

    During an Actions incident, jobs wait for a runner. If GitHub shows no incident, see "Waiting for a runner to pick up this job" for the other causes.

    Will my workflows run after GitHub recovers?

    Queued jobs usually start once Actions recovers. Jobs that failed during the incident do not re-run by themselves; re-run them with "Re-run failed jobs". Events GitHub never delivered may not trigger workflows at all, so push an empty commit if a pull request shows no checks.