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

[Help](/c/help/9)

# Apex domain (trenna.co) intermittently times out

33 views · 1 like · 2 posts


Felipe (@felipe-3267) · 2026-01-21

Hi Vercel team/community,

I’m experiencing intermittent connection timeouts on my apex domain (**trenna.co**) from my location in Porto Alegre, Brazil (Claro NXT / virtua.com.br ISP). The site works fine from other locations/networks, and **[www.trenna.co](http://www.trenna.co)** loads consistently without issues.

**Current setup (as recommended by Vercel):**

* Apex (**trenna.co**): A record → 216.198.79.1 (from Vercel dashboard)

* www: CNAME → \[your-vercel-cname\].vercel-dns-017.com

* Redirect: Apex → www (307 redirect configured in Domains settings)

* CAA record: 0 issue “letsencrypt.org” (verified and passing in dashboard)

* SSL: Active (Let’s Encrypt cert valid until Mar 2026)

**Symptoms:**

* From my network: [https://trenna.co](https://trenna.co) often gives ERR_CONNECTION_TIMED_OUT or takes 60+ seconds to fail.

* [https://www.trenna.co](https://www.trenna.co) loads instantly (no redirect needed).

* External checks (e.g., from other countries) show the apex works (200 or 307 redirect).

* The issue is location/ISP-specific — likely anycast routing problem.

**Debug output** (from Vercel connect debug script):

* DNS resolves apex to 216.198.79.1 consistently (via 8.8.8.8 too).

* Testing the IP range:

  * **216.198.79.1**: Connection timed out after \~3s (HTTPS 443), 100% packet loss on ping, tracert dies early.

  * All other IPs (216.198.79.65/129/193, 64.29.17.1/65/129/193): Connect successfully → TLS handshake OK, valid cert, HTTP/2 307 redirect to [https://www.trenna.co/](https://www.trenna.co/), ping \~44-55ms with 0% loss, x-vercel-id from gru1 (São Paulo region).

* Direct curl to trenna.co: Timeout after \~75s on resolved IP 216.198.79.1.

Full log attached

**What I’ve tried:**

* Flush DNS cache, incognito, different browsers/devices.

* Test on mobile data (Claro 4G/5G) — same issue on fixed line, but sometimes better.

* VPN to other BR servers → often bypasses the bad route.

* Confirmed no local firewall/antivirus blocking.

* CAA and DNS are correct (verified in dashboard and dig).

This looks like a classic anycast/BGP routing inconsistency where my ISP routes to a “bad” PoP for 216.198.79.1, while other IPs in the range hit good routes (GRU region).

**Questions:**

* Is there a way to force/avoid the problematic IP (216.198.79.1) for my apex A record?

* Recommended workaround: Invert config (make apex primary Production, redirect www → apex with 308) to avoid redirect on the flaky apex path?

* Should I switch to Vercel nameservers (ns1/2.vercel-dns.com) even for apex (with ALIAS/ANAME if supported by Namecheap)?

* Any known issues with Claro Brazil + Vercel anycast IPs?

Happy to provide more logs, screenshots, or run additional tests. Thanks in advance!

Full log:

```

Domain to test (e.g. example.com):
┌───────────────────────────────────────
├─────── Fetching IP Addresses
│
│ trenna.co IP range: 216.198.79.1, 216.198.79.65, 216.198.79.129, 216.198.79.193, 64.29.17.1, 64.29.17.65, 64.29.17.129, 64.29.17.193
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── STARTING
│
│ Domain to test: trenna.co
│ Timestamp (UTC): Wed Jan 21 23:26:30 UTC 2026
│ Timestamp (Local): Wed Jan 21 20:26:30 -03 2026
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── IP Information

{
“ip”: “179.152.53.181”,
“hostname”: “b39835b5.virtua.com.br”,
“city”: “Porto Alegre”,
“region”: “Rio Grande do Sul”,
“country”: “BR”,
“loc”: “-30.0328,-51.2302”,
“org”: “AS28573 Claro NXT Telecomunicacoes Ltda”,
“postal”: “90000-000”,
“timezone”: “America/Sao_Paulo”,
“readme”: “https://ipinfo.io/missingauth”
}
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.1
Checking headers via 216.198.79.1

* Connecting to hostname: 216.198.79.1
* Trying 216.198.79.1:443…
* Connection timed out after 3004 milliseconds
* Closing connection

Checking ping to 216.198.79.1
PING 216.198.79.1 (216.198.79.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2

— 216.198.79.1 ping statistics —
4 packets transmitted, 0 packets received, 100.0% packet loss

Checking tracert to 216.198.79.1
1  192.168.2.1 (192.168.2.1)  4.455 ms  2.791 ms  3.176 ms
2  192.168.0.1 (192.168.0.1)  3.974 ms  4.385 ms  3.610 ms
3  b3983401.virtua.com.br (179.152.52.1)  18.469 ms  19.036 ms  13.322 ms
4  \* \* \*
5  \* \* \*
6  \* \* \*
7  \* \* \*
8  \* \* \*
9  \* \* \*
10  \* \* \*
11  \* \* \*
12  \* \* \*
13  \* \* \*
14  \* \* \*
15  \* \* \*
16  \* \* \*
17  \* \* \*
18  \* \* \*
19  \* \* \*
20  \* \* \*
21  \* \* \*
22  \* \* \*
23  \* \* \*
24  \* \* \*
25  \* \* \*
26  \* \* \*
27  \* \* \*
28  \* \* \*
29  \* \* \*
30  \* \* \*
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.65
Checking headers via 216.198.79.65

* Connecting to hostname: 216.198.79.65
* Trying 216.198.79.65:443…
* Connected to 216.198.79.65 (216.198.79.65) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
  } \[314 bytes data\]
* (304) (IN), TLS handshake, Server hello (2):
  { \[122 bytes data\]
* (304) (IN), TLS handshake, Unknown (8):
  { \[15 bytes data\]
* (304) (IN), TLS handshake, Certificate (11):
  { \[2582 bytes data\]
* (304) (IN), TLS handshake, CERT verify (15):
  { \[264 bytes data\]
* (304) (IN), TLS handshake, Finished (20):
  { \[36 bytes data\]
* (304) (OUT), TLS handshake, Finished (20):
  } \[36 bytes data\]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=trenna.co
* start date: Dec 18 14:45:39 2025 GMT
* expire date: Mar 18 14:45:38 2026 GMT
* issuer: C=US; O=Let’s Encrypt; CN=R12
* SSL certificate verify ok.
* using HTTP/2
* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/
* \[HTTP/2\] \[1\] \[:method: GET\]
* \[HTTP/2\] \[1\] \[:scheme: https\]
* \[HTTP/2\] \[1\] \[:authority: trenna.co\]
* \[HTTP/2\] \[1\] \[:path: /\]
* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]
* \[HTTP/2\] \[1\] \[accept: */*\]

> GET / HTTP/2
> Host: trenna.co
> User-Agent: curl/8.7.1
> Accept: */*

* Request completely sent off
  < HTTP/2 307
  < cache-control: public, max-age=0, must-revalidate
  < content-type: text/plain
  < date: Wed, 21 Jan 2026 23:28:10 GMT
  < location: https://www.trenna.co/
  < server: Vercel
  < strict-transport-security: max-age=63072000
  < x-vercel-id: gru1::cklmr-1769038090026-2645e6c429a5
  <
  { \[15 bytes data\]
* Connection #0 to host 216.198.79.65 left intact

Checking ping to 216.198.79.65
PING 216.198.79.65 (216.198.79.65): 56 data bytes
64 bytes from 216.198.79.65: icmp_seq=0 ttl=243 time=44.373 ms
64 bytes from 216.198.79.65: icmp_seq=1 ttl=243 time=44.100 ms
64 bytes from 216.198.79.65: icmp_seq=2 ttl=243 time=45.611 ms
64 bytes from 216.198.79.65: icmp_seq=3 ttl=243 time=44.578 ms

— 216.198.79.65 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 44.100/44.666/45.611/0.572 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.129
Checking headers via 216.198.79.129

* Connecting to hostname: 216.198.79.129
* Trying 216.198.79.129:443…
* Connected to 216.198.79.129 (216.198.79.129) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
  } \[314 bytes data\]
* (304) (IN), TLS handshake, Server hello (2):
  { \[122 bytes data\]
* (304) (IN), TLS handshake, Unknown (8):
  { \[15 bytes data\]
* (304) (IN), TLS handshake, Certificate (11):
  { \[2582 bytes data\]
* (304) (IN), TLS handshake, CERT verify (15):
  { \[264 bytes data\]
* (304) (IN), TLS handshake, Finished (20):
  { \[36 bytes data\]
* (304) (OUT), TLS handshake, Finished (20):
  } \[36 bytes data\]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=trenna.co
* start date: Dec 18 14:45:39 2025 GMT
* expire date: Mar 18 14:45:38 2026 GMT
* issuer: C=US; O=Let’s Encrypt; CN=R12
* SSL certificate verify ok.
* using HTTP/2
* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/
* \[HTTP/2\] \[1\] \[:method: GET\]
* \[HTTP/2\] \[1\] \[:scheme: https\]
* \[HTTP/2\] \[1\] \[:authority: trenna.co\]
* \[HTTP/2\] \[1\] \[:path: /\]
* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]
* \[HTTP/2\] \[1\] \[accept: */*\]

> GET / HTTP/2
> Host: trenna.co
> User-Agent: curl/8.7.1
> Accept: */*

* Request completely sent off
  < HTTP/2 307
  < cache-control: public, max-age=0, must-revalidate
  < content-type: text/plain
  < date: Wed, 21 Jan 2026 23:28:13 GMT
  < location: https://www.trenna.co/
  < server: Vercel
  < strict-transport-security: max-age=63072000
  < x-vercel-id: gru1::vbhjb-1769038093309-8b9df01af79c
  <
  { \[15 bytes data\]
* Connection #0 to host 216.198.79.129 left intact

Checking ping to 216.198.79.129
PING 216.198.79.129 (216.198.79.129): 56 data bytes
64 bytes from 216.198.79.129: icmp_seq=0 ttl=243 time=49.086 ms
64 bytes from 216.198.79.129: icmp_seq=1 ttl=243 time=65.509 ms
64 bytes from 216.198.79.129: icmp_seq=2 ttl=243 time=49.244 ms
64 bytes from 216.198.79.129: icmp_seq=3 ttl=243 time=45.415 ms

— 216.198.79.129 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 45.415/52.313/65.509/7.771 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.193
Checking headers via 216.198.79.193

* Connecting to hostname: 216.198.79.193
* Trying 216.198.79.193:443…
* Connected to 216.198.79.193 (216.198.79.193) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
  } \[314 bytes data\]
* (304) (IN), TLS handshake, Server hello (2):
  { \[122 bytes data\]
* (304) (IN), TLS handshake, Unknown (8):
  { \[15 bytes data\]
* (304) (IN), TLS handshake, Certificate (11):
  { \[2582 bytes data\]
* (304) (IN), TLS handshake, CERT verify (15):
  { \[264 bytes data\]
* (304) (IN), TLS handshake, Finished (20):
  { \[36 bytes data\]
* (304) (OUT), TLS handshake, Finished (20):
  } \[36 bytes data\]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=trenna.co
* start date: Dec 18 14:45:39 2025 GMT
* expire date: Mar 18 14:45:38 2026 GMT
* issuer: C=US; O=Let’s Encrypt; CN=R12
* SSL certificate verify ok.
* using HTTP/2
* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/
* \[HTTP/2\] \[1\] \[:method: GET\]
* \[HTTP/2\] \[1\] \[:scheme: https\]
* \[HTTP/2\] \[1\] \[:authority: trenna.co\]
* \[HTTP/2\] \[1\] \[:path: /\]
* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]
* \[HTTP/2\] \[1\] \[accept: */*\]

> GET / HTTP/2
> Host: trenna.co
> User-Agent: curl/8.7.1
> Accept: */*

* Request completely sent off
  < HTTP/2 307
  < cache-control: public, max-age=0, must-revalidate
  < content-type: text/plain
  < date: Wed, 21 Jan 2026 23:28:16 GMT
  < location: https://www.trenna.co/
  < server: Vercel
  < strict-transport-security: max-age=63072000
  < x-vercel-id: gru1::q6xx2-1769038096579-ad6ed3aa7338
  <
  { \[15 bytes data\]
* Connection #0 to host 216.198.79.193 left intact

Checking ping to 216.198.79.193
PING 216.198.79.193 (216.198.79.193): 56 data bytes
64 bytes from 216.198.79.193: icmp_seq=0 ttl=243 time=50.723 ms
64 bytes from 216.198.79.193: icmp_seq=1 ttl=243 time=45.879 ms
64 bytes from 216.198.79.193: icmp_seq=2 ttl=243 time=54.966 ms
64 bytes from 216.198.79.193: icmp_seq=3 ttl=243 time=47.700 ms

— 216.198.79.193 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 45.879/49.817/54.966/3.440 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.1
Checking headers via 64.29.17.1

* Connecting to hostname: 64.29.17.1
* Trying 64.29.17.1:443…
* Connected to 64.29.17.1 (64.29.17.1) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
  } \[314 bytes data\]
* (304) (IN), TLS handshake, Server hello (2):
  { \[122 bytes data\]
* (304) (IN), TLS handshake, Unknown (8):
  { \[15 bytes data\]
* (304) (IN), TLS handshake, Certificate (11):
  { \[2582 bytes data\]
* (304) (IN), TLS handshake, CERT verify (15):
  { \[264 bytes data\]
* (304) (IN), TLS handshake, Finished (20):
  { \[36 bytes data\]
* (304) (OUT), TLS handshake, Finished (20):
  } \[36 bytes data\]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=trenna.co
* start date: Dec 18 14:45:39 2025 GMT
* expire date: Mar 18 14:45:38 2026 GMT
* issuer: C=US; O=Let’s Encrypt; CN=R12
* SSL certificate verify ok.
* using HTTP/2
* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/
* \[HTTP/2\] \[1\] \[:method: GET\]
* \[HTTP/2\] \[1\] \[:scheme: https\]
* \[HTTP/2\] \[1\] \[:authority: trenna.co\]
* \[HTTP/2\] \[1\] \[:path: /\]
* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]
* \[HTTP/2\] \[1\] \[accept: */*\]

> GET / HTTP/2
> Host: trenna.co
> User-Agent: curl/8.7.1
> Accept: */*

* Request completely sent off
  < HTTP/2 307
  < cache-control: public, max-age=0, must-revalidate
  < content-type: text/plain
  < date: Wed, 21 Jan 2026 23:28:19 GMT
  < location: https://www.trenna.co/
  < server: Vercel
  < strict-transport-security: max-age=63072000
  < x-vercel-id: gru1::mcbtr-1769038099871-84d49cfe386b
  <
  { \[15 bytes data\]
* Connection #0 to host 64.29.17.1 left intact

Checking ping to 64.29.17.1
PING 64.29.17.1 (64.29.17.1): 56 data bytes
64 bytes from 64.29.17.1: icmp_seq=0 ttl=243 time=49.074 ms
64 bytes from 64.29.17.1: icmp_seq=1 ttl=243 time=45.828 ms
64 bytes from 64.29.17.1: icmp_seq=2 ttl=243 time=45.377 ms
64 bytes from 64.29.17.1: icmp_seq=3 ttl=243 time=46.366 ms

— 64.29.17.1 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 45.377/46.661/49.074/1.436 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.65
Checking headers via 64.29.17.65

* Connecting to hostname: 64.29.17.65
* Trying 64.29.17.65:443…
* Connected to 64.29.17.65 (64.29.17.65) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
  } \[314 bytes data\]
* (304) (IN), TLS handshake, Server hello (2):
  { \[122 bytes data\]
* (304) (IN), TLS handshake, Unknown (8):
  { \[15 bytes data\]
* (304) (IN), TLS handshake, Certificate (11):
  { \[2582 bytes data\]
* (304) (IN), TLS handshake, CERT verify (15):
  { \[264 bytes data\]
* (304) (IN), TLS handshake, Finished (20):
  { \[36 bytes data\]
* (304) (OUT), TLS handshake, Finished (20):
  } \[36 bytes data\]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=trenna.co
* start date: Dec 18 14:45:39 2025 GMT
* expire date: Mar 18 14:45:38 2026 GMT
* issuer: C=US; O=Let’s Encrypt; CN=R12
* SSL certificate verify ok.
* using HTTP/2
* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/
* \[HTTP/2\] \[1\] \[:method: GET\]
* \[HTTP/2\] \[1\] \[:scheme: https\]
* \[HTTP/2\] \[1\] \[:authority: trenna.co\]
* \[HTTP/2\] \[1\] \[:path: /\]
* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]
* \[HTTP/2\] \[1\] \[accept: */*\]

> GET / HTTP/2
> Host: trenna.co
> User-Agent: curl/8.7.1
> Accept: */*

* Request completely sent off
  < HTTP/2 307
  < cache-control: public, max-age=0, must-revalidate
  < content-type: text/plain
  < date: Wed, 21 Jan 2026 23:28:23 GMT
  < location: https://www.trenna.co/
  < server: Vercel
  < strict-transport-security: max-age=63072000
  < x-vercel-id: gru1::zp695-1769038103149-14272d0cf0d9
  <
  { \[15 bytes data\]
* Connection #0 to host 64.29.17.65 left intact

Checking ping to 64.29.17.65
PING 64.29.17.65 (64.29.17.65): 56 data bytes
64 bytes from 64.29.17.65: icmp_seq=0 ttl=243 time=46.404 ms
64 bytes from 64.29.17.65: icmp_seq=1 ttl=243 time=53.850 ms
64 bytes from 64.29.17.65: icmp_seq=2 ttl=243 time=62.024 ms
64 bytes from 64.29.17.65: icmp_seq=3 ttl=243 time=59.194 ms

— 64.29.17.65 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 46.404/55.368/62.024/5.950 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.129
Checking headers via 64.29.17.129

* Connecting to hostname: 64.29.17.129
* Trying 64.29.17.129:443…
* Connected to 64.29.17.129 (64.29.17.129) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
  } \[314 bytes data\]
* (304) (IN), TLS handshake, Server hello (2):
  { \[122 bytes data\]
* (304) (IN), TLS handshake, Unknown (8):
  { \[15 bytes data\]
* (304) (IN), TLS handshake, Certificate (11):
  { \[2582 bytes data\]
* (304) (IN), TLS handshake, CERT verify (15):
  { \[264 bytes data\]
* (304) (IN), TLS handshake, Finished (20):
  { \[36 bytes data\]
* (304) (OUT), TLS handshake, Finished (20):
  } \[36 bytes data\]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=trenna.co
* start date: Dec 18 14:45:39 2025 GMT
* expire date: Mar 18 14:45:38 2026 GMT
* issuer: C=US; O=Let’s Encrypt; CN=R12
* SSL certificate verify ok.
* using HTTP/2
* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/
* \[HTTP/2\] \[1\] \[:method: GET\]
* \[HTTP/2\] \[1\] \[:scheme: https\]
* \[HTTP/2\] \[1\] \[:authority: trenna.co\]
* \[HTTP/2\] \[1\] \[:path: /\]
* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]
* \[HTTP/2\] \[1\] \[accept: */*\]

> GET / HTTP/2
> Host: trenna.co
> User-Agent: curl/8.7.1
> Accept: */*

* Request completely sent off
  < HTTP/2 307
  < cache-control: public, max-age=0, must-revalidate
  < content-type: text/plain
  < date: Wed, 21 Jan 2026 23:28:26 GMT
  < location: https://www.trenna.co/
  < server: Vercel
  < strict-transport-security: max-age=63072000
  < x-vercel-id: gru1::hkq45-1769038106443-4e34d4128704
  <
  { \[15 bytes data\]
* Connection #0 to host 64.29.17.129 left intact

Checking ping to 64.29.17.129
PING 64.29.17.129 (64.29.17.129): 56 data bytes
64 bytes from 64.29.17.129: icmp_seq=0 ttl=243 time=43.060 ms
64 bytes from 64.29.17.129: icmp_seq=1 ttl=243 time=49.917 ms
64 bytes from 64.29.17.129: icmp_seq=2 ttl=243 time=47.891 ms
64 bytes from 64.29.17.129: icmp_seq=3 ttl=243 time=42.941 ms

— 64.29.17.129 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 42.941/45.952/49.917/3.038 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.193
Checking headers via 64.29.17.193

* Connecting to hostname: 64.29.17.193
* Trying 64.29.17.193:443…
* Connected to 64.29.17.193 (64.29.17.193) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
  } \[314 bytes data\]
* (304) (IN), TLS handshake, Server hello (2):
  { \[122 bytes data\]
* (304) (IN), TLS handshake, Unknown (8):
  { \[15 bytes data\]
* (304) (IN), TLS handshake, Certificate (11):
  { \[2582 bytes data\]
* (304) (IN), TLS handshake, CERT verify (15):
  { \[264 bytes data\]
* (304) (IN), TLS handshake, Finished (20):
  { \[36 bytes data\]
* (304) (OUT), TLS handshake, Finished (20):
  } \[36 bytes data\]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=trenna.co
* start date: Dec 18 14:45:39 2025 GMT
* expire date: Mar 18 14:45:38 2026 GMT
* issuer: C=US; O=Let’s Encrypt; CN=R12
* SSL certificate verify ok.
* using HTTP/2
* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/
* \[HTTP/2\] \[1\] \[:method: GET\]
* \[HTTP/2\] \[1\] \[:scheme: https\]
* \[HTTP/2\] \[1\] \[:authority: trenna.co\]
* \[HTTP/2\] \[1\] \[:path: /\]
* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]
* \[HTTP/2\] \[1\] \[accept: */*\]

> GET / HTTP/2
> Host: trenna.co
> User-Agent: curl/8.7.1
> Accept: */*

* Request completely sent off
  < HTTP/2 307
  < cache-control: public, max-age=0, must-revalidate
  < content-type: text/plain
  < date: Wed, 21 Jan 2026 23:28:29 GMT
  < location: https://www.trenna.co/
  < server: Vercel
  < strict-transport-security: max-age=63072000
  < x-vercel-id: gru1::xznqg-1769038109737-c96f2a31e405
  <
  { \[15 bytes data\]
* Connection #0 to host 64.29.17.193 left intact

Checking ping to 64.29.17.193
PING 64.29.17.193 (64.29.17.193): 56 data bytes
64 bytes from 64.29.17.193: icmp_seq=0 ttl=243 time=47.651 ms
64 bytes from 64.29.17.193: icmp_seq=1 ttl=243 time=55.653 ms
64 bytes from 64.29.17.193: icmp_seq=2 ttl=243 time=55.783 ms
64 bytes from 64.29.17.193: icmp_seq=3 ttl=243 time=52.909 ms

— 64.29.17.193 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 47.651/52.999/55.783/3.294 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig trenna.co

; <<>> DiG 9.10.6 <<>> trenna.co
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54007
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;trenna.co.			IN	A

;; ANSWER SECTION:
trenna.co.		1799	IN	A	216.198.79.1

;; Query time: 474 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Jan 21 20:28:33 -03 2026
;; MSG SIZE  rcvd: 54

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig trenna.co via 8.8.8.8

; <<>> DiG 9.10.6 <<>> tre@8.8.8.8na.co @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32772
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;trenna.co.			IN	A

;; ANSWER SECTION:
trenna.co.		1799	IN	A	216.198.79.1

;; Query time: 500 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Jan 21 20:28:33 -03 2026
;; MSG SIZE  rcvd: 54

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig trenna.co via trace

; <<>> DiG 9.10.6 <<>> trenna.co +trace
;; global options: +cmd
;; Received 28 bytes from 8.8.8.8#53(8.8.8.8) in 99 ms

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Output of trenna.co

* Host trenna.co:443 was resolved.
* IPv6: (none)
* IPv4: 216.198.79.1
* Trying 216.198.79.1:443…
* connect to 216.198.79.1 port 443 from 192.168.2.100 port 52875 failed: Operation timed out
* Failed to connect to trenna.co port 443 after 75063 ms: Couldn’t connect to server
* Closing connection

└───────────────────────────────────────

┌───────────────────────────────────────
│ Time elapsed: 199 seconds
│
├─────── FINISHED
└───────────────────────────────────────
```

File can be found at /Users/ftocchetto/Documents/GitHub/saas-cb/vercel-debug.txt


system (@system) · 2026-01-21 · ♥ 1

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking [v0](https://v0.dev/).