Cached JavaScript stalls after HTTP 200 from an Accra connection

I’m troubleshooting a Vercel Hobby deployment from a tethered internet connection in Accra, Ghana. Its versioned public vendor.js is 267,351 bytes decoded. A complete gzip transfer measured 85,246 bytes.

On 7 November 2026, two HTTP/1.1 and two HTTP/2 GETs returned HTTP 200 with a CDN cache hit and a fra1 region marker. Each reached a 20-second cutoff after receiving only 13,037 to 49,152 compressed body bytes.
Requests without compression also stalled. Chrome and Edge reproduced the startup issue, and Edge recorded ERR_HTTP2_PING_FAILED on one runtime request.
Independent probes downloaded the same URL in about 35 ms from Frankfurt and 160 ms from Los Angeles. I haven’t been able to run the full download from a second Ghanaian network, so the affected part of the delivery path is still open.

Is there a supported private channel for sharing the reproduction URL and request IDs with Vercel so the delivery path can be traced? I’d also be interested to hear whether anyone has seen comparable cached static downloads stall on another Ghanaian ISP.

On 7 November 2026, two HTTP/1.1 and two HTTP/2 GETs returned HTTP 200 with a CDN cache hit and a fra1 region marker. Each reached a 20-second cutoff after receiving only 13,037 to 49,152 compressed body bytes.
Requests without compression also stalled. Chrome and Edge reproduced the startup issue, and Edge recorded ERR_HTTP2_PING_FAILED on one runtime request.
Independent probes downloaded the same URL in about 35 ms from Frankfurt and 160 ms from Los Angeles. I haven’t been able to run the full download from a second Ghanaian network, so the affected part of the delivery path is still open.