Static Web Apps deployments failing/hanging since ~14:10 UTC on 21 July 2026 (BadRequest content server errors + upload timeouts)

[ogddata]

Describe the bug

Our Static Web App has been deploying successfully via GitHub Actions (Azure/static-web-apps-deploy@v1) multiple times per hour throughout the day. The last successful deployment completed at 14:10 UTC on 21 July 2026. Every deployment attempt since then has failed, with two distinct symptoms appearing across different runs:

Immediate failure with the message:
We are currently experiencing problems communicating with our content server. Please try again later or file an issue if this behavior continues.
Upload succeeds and the deployment shows Status: InProgress, but then times out after 500+ seconds with:
Upload Timed Out. Unsure if deployment was successful or not.
A clear and concise description of what the bug is.

To Reproduce
We ruled out any issue on our side by deploying a completely unmodified, trivial static HTML file with no build steps and no dependencies — it hung/failed in exactly the same way as our normal app. This confirms the issue is not related to repository content, app size, or configuration.

Relevant config: app_location: /, no API directory, staticwebapp.config.json present, no database connections configured.

Expected behavior

Deployment completes successfully as it had been doing consistently prior to 14:10 UTC.

Deployment IDs for reference

69a30c78-34af-49fc-9df0-ca1f58f823e4
7f706473-f75e-4a54-a22a-d7c02e3834b7
3c4696d0-173c-4c15-9f64-8cf4447bf9fa

[pedro-radity]

Same issue here

[ogddata]

Same issue here

I can't see anything saying the service is down but perhaps it is

[pedro-radity]

Yeah, no alerts so far

[beardsciences]

Same issue here; no alerts

[flipkuzma]

Same issue here; no alerts either.

[mrebolledo]

same issue here

[anjapadu]

Same!

[adrianalbino-pioneer]

Same

[Remingburg]

same!

[sai123murali]

Same!!!!

[RyanTuckerN]

+1

[taimooransari]

Still down, goes into polling and times out.

[Jean-LucasLS]

Same here.

[dimensionalfact]

Same here since 14:47 UTC, Central US scale unit 7 (*.7.azurestaticapps.net). Two different apps in our tenant fail the same way, and we ruled out our side:

• GitHub Actions (ubuntu-latest, Azure/static-web-apps-deploy@v1): Oryx build succeeds every run, then either the content server error or Upload Timed Out after ~600s of InProgress polling. Nine straight failures across reruns and fresh commits.
• SWA CLI from a local workstation with deployment-token auth, no GitHub in the path at all: identical content server error. DeploymentId 9fc6d174-bbb4-4437-8573-b84e6dc4e39f if anyone from the team wants to pull server-side logs.
• ARM shows the default environment stuck at status Uploading since 17:01 UTC, and the builds API for the site (providers/Microsoft.Web/staticSites/{app}/builds) returns GatewayTimeout. The management plane can't reach the app's build service either.
• Production serving is unaffected. Deployments only.

Last green deploy for us was 23:28 UTC on 20 July.

[steelkf]

Same here — confirming another affected tenant.

Setup: GitHub Actions with Azure/static-web-apps-deploy@v1, app_location: "/", managed Functions API (node 18). Oryx build succeeds on every run; only the deploy/content-distribution step fails, in the two ways this thread describes:

• Immediate: "We are currently experiencing problems communicating with our content server. Please try again later..."
• Or: "Upload Timed Out. Unsure if deployment was successful or not." after ~540s of InProgress polling.

~10 consecutive failures across fresh commits and re-runs since mid-day 21 July 2026 UTC. Ruled out our side — the build artifacts zip fine every time; it's purely the handoff to the content server. Production serving is unaffected; only new deployments are blocked.

We're on scale unit 7 — URL is happy-pond-0dc119310.7.azurestaticapps.net — matching the *.7.azurestaticapps.net unit @dimensionalfact reported above, so that's at least two independent tenants affected on scale unit 7.

Recent DeploymentId for server-side correlation: f2a60078-2cb5-4583-a1ac-d2cb1cc7b9f2