Are Pages deployments broken?

[erdostom]

Select Topic Area

Question

Body

All of my deployments are stuck on

Getting Pages deployment status...
Current status: deployment_queued

[nbsmani]

Same error for me too!

[nbsmani]

My site is back online just now.

[petrikkachur]

Same

[Stitch-P]

Same here

[ShingZhanho]

Same here. Kept re-running and only got it to deploy once. Other runs are all failing because of infinite queue.

[sabman]

Same ... won't update my page

[claybratt]

Same

[rvanbaalen]

Endless cycles of queued deployments that never deploy indeed. Switching over to Cloudflare Pages for the time being.

Edit: something seems to be going on at Github; "ability to merge automatically"-check is also taking ages now.

[tommhe14]

same issue, yet the status pages reports that its functional? https://www.githubstatus.com

How does one report this to a github dev?

[theGEBIRGE]

I have the same problem.

[theGEBIRGE]

Update: Now a newly triggered deployment ran to completion without any action taken on my end.

[LuisFilipeTinos]

Same problem here

[kashishhora]

Same issue over here, been like this for over an hour now

[shinybrar]

Seeing the same issue as well, +1 for the github team to update us.

[lzhou-lilly]

Same issue, US east.

Fetching artifact metadata for "github-pages" in this workflow run
Found 4 artifact(s)
Error: Fetching artifact metadata failed. Is githubstatus.com reporting issues with API requests, Pages, or Actions? Please re-run the deployment at a later time.
Error: Error: Multiple artifacts named "github-pages" were unexpectedly found for this workflow run. Artifact count is 4.
at getArtifactMetadata (/__w/_actions/actions/deploy-pages/v4/src/internal/api-client.js:89:1)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Deployment.create (/__w/_actions/actions/deploy-pages/v4/src/internal/deployment.js:66:1)
at main (/__w/_actions/actions/deploy-pages/v4/src/index.js:30:1)

[lzhou-lilly]

Follow up: retrying the job sometimes trigger another issue of github:

Run actions/checkout@v6
...
Fetching the repository
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +*******************************:refs/remotes/origin/main
remote: Repository not found.
Error: fatal: repository 'https://github.com/***********/***************/' not found
The process '/usr/bin/git' failed with exit code 128

[lzhou-lilly]

OK, what worked for me, is that I have to remove failed runs, until artifact count is 0.

Each gh pages deployment run create a zip artifact. That is what those "Artifact count is 4" (and counting) was. And the error shows github is not happy with this pile of artifacts. If you do not remove those failed runs, they will get garbage collected eventually, but I dont know when.

Not sure what caused the first failure, but existing artifacts do seem to cause troubles for me.

Of course, this is just a hypothesis with my n of 1.

[ShingZhanho]

That's a different problem. The multiple github-pages artefacts has been a long lasting problem (see actions/deploy-pages#338). But the current problem seems to be at GitHub Pages' servers because the deployment is constantly stuck on the deployment_queued state.

[lzhou-lilly]

My first error is what the OP reported and that messed up my Artifacts in subsequent runs, no matter how I retried. That is what I am reporting and sharing in case anyone is in the same state as I was.

[audioslayer]

yeah i cant deploy anything new and stuck in the queue. Cant even delete old work actions, there just "stuck"

[RealBenjo]

thank God this is just a Github issue and not my goofy code (i'm kind of new to Github so i don't know exactly how this works).

[yanshay]

Unfortunately they are not aware of the issue: https://www.githubstatus.com/

[joejenett]

Just started working for me - good luck y'all!

[luminousherbs]

same for me

[briannafair]

Same here too!

[yamatt]

After quite a few deployment_queued I had one complete successfully after 2 minutes, but my next run is still going after 5 minutes.

[Uzy777]

same here. 🤣

[sreeharsha1902]

same here stuck in queue. us east region

[briannafair]

After 5 attempts later and an 8 minute wait on deploy it finally deployed for me. There is still hope!

[Lysander666]

It's not 'working'. Occasionally one page creeps through, but the rest will just hang and fail.

[undeadgalore13]

Been having the same issue since 11am est today. its now 9pm est for me.

extremely Annoying. Im using it to host a page to provide Meeting Links for people in need and i cant update it and someone might need it.
and its the first time ive used GitHub too. not a really good experience. probably going to end my usage here and when i get paid get a domain and a hosting service.

[ShingZhanho]

I tried deploying again at 9am UTC+8 and it seems to be back to normal. But's it's crazy they didn't even mention it on their status tracker when this many people are experiencing the issue.

[xutianyue]

same here still
get stuck in this infinite loop:

Getting Pages deployment status...
Current status: 

[xutianyue]

same here still get stuck in this infinite loop:

Getting Pages deployment status...
Current status: 

Update:
Re-tried for the 5th time and somehow it worked. Weird

[ShingZhanho]

Can only say that's luck. Sometimes it does work if you retry multiple times but for most workflow runs it just fails. The problem seems to still be there. 😮‍💨

[jsoref]

Normal runs for my workflow are ~2m with ~9-10s for publishing.
Today I've seen runs taking 8+m with >5m for publishing.

Oddly, there's nothing on https://www.githubstatus.com/history that matches -- https://www.githubstatus.com/incidents/zwlfnp5z0r4s appears to be about code search.

[undeadgalore13]

seems to be working now thank godSent from my iPhoneOn Jan 13, 2026, at 10:19 PM, Tianyue Xu ***@***.***> wrote: same here still get stuck in this infinite loop: Getting Pages deployment status... Current status: Update: Re-tried for the 5th time and somehow it worked. Weird —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[Stewie-pixel]

I think there is sth wrong w the GitHub Pages service
Cuz GitHub Pages runs on shared infrastructureand when there’s high traffic or an internal slowdown, new deployments are accepted but not started. In this situation, deployments can remain queued for a long time, just try to cancel and retry later or wait until GitHub’s Pages service recovers.

[nyabla]

still an issue :-(

[jsoref]

Right now there's a general actions outage: https://www.githubstatus.com/incidents/5ccghcfrkv39

[nyabla]

@jsoref thanks for alerting me

[rvanbaalen]

@jsoref took them long enough the acknowledge this on the status page.. now lets hope for a quick fix now that it's generally known 🤞🏼