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 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 often gives ERR_CONNECTION_TIMED_OUT or takes 60+ seconds to fail.
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/, 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:
12Domain to test (e.g. example.com):3┌───────────────────────────────────────4├─────── Fetching IP Addresses5│6│ 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.1937└───────────────────────────────────────89┌───────────────────────────────────────10├─────── STARTING11│12│ Domain to test: trenna.co13│ Timestamp (UTC): Wed Jan 21 23:26:30 UTC 202614│ Timestamp (Local): Wed Jan 21 20:26:30 -03 202615└───────────────────────────────────────1617┌───────────────────────────────────────18├─────── IP Information1920{21“ip”: “179.152.53.181”,22“hostname”: “b39835b5.virtua.com.br”,23“city”: “Porto Alegre”,24“region”: “Rio Grande do Sul”,25“country”: “BR”,26“loc”: “-30.0328,-51.2302”,27“org”: “AS28573 Claro NXT Telecomunicacoes Ltda”,28“postal”: “90000-000”,29“timezone”: “America/Sao_Paulo”,30“readme”: “https://ipinfo.io/missingauth”31}32└───────────────────────────────────────3334┌───────────────────────────────────────35├─────── Testing 216.198.79.136Checking headers via 216.198.79.13738* Connecting to hostname: 216.198.79.139* Trying 216.198.79.1:443…40* Connection timed out after 3004 milliseconds41* Closing connection4243Checking ping to 216.198.79.144PING 216.198.79.1 (216.198.79.1): 56 data bytes45Request timeout for icmp_seq 046Request timeout for icmp_seq 147Request timeout for icmp_seq 24849— 216.198.79.1 ping statistics —504 packets transmitted, 0 packets received, 100.0% packet loss5152Checking tracert to 216.198.79.1531 192.168.2.1 (192.168.2.1) 4.455 ms 2.791 ms 3.176 ms542 192.168.0.1 (192.168.0.1) 3.974 ms 4.385 ms 3.610 ms553 b3983401.virtua.com.br (179.152.52.1) 18.469 ms 19.036 ms 13.322 ms564 \* \* \*575 \* \* \*586 \* \* \*597 \* \* \*608 \* \* \*619 \* \* \*6210 \* \* \*6311 \* \* \*6412 \* \* \*6513 \* \* \*6614 \* \* \*6715 \* \* \*6816 \* \* \*6917 \* \* \*7018 \* \* \*7119 \* \* \*7220 \* \* \*7321 \* \* \*7422 \* \* \*7523 \* \* \*7624 \* \* \*7725 \* \* \*7826 \* \* \*7927 \* \* \*8028 \* \* \*8129 \* \* \*8230 \* \* \*83└───────────────────────────────────────8485┌───────────────────────────────────────86├─────── Testing 216.198.79.6587Checking headers via 216.198.79.658889* Connecting to hostname: 216.198.79.6590* Trying 216.198.79.65:443…91* Connected to 216.198.79.65 (216.198.79.65) port 44392* ALPN: curl offers h2,http/1.193* (304) (OUT), TLS handshake, Client hello (1):94 } \[314 bytes data\]95* (304) (IN), TLS handshake, Server hello (2):96 { \[122 bytes data\]97* (304) (IN), TLS handshake, Unknown (8):98 { \[15 bytes data\]99* (304) (IN), TLS handshake, Certificate (11):100 { \[2582 bytes data\]101* (304) (IN), TLS handshake, CERT verify (15):102 { \[264 bytes data\]103* (304) (IN), TLS handshake, Finished (20):104 { \[36 bytes data\]105* (304) (OUT), TLS handshake, Finished (20):106 } \[36 bytes data\]107* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF108* ALPN: server accepted h2109* Server certificate:110* subject: CN=trenna.co111* start date: Dec 18 14:45:39 2025 GMT112* expire date: Mar 18 14:45:38 2026 GMT113* issuer: C=US; O=Let’s Encrypt; CN=R12114* SSL certificate verify ok.115* using HTTP/2116* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/117* \[HTTP/2\] \[1\] \[:method: GET\]118* \[HTTP/2\] \[1\] \[:scheme: https\]119* \[HTTP/2\] \[1\] \[:authority: trenna.co\]120* \[HTTP/2\] \[1\] \[:path: /\]121* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]122* \[HTTP/2\] \[1\] \[accept: */*\]123124> GET / HTTP/2125> Host: trenna.co126> User-Agent: curl/8.7.1127> Accept: */*128129* Request completely sent off130 < HTTP/2 307131 < cache-control: public, max-age=0, must-revalidate132 < content-type: text/plain133 < date: Wed, 21 Jan 2026 23:28:10 GMT134 < location: https://www.trenna.co/135 < server: Vercel136 < strict-transport-security: max-age=63072000137 < x-vercel-id: gru1::cklmr-1769038090026-2645e6c429a5138 <139 { \[15 bytes data\]140* Connection #0 to host 216.198.79.65 left intact141142Checking ping to 216.198.79.65143PING 216.198.79.65 (216.198.79.65): 56 data bytes14464 bytes from 216.198.79.65: icmp_seq=0 ttl=243 time=44.373 ms14564 bytes from 216.198.79.65: icmp_seq=1 ttl=243 time=44.100 ms14664 bytes from 216.198.79.65: icmp_seq=2 ttl=243 time=45.611 ms14764 bytes from 216.198.79.65: icmp_seq=3 ttl=243 time=44.578 ms148149— 216.198.79.65 ping statistics —1504 packets transmitted, 4 packets received, 0.0% packet loss151round-trip min/avg/max/stddev = 44.100/44.666/45.611/0.572 ms152└───────────────────────────────────────153154┌───────────────────────────────────────155├─────── Testing 216.198.79.129156Checking headers via 216.198.79.129157158* Connecting to hostname: 216.198.79.129159* Trying 216.198.79.129:443…160* Connected to 216.198.79.129 (216.198.79.129) port 443161* ALPN: curl offers h2,http/1.1162* (304) (OUT), TLS handshake, Client hello (1):163 } \[314 bytes data\]164* (304) (IN), TLS handshake, Server hello (2):165 { \[122 bytes data\]166* (304) (IN), TLS handshake, Unknown (8):167 { \[15 bytes data\]168* (304) (IN), TLS handshake, Certificate (11):169 { \[2582 bytes data\]170* (304) (IN), TLS handshake, CERT verify (15):171 { \[264 bytes data\]172* (304) (IN), TLS handshake, Finished (20):173 { \[36 bytes data\]174* (304) (OUT), TLS handshake, Finished (20):175 } \[36 bytes data\]176* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF177* ALPN: server accepted h2178* Server certificate:179* subject: CN=trenna.co180* start date: Dec 18 14:45:39 2025 GMT181* expire date: Mar 18 14:45:38 2026 GMT182* issuer: C=US; O=Let’s Encrypt; CN=R12183* SSL certificate verify ok.184* using HTTP/2185* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/186* \[HTTP/2\] \[1\] \[:method: GET\]187* \[HTTP/2\] \[1\] \[:scheme: https\]188* \[HTTP/2\] \[1\] \[:authority: trenna.co\]189* \[HTTP/2\] \[1\] \[:path: /\]190* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]191* \[HTTP/2\] \[1\] \[accept: */*\]192193> GET / HTTP/2194> Host: trenna.co195> User-Agent: curl/8.7.1196> Accept: */*197198* Request completely sent off199 < HTTP/2 307200 < cache-control: public, max-age=0, must-revalidate201 < content-type: text/plain202 < date: Wed, 21 Jan 2026 23:28:13 GMT203 < location: https://www.trenna.co/204 < server: Vercel205 < strict-transport-security: max-age=63072000206 < x-vercel-id: gru1::vbhjb-1769038093309-8b9df01af79c207 <208 { \[15 bytes data\]209* Connection #0 to host 216.198.79.129 left intact210211Checking ping to 216.198.79.129212PING 216.198.79.129 (216.198.79.129): 56 data bytes21364 bytes from 216.198.79.129: icmp_seq=0 ttl=243 time=49.086 ms21464 bytes from 216.198.79.129: icmp_seq=1 ttl=243 time=65.509 ms21564 bytes from 216.198.79.129: icmp_seq=2 ttl=243 time=49.244 ms21664 bytes from 216.198.79.129: icmp_seq=3 ttl=243 time=45.415 ms217218— 216.198.79.129 ping statistics —2194 packets transmitted, 4 packets received, 0.0% packet loss220round-trip min/avg/max/stddev = 45.415/52.313/65.509/7.771 ms221└───────────────────────────────────────222223┌───────────────────────────────────────224├─────── Testing 216.198.79.193225Checking headers via 216.198.79.193226227* Connecting to hostname: 216.198.79.193228* Trying 216.198.79.193:443…229* Connected to 216.198.79.193 (216.198.79.193) port 443230* ALPN: curl offers h2,http/1.1231* (304) (OUT), TLS handshake, Client hello (1):232 } \[314 bytes data\]233* (304) (IN), TLS handshake, Server hello (2):234 { \[122 bytes data\]235* (304) (IN), TLS handshake, Unknown (8):236 { \[15 bytes data\]237* (304) (IN), TLS handshake, Certificate (11):238 { \[2582 bytes data\]239* (304) (IN), TLS handshake, CERT verify (15):240 { \[264 bytes data\]241* (304) (IN), TLS handshake, Finished (20):242 { \[36 bytes data\]243* (304) (OUT), TLS handshake, Finished (20):244 } \[36 bytes data\]245* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF246* ALPN: server accepted h2247* Server certificate:248* subject: CN=trenna.co249* start date: Dec 18 14:45:39 2025 GMT250* expire date: Mar 18 14:45:38 2026 GMT251* issuer: C=US; O=Let’s Encrypt; CN=R12252* SSL certificate verify ok.253* using HTTP/2254* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/255* \[HTTP/2\] \[1\] \[:method: GET\]256* \[HTTP/2\] \[1\] \[:scheme: https\]257* \[HTTP/2\] \[1\] \[:authority: trenna.co\]258* \[HTTP/2\] \[1\] \[:path: /\]259* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]260* \[HTTP/2\] \[1\] \[accept: */*\]261262> GET / HTTP/2263> Host: trenna.co264> User-Agent: curl/8.7.1265> Accept: */*266267* Request completely sent off268 < HTTP/2 307269 < cache-control: public, max-age=0, must-revalidate270 < content-type: text/plain271 < date: Wed, 21 Jan 2026 23:28:16 GMT272 < location: https://www.trenna.co/273 < server: Vercel274 < strict-transport-security: max-age=63072000275 < x-vercel-id: gru1::q6xx2-1769038096579-ad6ed3aa7338276 <277 { \[15 bytes data\]278* Connection #0 to host 216.198.79.193 left intact279280Checking ping to 216.198.79.193281PING 216.198.79.193 (216.198.79.193): 56 data bytes28264 bytes from 216.198.79.193: icmp_seq=0 ttl=243 time=50.723 ms28364 bytes from 216.198.79.193: icmp_seq=1 ttl=243 time=45.879 ms28464 bytes from 216.198.79.193: icmp_seq=2 ttl=243 time=54.966 ms28564 bytes from 216.198.79.193: icmp_seq=3 ttl=243 time=47.700 ms286287— 216.198.79.193 ping statistics —2884 packets transmitted, 4 packets received, 0.0% packet loss289round-trip min/avg/max/stddev = 45.879/49.817/54.966/3.440 ms290└───────────────────────────────────────291292┌───────────────────────────────────────293├─────── Testing 64.29.17.1294Checking headers via 64.29.17.1295296* Connecting to hostname: 64.29.17.1297* Trying 64.29.17.1:443…298* Connected to 64.29.17.1 (64.29.17.1) port 443299* ALPN: curl offers h2,http/1.1300* (304) (OUT), TLS handshake, Client hello (1):301 } \[314 bytes data\]302* (304) (IN), TLS handshake, Server hello (2):303 { \[122 bytes data\]304* (304) (IN), TLS handshake, Unknown (8):305 { \[15 bytes data\]306* (304) (IN), TLS handshake, Certificate (11):307 { \[2582 bytes data\]308* (304) (IN), TLS handshake, CERT verify (15):309 { \[264 bytes data\]310* (304) (IN), TLS handshake, Finished (20):311 { \[36 bytes data\]312* (304) (OUT), TLS handshake, Finished (20):313 } \[36 bytes data\]314* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF315* ALPN: server accepted h2316* Server certificate:317* subject: CN=trenna.co318* start date: Dec 18 14:45:39 2025 GMT319* expire date: Mar 18 14:45:38 2026 GMT320* issuer: C=US; O=Let’s Encrypt; CN=R12321* SSL certificate verify ok.322* using HTTP/2323* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/324* \[HTTP/2\] \[1\] \[:method: GET\]325* \[HTTP/2\] \[1\] \[:scheme: https\]326* \[HTTP/2\] \[1\] \[:authority: trenna.co\]327* \[HTTP/2\] \[1\] \[:path: /\]328* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]329* \[HTTP/2\] \[1\] \[accept: */*\]330331> GET / HTTP/2332> Host: trenna.co333> User-Agent: curl/8.7.1334> Accept: */*335336* Request completely sent off337 < HTTP/2 307338 < cache-control: public, max-age=0, must-revalidate339 < content-type: text/plain340 < date: Wed, 21 Jan 2026 23:28:19 GMT341 < location: https://www.trenna.co/342 < server: Vercel343 < strict-transport-security: max-age=63072000344 < x-vercel-id: gru1::mcbtr-1769038099871-84d49cfe386b345 <346 { \[15 bytes data\]347* Connection #0 to host 64.29.17.1 left intact348349Checking ping to 64.29.17.1350PING 64.29.17.1 (64.29.17.1): 56 data bytes35164 bytes from 64.29.17.1: icmp_seq=0 ttl=243 time=49.074 ms35264 bytes from 64.29.17.1: icmp_seq=1 ttl=243 time=45.828 ms35364 bytes from 64.29.17.1: icmp_seq=2 ttl=243 time=45.377 ms35464 bytes from 64.29.17.1: icmp_seq=3 ttl=243 time=46.366 ms355356— 64.29.17.1 ping statistics —3574 packets transmitted, 4 packets received, 0.0% packet loss358round-trip min/avg/max/stddev = 45.377/46.661/49.074/1.436 ms359└───────────────────────────────────────360361┌───────────────────────────────────────362├─────── Testing 64.29.17.65363Checking headers via 64.29.17.65364365* Connecting to hostname: 64.29.17.65366* Trying 64.29.17.65:443…367* Connected to 64.29.17.65 (64.29.17.65) port 443368* ALPN: curl offers h2,http/1.1369* (304) (OUT), TLS handshake, Client hello (1):370 } \[314 bytes data\]371* (304) (IN), TLS handshake, Server hello (2):372 { \[122 bytes data\]373* (304) (IN), TLS handshake, Unknown (8):374 { \[15 bytes data\]375* (304) (IN), TLS handshake, Certificate (11):376 { \[2582 bytes data\]377* (304) (IN), TLS handshake, CERT verify (15):378 { \[264 bytes data\]379* (304) (IN), TLS handshake, Finished (20):380 { \[36 bytes data\]381* (304) (OUT), TLS handshake, Finished (20):382 } \[36 bytes data\]383* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF384* ALPN: server accepted h2385* Server certificate:386* subject: CN=trenna.co387* start date: Dec 18 14:45:39 2025 GMT388* expire date: Mar 18 14:45:38 2026 GMT389* issuer: C=US; O=Let’s Encrypt; CN=R12390* SSL certificate verify ok.391* using HTTP/2392* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/393* \[HTTP/2\] \[1\] \[:method: GET\]394* \[HTTP/2\] \[1\] \[:scheme: https\]395* \[HTTP/2\] \[1\] \[:authority: trenna.co\]396* \[HTTP/2\] \[1\] \[:path: /\]397* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]398* \[HTTP/2\] \[1\] \[accept: */*\]399400> GET / HTTP/2401> Host: trenna.co402> User-Agent: curl/8.7.1403> Accept: */*404405* Request completely sent off406 < HTTP/2 307407 < cache-control: public, max-age=0, must-revalidate408 < content-type: text/plain409 < date: Wed, 21 Jan 2026 23:28:23 GMT410 < location: https://www.trenna.co/411 < server: Vercel412 < strict-transport-security: max-age=63072000413 < x-vercel-id: gru1::zp695-1769038103149-14272d0cf0d9414 <415 { \[15 bytes data\]416* Connection #0 to host 64.29.17.65 left intact417418Checking ping to 64.29.17.65419PING 64.29.17.65 (64.29.17.65): 56 data bytes42064 bytes from 64.29.17.65: icmp_seq=0 ttl=243 time=46.404 ms42164 bytes from 64.29.17.65: icmp_seq=1 ttl=243 time=53.850 ms42264 bytes from 64.29.17.65: icmp_seq=2 ttl=243 time=62.024 ms42364 bytes from 64.29.17.65: icmp_seq=3 ttl=243 time=59.194 ms424425— 64.29.17.65 ping statistics —4264 packets transmitted, 4 packets received, 0.0% packet loss427round-trip min/avg/max/stddev = 46.404/55.368/62.024/5.950 ms428└───────────────────────────────────────429430┌───────────────────────────────────────431├─────── Testing 64.29.17.129432Checking headers via 64.29.17.129433434* Connecting to hostname: 64.29.17.129435* Trying 64.29.17.129:443…436* Connected to 64.29.17.129 (64.29.17.129) port 443437* ALPN: curl offers h2,http/1.1438* (304) (OUT), TLS handshake, Client hello (1):439 } \[314 bytes data\]440* (304) (IN), TLS handshake, Server hello (2):441 { \[122 bytes data\]442* (304) (IN), TLS handshake, Unknown (8):443 { \[15 bytes data\]444* (304) (IN), TLS handshake, Certificate (11):445 { \[2582 bytes data\]446* (304) (IN), TLS handshake, CERT verify (15):447 { \[264 bytes data\]448* (304) (IN), TLS handshake, Finished (20):449 { \[36 bytes data\]450* (304) (OUT), TLS handshake, Finished (20):451 } \[36 bytes data\]452* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF453* ALPN: server accepted h2454* Server certificate:455* subject: CN=trenna.co456* start date: Dec 18 14:45:39 2025 GMT457* expire date: Mar 18 14:45:38 2026 GMT458* issuer: C=US; O=Let’s Encrypt; CN=R12459* SSL certificate verify ok.460* using HTTP/2461* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/462* \[HTTP/2\] \[1\] \[:method: GET\]463* \[HTTP/2\] \[1\] \[:scheme: https\]464* \[HTTP/2\] \[1\] \[:authority: trenna.co\]465* \[HTTP/2\] \[1\] \[:path: /\]466* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]467* \[HTTP/2\] \[1\] \[accept: */*\]468469> GET / HTTP/2470> Host: trenna.co471> User-Agent: curl/8.7.1472> Accept: */*473474* Request completely sent off475 < HTTP/2 307476 < cache-control: public, max-age=0, must-revalidate477 < content-type: text/plain478 < date: Wed, 21 Jan 2026 23:28:26 GMT479 < location: https://www.trenna.co/480 < server: Vercel481 < strict-transport-security: max-age=63072000482 < x-vercel-id: gru1::hkq45-1769038106443-4e34d4128704483 <484 { \[15 bytes data\]485* Connection #0 to host 64.29.17.129 left intact486487Checking ping to 64.29.17.129488PING 64.29.17.129 (64.29.17.129): 56 data bytes48964 bytes from 64.29.17.129: icmp_seq=0 ttl=243 time=43.060 ms49064 bytes from 64.29.17.129: icmp_seq=1 ttl=243 time=49.917 ms49164 bytes from 64.29.17.129: icmp_seq=2 ttl=243 time=47.891 ms49264 bytes from 64.29.17.129: icmp_seq=3 ttl=243 time=42.941 ms493494— 64.29.17.129 ping statistics —4954 packets transmitted, 4 packets received, 0.0% packet loss496round-trip min/avg/max/stddev = 42.941/45.952/49.917/3.038 ms497└───────────────────────────────────────498499┌───────────────────────────────────────500├─────── Testing 64.29.17.193501Checking headers via 64.29.17.193502503* Connecting to hostname: 64.29.17.193504* Trying 64.29.17.193:443…505* Connected to 64.29.17.193 (64.29.17.193) port 443506* ALPN: curl offers h2,http/1.1507* (304) (OUT), TLS handshake, Client hello (1):508 } \[314 bytes data\]509* (304) (IN), TLS handshake, Server hello (2):510 { \[122 bytes data\]511* (304) (IN), TLS handshake, Unknown (8):512 { \[15 bytes data\]513* (304) (IN), TLS handshake, Certificate (11):514 { \[2582 bytes data\]515* (304) (IN), TLS handshake, CERT verify (15):516 { \[264 bytes data\]517* (304) (IN), TLS handshake, Finished (20):518 { \[36 bytes data\]519* (304) (OUT), TLS handshake, Finished (20):520 } \[36 bytes data\]521* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / \[blank\] / UNDEF522* ALPN: server accepted h2523* Server certificate:524* subject: CN=trenna.co525* start date: Dec 18 14:45:39 2025 GMT526* expire date: Mar 18 14:45:38 2026 GMT527* issuer: C=US; O=Let’s Encrypt; CN=R12528* SSL certificate verify ok.529* using HTTP/2530* \[HTTP/2\] \[1\] OPENED stream for https://trenna.co/531* \[HTTP/2\] \[1\] \[:method: GET\]532* \[HTTP/2\] \[1\] \[:scheme: https\]533* \[HTTP/2\] \[1\] \[:authority: trenna.co\]534* \[HTTP/2\] \[1\] \[:path: /\]535* \[HTTP/2\] \[1\] \[user-agent: curl/8.7.1\]536* \[HTTP/2\] \[1\] \[accept: */*\]537538> GET / HTTP/2539> Host: trenna.co540> User-Agent: curl/8.7.1541> Accept: */*542543* Request completely sent off544 < HTTP/2 307545 < cache-control: public, max-age=0, must-revalidate546 < content-type: text/plain547 < date: Wed, 21 Jan 2026 23:28:29 GMT548 < location: https://www.trenna.co/549 < server: Vercel550 < strict-transport-security: max-age=63072000551 < x-vercel-id: gru1::xznqg-1769038109737-c96f2a31e405552 <553 { \[15 bytes data\]554* Connection #0 to host 64.29.17.193 left intact555556Checking ping to 64.29.17.193557PING 64.29.17.193 (64.29.17.193): 56 data bytes55864 bytes from 64.29.17.193: icmp_seq=0 ttl=243 time=47.651 ms55964 bytes from 64.29.17.193: icmp_seq=1 ttl=243 time=55.653 ms56064 bytes from 64.29.17.193: icmp_seq=2 ttl=243 time=55.783 ms56164 bytes from 64.29.17.193: icmp_seq=3 ttl=243 time=52.909 ms562563— 64.29.17.193 ping statistics —5644 packets transmitted, 4 packets received, 0.0% packet loss565round-trip min/avg/max/stddev = 47.651/52.999/55.783/3.294 ms566└───────────────────────────────────────567568┌───────────────────────────────────────569├─────── dig trenna.co570571; <<>> DiG 9.10.6 <<>> trenna.co572;; global options: +cmd573;; Got answer:574;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54007575;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1576577;; OPT PSEUDOSECTION:578; EDNS: version: 0, flags:; udp: 512579;; QUESTION SECTION:580;trenna.co. IN A581582;; ANSWER SECTION:583trenna.co. 1799 IN A 216.198.79.1584585;; Query time: 474 msec586;; SERVER: 8.8.8.8#53(8.8.8.8)587;; WHEN: Wed Jan 21 20:28:33 -03 2026588;; MSG SIZE rcvd: 54589590└───────────────────────────────────────591592┌───────────────────────────────────────593├─────── dig trenna.co via 8.8.8.8594595; <<>> DiG 9.10.6 <<>> tre@8.8.8.8na.co @8.8.8.8596;; global options: +cmd597;; Got answer:598;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32772599;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1600601;; OPT PSEUDOSECTION:602; EDNS: version: 0, flags:; udp: 512603;; QUESTION SECTION:604;trenna.co. IN A605606;; ANSWER SECTION:607trenna.co. 1799 IN A 216.198.79.1608609;; Query time: 500 msec610;; SERVER: 8.8.8.8#53(8.8.8.8)611;; WHEN: Wed Jan 21 20:28:33 -03 2026612;; MSG SIZE rcvd: 54613614└───────────────────────────────────────615616┌───────────────────────────────────────617├─────── dig trenna.co via trace618619; <<>> DiG 9.10.6 <<>> trenna.co +trace620;; global options: +cmd621;; Received 28 bytes from 8.8.8.8#53(8.8.8.8) in 99 ms622623└───────────────────────────────────────624625┌───────────────────────────────────────626├─────── Output of trenna.co627628* Host trenna.co:443 was resolved.629* IPv6: (none)630* IPv4: 216.198.79.1631* Trying 216.198.79.1:443…632* connect to 216.198.79.1 port 443 from 192.168.2.100 port 52875 failed: Operation timed out633* Failed to connect to trenna.co port 443 after 75063 ms: Couldn’t connect to server634* Closing connection635636└───────────────────────────────────────637638┌───────────────────────────────────────639│ Time elapsed: 199 seconds640│641├─────── FINISHED642└───────────────────────────────────────File can be found at /Users/ftocchetto/Documents/GitHub/saas-cb/vercel-debug.txt