[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Serverless Egress Network Block (TCP Handshake Timeout) in ALL Regions

34 views · 0 likes · 1 post


koshman23 (@akash-8667) · 2025-11-28

Hello Vercel Team and Community,

I am running into a severe, platform-level issue where my serverless function is completely unable to make any outbound HTTP requests, causing a timeout after 300 seconds on all data-fetching routes.

I have performed extensive debugging and have strong evidence that this is an **infrastructure network block** and not a code issue.

**Project Details:**

* **URL:** `https://shopify-airea-api.vercel.app`

* **Regions Tested:** Washington D.C. (`iad1`), San Francisco (`sfo1`), and Cleveland (`cle1`). **The issue persists in all regions.**

* **Node.js Version:** \[Your confirmed 22.x or 24.x\]

**Evidence of Failure:**

1. **Public API Hangs:** The `/api/debug-public` endpoint (which hits a public service like JSONPlaceholder) also hangs, proving the block is non-Supabase specific.

2. **TCP Handshake Timeout (Proof):** I used `NODE_DEBUG=http,https,net` to capture the failure. The logs confirm the function is failing at the lowest level of networking—the TCP handshake:

   ```plaintext
   NET 4: connect/multiple: attempting to connect to 104.18.38.10:443 (addressType: 4)
   NET 4: connect/multiple: setting the attempt timeout to 250 ms
   NET 4: connect/multiple: connection to 104.18.38.10:443 timed out
   
   ```

   This indicates a fundamental **egress network block** on the Vercel side preventing TCP connections from establishing across multiple regions.

Could a Vercel staff member please escalate this to the infrastructure team for an account- or project-specific routing check? Thank you for your time and assistance