Connection timed out to Google Cloud Run service (error code 522) only when proxied

Website, Application, Performance
1

What is the name of the domain?

tally.so

What is the error number?

522

What is the error message?

Connection timed out

What is the issue you’re encountering

An ISP from Ecuador consistently cannot connect to our website hosted in Europe (it works for everyone else)

What steps have you taken to resolve the issue?

Our website is behind Cloudflare’s proxy, and traffic is served as expected for the majority of users. However, we’ve identified a specific issue with an ISP in Ecuador, Xtrim, where users consistently encounter the error mentioned above and cannot access our website.

I worked with a network engineer from Xtrim who provided a trace, but it stops at Cloudflare’s IPs. Interestingly, when I shared a private link that bypasses Cloudflare and points directly to our Google Cloud Run service, users from Xtrim could access the website without issue. This suggests the problem lies in the connection between Cloudflare and Google Cloud Run.

For reference, here are some of the affected IPs associated with Xtrim:
• 186.71.152.116
• 190.155.231.245
• 181.175.161.39
• 200.63.213.51

It’s likely that all networks under their AS 14522 are impacted. Could you assist in investigating and resolving this issue?

What are the steps to reproduce the issue?

Try to access https://tally.so from any IP in AS 14522

Screenshot of the error

image.png
image.png1037×643 27.5 KB

1 Like
2

The same thing happens to me with my page, my server is in Venezuela and when I open the page in Venezuela with cloudflare, this error occurs, while with VPN it is solved (In some cases)

What I did was activate development mode, which disabled all the cache, and surprisingly it is working.

Tambien me sucede lo mismo con mi pagina, mi servidor esta en venezuela y al abrir la pagina en Venezuela con cloudflare, sucede ese error, mientras que con VPN se soluciona (En algunos casos)

Lo que hice fue activar el modo desarrollo, el cual desactivó toda la caché, y sorpresivamente está funcionando.

3

As mentioned by @cromstudioin, I bypassed cache for requests with the CF-IPCountry header set to Ecuador (EC), and users from Xtrim have confirmed they can access our website now (though it’s slow).

Could someone from the Cloudflare team provide insight into why this might be happening?

4

This is not really a solution, I suppose that if it worked well before, it is something internal to Cloudflare with Latin American countries.

5

This topic was automatically closed after 15 days. New replies are no longer allowed.