Hi @Sergio Ochoa,
This does appear to be a DNS caching or routing-related issue. Sometimes local DNS caches hold outdated or incorrect info, open a Command Prompt as an administrator and run ipconfig /flushdns
. Then attempt to access your app again. Test if it works on another device on the same network, this will confirm whether the issue is device-dependent or related to your own network.
Even if you have changed your DNS to Google's or Cloudflare's, attempt to set it at the router level rather than on your computer. Google DNS: 8.8.8.8 and 8.8.4.4 Cloudflare DNS: 1.1.1.1 and 1.0.0.1
Check if the domain resolves to an IP address, From Command Prompt, run: nslookup icy-sky-0b3ce1210.6.azurestaticapps.net
. If not, a DNS propagation issue is probably the problem.
As you mentioned AT&T reported that they didn't block the domain, some ISPs have filters or security features that might trigger resets. You might try using a VPN to determine if that bypasses the issue.
Sometimes problems can occur on Azure's end as well. You can look at the Azure Status Page to determine if there are any current issues. A new deployment will resolve strange networking or provisioning problems, redeploy: Quickstart: Deploy a Static Web App
Even though you're using the default domain, verify whether any networking restrictions were applied to the app in Azure.
You may need to try temporarily setting a custom domain on your app to check if this will fix the access problem
https://learn.microsoft.com/en-us/azure/static-web-apps/private-endpoint
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Let me know if you have any further Queries.