Hi Zeabur team,
I'm unable to access my service at twolambda.zeabur.app from the United States. However, friends in China can access it without issues. The service is running and the networking is configured with a public domain pointing to container port 8080 (HTTP).
The site is completely unreachable from the US. Connecting with curl -v shows that the TCP connection to port 443 succeeds, but the TLS handshake immediately fails with a "Broken pipe" error:
- Connected to twolambda.zeabur.app (43.199.8.212) port 443
- ALPN: curl offers h2,http/1.1
- (304) (OUT), TLS handshake, Client hello (1):
- Send failure: Broken pipe
The DNS always resolves to the HKG1 (Hong Kong) ingress with no geo-based routing:
twolambda.zeabur.app → hkg1.cname.zeabur-dns.com → hkg1.ingress.zeabur-dns.com → 43.199.8.212 (ap-east-1)
A traceroute from San Francisco shows the traffic routing through Tokyo with significant packet loss before reaching Hong Kong:
Hop 10: * * * (packet loss)
Hop 11: 64.86.26.32 — 140ms
Hop 12: 64.86.26.39 — 208ms
Hop 13: qcore1.tv2-tokyo.as6453.net — 157ms (Tokyo)
Hop 14: * * * (packet loss)
Hop 15: tcore1.av3-toyohashi.as6453.net — 161ms (Toyohashi, Japan)
The connection reaches the server IP but the TLS handshake is dropped. Since users in China (closer to HKG1) can access it fine, this appears to be an issue with the HKG1 ingress handling connections from outside Asia.
Details:
- My IP: 71.198.21.95 (San Francisco, CA — Comcast)
- Project: my-v0-project
- Domain: twolambda.zeabur.app
- Region: HKG1
- Ingress IP: 43.199.8.212
Could you please investigate whether the HKG1 ingress has issues with TLS termination for non-Asian traffic, or if there's a way to route US traffic to a closer region?
Thanks!