Bubble systems with problems at TIM telephone operator

[cotadorsimplificado]

My clients and I are having trouble opening my SaaS when the mobile or wired network is from TIM.

Here it only opened on Claro’s 5G and Wifi from Alares and other operators.

I tested it on other third-party SaaS that I know will be built on Bubble and the same problem of not opening anything occurred.

Is the same with you?

[ri_scc_94]

Same here, this is really worrisome!

It’s important for my clients to be able to access the app and some can’t

[rogerio.frigeri]

I’m experiencing the exact same issue with my Bubble app hosted at www.clin.care.

The app works perfectly on all networks except TIM (Brazilian operator). When accessed via TIM (either mobile or fiber), the page takes a long time to load and eventually throws a timeout error.

Here are a few details I’ve gathered:

• DNS is configured correctly with A records pointing to 104.19.241.93 and 104.19.240.93.
• I confirmed the IPs are served via Cloudflare, which may be part of the issue.
• On TIM networks, ping and tracert to those IPs fail completely.
• On any other ISP (Claro, Vivo, Wi-Fi from other providers), the site loads normally.
• I tried accessing the default Bubble app URL (.bubbleapps.io), but it redirects to the custom domain automatically, so that’s not a workaround unless I remove the custom domain.

This seems to be a routing or DNS-level issue specifically between TIM and Cloudflare/Bubble.
I’d appreciate if the Bubble team could investigate this or coordinate with Cloudflare for a possible fix.

If anyone found a workaround that avoids the redirection or changes how Bubble handles the fallback URL, let me know.

[cotadorsimplificado]

Dá pra solucionar sem esperar pela TIM.
Add estes outros 2 ips que o Bubble fornece para novos apps:

Limpem o cache de DNS, se possível, e logo voltará a carregar normal.

Se demorar muito, removam os ips antigos e tbm limpem o cache.