Current behavior
I have a Next.js application deployed on Vercel. Custom domain: https://mytps.app
Vercel deployment: https://tps-app-theta.vercel.app The application loads correctly on:
- macOS
- iPhone (Safari)
- Desktop Chrome However, on Android devices the custom domain never loads. Chrome reports:
net::ERR_HTTP2_PING_FAILEDThe browser eventually shows a blank white page. The important part is that the Vercel deployment URL works perfectly on the exact same Android device, browser and network. Only the custom domain fails.
Expected behavior
Both domains should behave identically because they point to the same deployment.
What I tested
- Multiple Android phones
- Multiple Android browsers
- Wi-Fi and mobile data
- Different networks
- DNS verified
- SSL verified
- Vercel domain configuration verified Results:
- https://tps-app-theta.vercel.app ✅ Works
- https://mytps.app ❌ Fails only on Android curl returns:
HTTP/2 200DNS resolves correctly. Chrome DevTools consistently reports:
net::ERR_HTTP2_PING_FAILEDI also confirmed this is not an application bug because the exact same deployment works through the Vercel subdomain.
Project information
Framework: Next.js Hosting: Vercel Project: tps-app Custom domain: https://mytps.app Deployment URL: https://tps-app-theta.vercel.app Could someone from the Edge Network team investigate whether there is a routing or HTTP/2 issue affecting the custom domain? Additional observations:
- The issue reproduces on multiple Android devices.
- The issue reproduces across multiple Android browsers.
- The same Android device, browser and network load https://tps-app-theta.vercel.app successfully.
- Only https://mytps.app fails.
- Chrome DevTools reports: net::ERR_HTTP2_PING_FAILED.