Share via

Static Web App piqual-ai-prod showing white screen for US users and some Indian users

Kishore Suresh 0 Reputation points
2025-08-19T14:59:35.4733333+00:00

We have an Azure Static Web App named piqual-ai-prod connected to the domain piqual.com. The app is hosted in the Central US region.

Currently, the site is accessible and working fine for some users in India. However, some users in the US are facing an issue where the page loads but only shows a white screen instead of the actual content.

We have confirmed that DNS is correctly pointing to the Azure Static Web App, and the site works from certain regions. The issue seems to be region-specific (affecting some Indian users and some US users).

Azure Static Web Apps
Azure Static Web Apps
An Azure service that provides streamlined full-stack web app development.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. RAMAMURTHY MAKARAPU 160 Reputation points Microsoft External Staff Moderator
    2025-08-20T00:28:01.78+00:00

    Hello @Kishore Suresh,

    Thank you for submitting your question on Microsoft Q&A.

    Since your Azure Static Web App (piqual-ai-prod) is globally distributed behind Azure’s edge, and you’re experiencing white screen rendering issues in specific regions (US and some India users), the issue is likely related to content delivery, caching, or client-side runtime rather than just DNS.

    Here’s some of possible causes and actions

    Region-specific CDN/edge caching issues

    • Static Web Apps are served via Azure Front Door, and sometimes an edge POP caches a corrupted or incomplete build.
    • This can result in a white screen with no errors except blank HTML/JS in the network tab.

    Action required is

    • From affected regions, use Developer Tools > Network tab to check if index.html loads completely and if JS/CSS bundles are fetched or returning 404/403 errors.
    • Test with tools like GlobalPing from different regions to compare headers.

    Client-side JS/SPA bundle mismatch

    • For React/Vue/Angular SPAs, a stale cached bundle may be served while index.html references new chunks, causing a white screen. This is common after recent deployments.

    Action required is

    • Check Chrome DevTools Console for errors like net::ERR_ABORTED 404 for JS files.
    • If present, do a hard refresh or clear cache and retest.
    • Consider enabling asset versioning in your build process.

    Geo-routing or firewall rules

    • Using Cloudflare, WAF, or custom routing can block users, but this is less likely with pure Azure Static Web Apps unless paired with Azure Front Door or Traffic Manager.

    Action required is

    • Verify there are no conditional rules by IP region in DNS/CDN.
    • Run dig piqual.com and compare resolved IPs from India and US.

    TLS/HTTP2 quirks

    • Some regions might hit older TLS edge nodes, but this usually causes connection errors, not just a blank page.

    Debugging steps

    • Test from US and India using VPN/GlobalPing and review HTTP responses.
    • Check browser console logs from affected users for missing JS bundles.
    • If it’s an edge cache issue, try purging the Static Web App CDN cache or simply redeploy to refresh caches across POPs.
    • If problems persist, consider opening an Azure Support ticket, as Microsoft may need to flush bad POP caches.
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.