Static Webapp Throwing Random 500s

Question

We have multiple static web apps in different subscriptions. This morning they all started return 500 errors for about 5% of all requests given to them. It appears random as to what request gets a 500 error. Some are for static content, others are for proxied backend API calls. They aren't consistent at all. All 500's are coming from "Azure Static Web Apps" and not from our backend. We don't use function apps.

The "Diagnostics" page also returns an error when I try to use that

"Sorry, an error occurred. Please refresh the page and try again."

Its been at least 30min and I see no public service outage. Anyone else having this issue?

Answer 1

Hi @Matt Davis

Thank you for reaching us regarding the issue.

Thanks for confirming that issue is auto-resolved.

From our investigation we found that Azure Static Web Apps platform issue (edge / proxy / routing layer).This was not caused by your application code, build artifacts, configuration, or backend services.

• Errors originated from Azure Static Web Apps (confirmed via response headers and network traces), not your backend.
• Failures were random and inconsistent, some requests succeeded, others failed for the exact same resource.
• The issue affected multiple apps across subscriptions simultaneously and self-resolved, which is characteristic of a transient Microsoft-side platform glitch.

Recommended Next Steps

• Capture detailed diagnostics for any future occurrences:
  • Timestamps, failing URLs, response headers, and any x-ms-correlation-id or request IDs.
  • Browser Network tab screenshots.
• Monitor proactively:
  • Use Azure Monitor metrics: CdnPercentageOf5XX, SiteErrors, CdnRequestCount, and CdnTotalLatency.
  • Enable and review Static Web Apps HTTP logs where available.
• Escalate if it recurs:
• Open an Azure Technical Support ticket under Static Web Apps.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.

Answer 2

Hello Matt Davis,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that your Static Web App throwing random intermittent HTTP 500 errors.

Based on the pattern described, this is not a normal application-code or backend issue. The strongest evidence is that both static content and proxied API routes fail randomly, the backend is not producing the 500 responses, and the Azure Static Web Apps diagnostics blade is also failing. This points to an Azure Static Web Apps edge/proxy/platform issue that requires Microsoft-side Internal correlation.

You will need to:

• Capture failing request timestamps, URLs, response headers, and request identifiers.
• Validate the issue in Azure Monitor using CdnPercentageOf5XX, SiteErrors, CdnRequestCount, and CdnTotalLatency.
• Export or capture Static Web Apps HTTP logs where available.
• Report the impact in Azure Service Health, even if no public Azure outage is visible.
• Open an Azure technical support request for Static Web Apps and ask Microsoft to correlate the failed requests with SWA edge/proxy telemetry. - You can also contact Priority Customer Support
• If production impact is high, temporarily redeploy or route traffic to a new Static Web App resource or alternate hosting path while Microsoft investigates.

The public Azure Status page not showing an outage does not rule out this issue - https://docs.azure.cn/en-us/service-health/azure-status-overview, https://azure.status.microsoft/

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

---

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.