Partial Vercel Edge IP Unreachable from Brazilian ISPs (216.198.79.1)

Discussions
,
1

Summary

I’m experiencing intermittent connectivity issues to my Vercel-hosted site (recuida.com) from Brazil. After running diagnostics, I discovered that one of Vercel’s edge IPs is completely unreachable from at least two different Brazilian ISPs, while others work normally.

The Problem

When DNS resolves my domain to 216.198.79.1, the site becomes completely inaccessible:

  • HTTPS connection times out
  • Ping shows 100% packet loss

However, when DNS resolves to other Vercel IPs (like 216.198.79.65, 64.29.17.1), everything works perfectly with low latency (~5ms).

Test Results Summary

Vercel IP HTTPS Ping
216.198.79.1 :cross_mark: Timeout :cross_mark: 100% loss
216.198.79.65 :white_check_mark: HTTP 200 :white_check_mark: 0% loss
216.198.79.129 :white_check_mark: HTTP 200 :warning: 25% loss
216.198.79.193 :white_check_mark: HTTP 200 :warning: 25% loss
64.29.17.1 :white_check_mark: HTTP 200 :white_check_mark: 0% loss

Environment

Location: São Paulo, Brazil
ISPs tested: 2 different providers (including AS52839 - RSS SOCIEDADE CIVIL LTDA)
Domain: recuida.com
Vercel region: GRU (São Paulo) - confirmed via x-vercel-id header

What I’ve Tried

Tested from two different ISPs/networks — same result
Ran Vercel’s official debug script
Confirmed working IPs respond correctly with valid TLS and HTTP 200

Questions for the Community

  • Has anyone else in Brazil experienced similar issues with specific Vercel edge IPs being unreachable?
  • Is there a way to exclude a problematic IP from DNS resolution for my domain?
  • Could this be related to upstream routing issues with Brazilian carriers?

Additional Notes

I’ve reviewed Vercel’s troubleshooting connectivity guide. Since the issue affects a specific IP across multiple ISPs, it seems like it could be a routing problem at an intermediate network level rather than a single ISP block.

Any insights or similar experiences would be appreciated!

2

Additionally, here is the output of vercel-debug.txt for one of the tests:

Domain to test (e.g. example.com):
┌───────────────────────────────────────
├─────── Fetching IP Addresses
│
│ recuida.com 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: recuida.com
│ Timestamp (UTC): Thu Apr 30 00:58:27 UTC 2026
│ Timestamp (Local): Wed Apr 29 21:58:27 -03 2026
└───────────────────────────────────────

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

{
“ip”: “177.52.235.14”,
“hostname”: “static-177-52-235-14.rssmultimidia.com.br”,
“city”: “São Paulo”,
“region”: “São Paulo”,
“country”: “BR”,
“loc”: “-23.5475,-46.6361”,
“org”: “AS52839 RSS SOCIEDADE CIVIL LTDA”,
“postal”: “01000-000”,
“timezone”: “America/Sao_Paulo”,
“readme”: “IP Address data API | IPinfo.io”
}
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── 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 3000 milliseconds
  • Closing connection

Checking ping to 216.198.79.1
PING 216.198.79.1 (216.198.79.1) 56(84) bytes of data.

-– 216.198.79.1 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3065ms

Checking tracert to 216.198.79.1
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── 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
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [19 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [2573 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [36 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [36 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=recuida.com
  • start date: Apr 15 23:05:04 2026 GMT
  • expire date: Jul 14 23:05:03 2026 GMT
  • issuer: C=US; O=Let’s Encrypt; CN=R13
  • SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
  • Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
  • Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [122 bytes data]
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://recuida.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: recuida.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.5.0]
  • [HTTP/2] [1] [accept: /]
    } [5 bytes data]

GET / HTTP/2
Host: recuida.com
User-Agent: curl/8.5.0
Accept: /

{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< access-control-allow-origin: *
< age: 204279
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline
< content-type: text/html; charset=utf-8
< date: Thu, 30 Apr 2026 00:58:44 GMT
< etag: “be42f8a10d39b47e381768dc2cdf8eef”
< server: Vercel
< strict-transport-security: max-age=63072000
< vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
< x-matched-path: /
< x-nextjs-prerender: 1
< x-nextjs-stale-time: 300
< x-vercel-cache: HIT
< x-vercel-id: gru1::2pt9x-1777510724034-3ad9dd5de99e
< content-length: 94910
<
{ [3148 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(84) bytes of data.
64 bytes from 216.198.79.65: icmp_seq=1 ttl=246 time=6.41 ms
64 bytes from 216.198.79.65: icmp_seq=2 ttl=246 time=5.35 ms
64 bytes from 216.198.79.65: icmp_seq=3 ttl=246 time=5.27 ms
64 bytes from 216.198.79.65: icmp_seq=4 ttl=246 time=4.87 ms

-– 216.198.79.65 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3031ms
rtt min/avg/max/mdev = 4.866/5.473/6.410/0.570 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
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [19 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [2573 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [36 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [36 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=recuida.com
  • start date: Apr 15 23:05:04 2026 GMT
  • expire date: Jul 14 23:05:03 2026 GMT
  • issuer: C=US; O=Let’s Encrypt; CN=R13
  • SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
  • Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
  • Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [122 bytes data]
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://recuida.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: recuida.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.5.0]
  • [HTTP/2] [1] [accept: /]
    } [5 bytes data]

GET / HTTP/2
Host: recuida.com
User-Agent: curl/8.5.0
Accept: /

{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< access-control-allow-origin: *
< age: 204283
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline
< content-type: text/html; charset=utf-8
< date: Thu, 30 Apr 2026 00:58:47 GMT
< etag: “be42f8a10d39b47e381768dc2cdf8eef”
< server: Vercel
< strict-transport-security: max-age=63072000
< vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
< x-matched-path: /
< x-nextjs-prerender: 1
< x-nextjs-stale-time: 300
< x-vercel-cache: HIT
< x-vercel-id: gru1::xsplv-1777510727578-93e8d844e875
< content-length: 94910
<
{ [5 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(84) bytes of data.
64 bytes from 216.198.79.129: icmp_seq=1 ttl=246 time=5.31 ms
64 bytes from 216.198.79.129: icmp_seq=3 ttl=246 time=5.02 ms
64 bytes from 216.198.79.129: icmp_seq=4 ttl=246 time=5.42 ms

-– 216.198.79.129 ping statistics —
4 packets transmitted, 3 received, 25% packet loss, time 3019ms
rtt min/avg/max/mdev = 5.021/5.247/5.416/0.166 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
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [19 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [2573 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [36 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [36 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=recuida.com
  • start date: Apr 15 23:05:04 2026 GMT
  • expire date: Jul 14 23:05:03 2026 GMT
  • issuer: C=US; O=Let’s Encrypt; CN=R13
  • SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
  • Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
  • Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [122 bytes data]
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://recuida.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: recuida.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.5.0]
  • [HTTP/2] [1] [accept: /]
    } [5 bytes data]

GET / HTTP/2
Host: recuida.com
User-Agent: curl/8.5.0
Accept: /

{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< access-control-allow-origin: *
< age: 204287
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline
< content-type: text/html; charset=utf-8
< date: Thu, 30 Apr 2026 00:58:51 GMT
< etag: “be42f8a10d39b47e381768dc2cdf8eef”
< server: Vercel
< strict-transport-security: max-age=63072000
< vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
< x-matched-path: /
< x-nextjs-prerender: 1
< x-nextjs-stale-time: 300
< x-vercel-cache: HIT
< x-vercel-id: gru1::h8mcx-1777510731715-7973e3ec1acc
< content-length: 94910
<
{ [5 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(84) bytes of data.
64 bytes from 216.198.79.193: icmp_seq=1 ttl=246 time=7.58 ms
64 bytes from 216.198.79.193: icmp_seq=3 ttl=246 time=6.46 ms
64 bytes from 216.198.79.193: icmp_seq=4 ttl=246 time=6.13 ms

-– 216.198.79.193 ping statistics —
4 packets transmitted, 3 received, 25% packet loss, time 3033ms
rtt min/avg/max/mdev = 6.125/6.722/7.583/0.623 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
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [19 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [2573 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [36 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [36 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=recuida.com
  • start date: Apr 15 23:05:04 2026 GMT
  • expire date: Jul 14 23:05:03 2026 GMT
  • issuer: C=US; O=Let’s Encrypt; CN=R13
  • SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
  • Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
  • Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [122 bytes data]
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://recuida.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: recuida.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.5.0]
  • [HTTP/2] [1] [accept: /]
    } [5 bytes data]

GET / HTTP/2
Host: recuida.com
User-Agent: curl/8.5.0
Accept: /

{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< access-control-allow-origin: *
< age: 204291
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline
< content-type: text/html; charset=utf-8
< date: Thu, 30 Apr 2026 00:58:55 GMT
< etag: “be42f8a10d39b47e381768dc2cdf8eef”
< server: Vercel
< strict-transport-security: max-age=63072000
< vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
< x-matched-path: /
< x-nextjs-prerender: 1
< x-nextjs-stale-time: 300
< x-vercel-cache: HIT
< x-vercel-id: gru1::n9774-1777510735841-eff052833297
< content-length: 94910
<
{ [3146 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(84) bytes of data.
64 bytes from 64.29.17.1: icmp_seq=1 ttl=246 time=5.43 ms
64 bytes from 64.29.17.1: icmp_seq=2 ttl=246 time=9.98 ms
64 bytes from 64.29.17.1: icmp_seq=3 ttl=246 time=5.18 ms
64 bytes from 64.29.17.1: icmp_seq=4 ttl=246 time=4.98 ms

-– 64.29.17.1 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 4.980/6.391/9.976/2.075 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
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [19 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [2573 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [36 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [36 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=recuida.com
  • start date: Apr 15 23:05:04 2026 GMT
  • expire date: Jul 14 23:05:03 2026 GMT
  • issuer: C=US; O=Let’s Encrypt; CN=R13
  • SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
  • Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
  • Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [122 bytes data]
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://recuida.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: recuida.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.5.0]
  • [HTTP/2] [1] [accept: /]
    } [5 bytes data]

GET / HTTP/2
Host: recuida.com
User-Agent: curl/8.5.0
Accept: /

{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< access-control-allow-origin: *
< age: 204294
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline
< content-type: text/html; charset=utf-8
< date: Thu, 30 Apr 2026 00:58:59 GMT
< etag: “be42f8a10d39b47e381768dc2cdf8eef”
< server: Vercel
< strict-transport-security: max-age=63072000
< vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
< x-matched-path: /
< x-nextjs-prerender: 1
< x-nextjs-stale-time: 300
< x-vercel-cache: HIT
< x-vercel-id: gru1::274s5-1777510739192-2c56fe4f2da4
< content-length: 94910
<
{ [1 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(84) bytes of data.
64 bytes from 64.29.17.65: icmp_seq=1 ttl=246 time=6.10 ms
64 bytes from 64.29.17.65: icmp_seq=2 ttl=246 time=4.72 ms
64 bytes from 64.29.17.65: icmp_seq=3 ttl=246 time=4.78 ms
64 bytes from 64.29.17.65: icmp_seq=4 ttl=246 time=5.39 ms

-– 64.29.17.65 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 4.724/5.248/6.102/0.558 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
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [19 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [2573 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [36 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [36 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=recuida.com
  • start date: Apr 15 23:05:04 2026 GMT
  • expire date: Jul 14 23:05:03 2026 GMT
  • issuer: C=US; O=Let’s Encrypt; CN=R13
  • SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
  • Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
  • Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [122 bytes data]
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://recuida.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: recuida.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.5.0]
  • [HTTP/2] [1] [accept: /]
    } [5 bytes data]

GET / HTTP/2
Host: recuida.com
User-Agent: curl/8.5.0
Accept: /

{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< access-control-allow-origin: *
< age: 204298
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline
< content-type: text/html; charset=utf-8
< date: Thu, 30 Apr 2026 00:59:02 GMT
< etag: “be42f8a10d39b47e381768dc2cdf8eef”
< server: Vercel
< strict-transport-security: max-age=63072000
< vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
< x-matched-path: /
< x-nextjs-prerender: 1
< x-nextjs-stale-time: 300
< x-vercel-cache: HIT
< x-vercel-id: gru1::cmffc-1777510742563-b2b2fc30cad8
< content-length: 94910
<
{ [5 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(84) bytes of data.
64 bytes from 64.29.17.129: icmp_seq=1 ttl=246 time=6.71 ms
64 bytes from 64.29.17.129: icmp_seq=2 ttl=246 time=4.76 ms
64 bytes from 64.29.17.129: icmp_seq=3 ttl=246 time=4.79 ms

-– 64.29.17.129 ping statistics —
4 packets transmitted, 3 received, 25% packet loss, time 2997ms
rtt min/avg/max/mdev = 4.759/5.419/6.712/0.914 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
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [19 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [2573 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [36 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [36 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=recuida.com
  • start date: Apr 15 23:05:04 2026 GMT
  • expire date: Jul 14 23:05:03 2026 GMT
  • issuer: C=US; O=Let’s Encrypt; CN=R13
  • SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
  • Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
  • Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [122 bytes data]
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://recuida.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: recuida.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.5.0]
  • [HTTP/2] [1] [accept: /]
    } [5 bytes data]

GET / HTTP/2
Host: recuida.com
User-Agent: curl/8.5.0
Accept: /

{ [5 bytes data]
< HTTP/2 200
< accept-ranges: bytes
< access-control-allow-origin: *
< age: 204302
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline
< content-type: text/html; charset=utf-8
< date: Thu, 30 Apr 2026 00:59:06 GMT
< etag: “be42f8a10d39b47e381768dc2cdf8eef”
< server: Vercel
< strict-transport-security: max-age=63072000
< vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
< x-matched-path: /
< x-nextjs-prerender: 1
< x-nextjs-stale-time: 300
< x-vercel-cache: HIT
< x-vercel-id: gru1::m8xqn-1777510746663-c50997431ede
< content-length: 94910
<
{ [5 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(84) bytes of data.
64 bytes from 64.29.17.193: icmp_seq=1 ttl=246 time=5.49 ms
64 bytes from 64.29.17.193: icmp_seq=2 ttl=246 time=5.12 ms
64 bytes from 64.29.17.193: icmp_seq=3 ttl=246 time=4.72 ms
64 bytes from 64.29.17.193: icmp_seq=4 ttl=246 time=6.54 ms

-– 64.29.17.193 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 4.718/5.467/6.543/0.678 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig recuida.com

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

┌───────────────────────────────────────
├─────── dig recuida.com via 8.8.8.8

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

┌───────────────────────────────────────
├─────── dig recuida.com via trace

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

┌───────────────────────────────────────
├─────── Output of recuida.com

  • Host recuida.com: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 172.23.46.2 port 37100 failed: Connection timed out
  • Failed to connect to recuida.com port 443 after 134850 ms: Couldn’t connect to server
  • Closing connection

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

┌───────────────────────────────────────
│ Time elapsed: 177 seconds
│
├─────── FINISHED
└───────────────────────────────────────