Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content is not distributed in the Brazil South region. #1549

Open
passarela opened this issue Sep 24, 2024 · 1 comment
Open

Content is not distributed in the Brazil South region. #1549

passarela opened this issue Sep 24, 2024 · 1 comment

Comments

@passarela
Copy link

passarela commented Sep 24, 2024

Describe the bug

I am approving the implementation of Azure Static Web Apps, but most of my customers are in Brazil and it seems to me that the Global distribution is not serving Brazil.

To Reproduce

  1. Deploy Azure Static Web App

  2. Access through a region in Brazil.

  3. Test CDN (https://www.cdnperf.com/tools/cdn-latency-benchmark/)
    image
    https://www.cdnperf.com/tools/cdn-latency-benchmark/?id=mt8el0m1go5hkg

  4. See that in Brazil it is resolved with IP (20.75.112.13), hosted
    image

Expected behavior
CDN must resolve to IP in a datacenter in the Brazil region.

Additional context
I would like to understand why the Global Azure Static Web Apps resource does not resolve the CDN with an IP from a region in Brazil.

@levidiorginis
Copy link

levidiorginis commented Sep 27, 2024

I am facing the exact same issue with Azure Static Web Apps, especially for customers in Brazil. The current behavior, where the CDN resolves to an IP outside the country (20.75.112.13 and 20.22.16.164), is causing significant latency. Since Azure Static Web Apps is considered a global resource, I believe a fix is necessary to improve the experience for users in Brazil.

As shown in the attached image from the CDNPerf website, which measures latency across different regions, Brazil is experiencing high response times. The latencies in Salvador, Fortaleza, and Rio de Janeiro are all above 100ms. After checking the origin of the IPs (20.22.16.164 and 20.75.112.13), I found that both are allocated to servers outside Brazil, specifically in the United States, which is contributing to the high latency.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants