Persistent CDN Distribution Failures - 10 Consecutive Deployment Failures #1704
Description
Azure Support Ticket: Static Web Apps Deployment Failure
Date: November 4, 2025
Subscription ID: 1d9b5f85-1000-4163-b266-17908db6a51a
Subscription Name: Cupreading Main
Severity: B (Business Impact)
Issue Summary
Problem: All deployments to Azure Static Web Apps are failing with error: "Deployment Failure Reason: Failure during content distribution."
Impact: Unable to deploy any code changes to production. This has been occurring since November 4, 2025, 10:26 UTC.
Duration: 2+ hours with 10 consecutive failed deployments
Affected Resources
Primary Resource (Original App)
- Name: raqballusa
- Resource ID: /subscriptions/1d9b5f85-1000-4163-b266-17908db6a51a/resourceGroups/CoffeeFortuneAI-RG/providers/Microsoft.Web/staticSites/raqballusa
- Location: East US 2
- SKU: Standard
- Hostname: lively-sand-07866a00f.2.azurestaticapps.net
- Status: Previously deployed content still accessible, but new deployments fail
Secondary Resource (New App - Testing)
- Name: raqballusa-new
- Resource ID: /subscriptions/1d9b5f85-1000-4163-b266-17908db6a51a/resourceGroups/CoffeeFortuneAI-RG/providers/Microsoft.Web/staticSites/raqballusa-new
- Location: West US 2
- SKU: Standard
- Hostname: wonderful-sand-02d96771e.3.azurestaticapps.net
- Status: Never successfully deployed (created today to test different region)
Failed Deployment Details
GitHub Actions Workflow Runs (10 Consecutive Failures)
Error Message Pattern
All deployments fail with identical error after successful upload:
[37mFinished building function app with Oryx[0m
[37mZipping Api Artifacts[0m
[37mDone Zipping Api Artifacts[0m
[37mZipping App Artifacts[0m
[37mDone Zipping App Artifacts[0m
[37mUploading build artifacts.[0m
[32mFinished Upload. Polling on deployment.[0m
[37mStatus: InProgress. Time: 0.173287(s)[0m
[37mStatus: Failed. Time: 15.3511666(s)[0m
[31mDeployment Failed :([0m
[31mDeployment Failure Reason: Failure during content distribution.[0m
Key Observation: Build and upload complete successfully. Failure occurs during CDN content distribution phase.
Troubleshooting Steps Taken
1. Verified Project Configuration ✅
- File Count: 116 files (well below 3000 file limit)
- Total Size: 28MB (within limits)
- Non-ASCII Characters: None found in file paths
- Build Configuration: Valid and unchanged from previous successful deployments
2. Tested Different Regions ✅
- Created new Static Web App in West US 2 (original was East US 2)
- Same error persists across both regions
- Rules out region-specific CDN issues
3. Verified Account Status ✅
- Subscription State: Enabled
- Spending Limit: Off (no restrictions)
- Quota: PayAsYouGo (active)
- No resource locks or policy restrictions
- All resources show "Succeeded" provisioning state
4. Tested Multiple Retries ✅
- 10 consecutive deployment attempts over 2 hours
- All failed with identical error
- Rules out transient/temporary issues
5. Verified Existing Content ✅
- Old deployment still accessible at https://lively-sand-07866a00f.2.azurestaticapps.net
- Returns HTTP 200
- Static content serving correctly
- Only NEW deployments are failing
6. Updated Deployment Tokens ✅
- Generated fresh deployment token
- Updated GitHub secrets
- Reconnected GitHub integration
- No change in behavior
Deployment Configuration
GitHub Actions Workflow:
- name: Build And Deploy
uses: Azure/static-web-apps-deploy@v1
with:
azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_WONDERFUL_SAND_02D96771E }}
repo_token: ${{ secrets.GITHUB_TOKEN }}
action: upload
app_location: website
api_location: "website/api"
output_location: ""
skip_app_build: true
production_branch: mainProject Structure:
- Frontend: Pure static HTML/CSS/JS in
/website - Backend: Azure Functions (Node.js) in
/website/api - Dependencies: PostgreSQL database, Azure Key Vault
Possible Relationship to Recent Azure Outages
Azure Front Door/CDN Outages (October 2025):
- October 29-30, 2025: Major Azure Front Door/CDN outage
- October 9, 2025: Earlier CDN latency issues in multiple regions
Question: Could these recent Azure CDN infrastructure problems still be affecting Static Web Apps CDN distribution?
Research on Known Issues
GitHub Issue Tracking shows this is a known intermittent problem:
However, in those cases, the issue was intermittent or resolved after retry. In our case:
- 10/10 deployments failed (100% failure rate)
- Persists across multiple regions
- Continues for 2+ hours
This suggests a more systemic issue rather than transient CDN problems.
Business Impact
Severity Justification (B - Business Impact):
- Production website cannot be updated with critical changes
- Key Vault migration code is stuck in testing
- Unable to deploy security patches or bug fixes
- Cannot proceed with planned e-commerce features
- Custom domain (raqballusa.com) cannot be migrated to new infrastructure
Workaround Status:
- Existing deployment continues to serve traffic
- However, any code changes (security, features, fixes) cannot be deployed
- This is blocking development and business operations
Requested Actions
- Investigate CDN distribution failures for both Static Web Apps
- Check for any backend CDN service issues affecting our subscription or region
- Verify CDN endpoint health for both raqballusa and raqballusa-new
- Review recent Azure Front Door/CDN incidents for potential ongoing impact
- Provide workaround if CDN distribution is experiencing service degradation
- Estimated Time to Resolution for planning purposes
Contact Information
- GitHub Repository: https://github.com/ruchanruchan/raqballusa
- Production URL: https://lively-sand-07866a00f.2.azurestaticapps.net
- Custom Domain: raqballusa.com (not yet configured)
Additional Data Available Upon Request
- Complete GitHub Actions logs for all 10 failed deployments
- Azure CLI diagnostic output
- Resource configuration exports
- Build artifact checksums
- Network trace data
Thank you for your assistance in resolving this deployment issue.