As developers, we love the seamless deployment experience of Vercel. You push to GitHub, and your app is live. But recently, I ran into a maddening network issue that made me question my own code, my security headers, and my sanity.
If your Vercel web applications (*.vercel.app or custom domains pointing to Vercel) are completely failing to load, timing out on the initial HTTPS handshake, or taking literally minutes to resolve on certain mobile networks (like MTN Zambia or Zed Mobile) while loading flawlessly on others (like Airtel)—you are not crazy, and it is not your code.
Even massive, highly-optimized sites hosted on Vercel—like Bruno Simon's famous 3D portfolio—suffer from this exact same breakdown on these specific mobile networks.
Here is the technical breakdown of why this happens and how you can protect your future users from being locked out of your apps.
The Symptom: The Endless Handshake






