DEPLOYMENT_NOT_FOUND despite READY deployment with alias assigned

caiocad-4192 · April 29, 2026, 12:26am

he Vercel AI diagnosed this as a potential internal routing issue between my domain and deployment, an infrastructure-level problem. My domain www.trabalheila.com.br is now working for me, but the Vercel system still reports DEPLOYMENT_NOT_FOUND. I have attached the full debug script output as requested."

±--------------------------------------
±------ Fetching IP Addresses
|
| www.trabalheila.com.br 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: www.trabalheila.com.br
| Timestamp (UTC): 04/29/2026 00:09:53
| Timestamp (Local): 04/28/2026 21:09:53
±--------------------------------------

±--------------------------------------
±------ IP Information

{
“ip”: “187.55.195.147”,
“hostname”: “187-55-195-147.user3p.v-tal.net.br”,
“city”: “Porto Alegre”,
“region”: “Rio Grande do Sul”,
“country”: “BR”,
“loc”: “-30.0328,-51.2302”,
“org”: “AS8167 V tal”,
“postal”: “90000-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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 216.198.79.1 (216.198.79.1) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7275

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:09:53 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::l6m7v-1777421393669-18ad30f4c682

<

{ [1552 bytes data]

Connection #0 to host 216.198.79.1 left intact

Checking ping to 216.198.79.1

Disparando 216.198.79.1 com 32 bytes de dados:
Resposta de 216.198.79.1: bytes=32 tempo=21ms TTL=246
Resposta de 216.198.79.1: bytes=32 tempo=21ms TTL=246
Resposta de 216.198.79.1: bytes=32 tempo=20ms TTL=246
Resposta de 216.198.79.1: bytes=32 tempo=20ms TTL=246

Estatísticas do Ping para 216.198.79.1:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 20ms, Máximo = 21ms, Média = 20ms
±--------------------------------------

±--------------------------------------
±------ 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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 216.198.79.65 (216.198.79.65) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7279

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:09:57 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::n5fs5-1777421397069-1d014470748f

<

{ [1552 bytes data]

Connection #0 to host 216.198.79.65 left intact

Checking ping to 216.198.79.65

Disparando 216.198.79.65 com 32 bytes de dados:
Resposta de 216.198.79.65: bytes=32 tempo=19ms TTL=246
Resposta de 216.198.79.65: bytes=32 tempo=18ms TTL=246
Resposta de 216.198.79.65: bytes=32 tempo=20ms TTL=246
Resposta de 216.198.79.65: bytes=32 tempo=18ms TTL=246

Estatísticas do Ping para 216.198.79.65:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 18ms, Máximo = 20ms, Média = 18ms
±--------------------------------------

±--------------------------------------
±------ 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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 216.198.79.129 (216.198.79.129) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7282

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:10:00 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::hmh69-1777421400430-973ede83d66f

<

{ [1552 bytes data]

Connection #0 to host 216.198.79.129 left intact

Checking ping to 216.198.79.129

Disparando 216.198.79.129 com 32 bytes de dados:
Resposta de 216.198.79.129: bytes=32 tempo=22ms TTL=246
Resposta de 216.198.79.129: bytes=32 tempo=23ms TTL=246
Resposta de 216.198.79.129: bytes=32 tempo=22ms TTL=246
Resposta de 216.198.79.129: bytes=32 tempo=22ms TTL=246

Estatísticas do Ping para 216.198.79.129:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 22ms, Máximo = 23ms, Média = 22ms
±--------------------------------------

±--------------------------------------
±------ 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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 216.198.79.193 (216.198.79.193) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7285

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:10:03 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::fl852-1777421403788-8eebdf03617a

<

{ [1552 bytes data]

Connection #0 to host 216.198.79.193 left intact

Checking ping to 216.198.79.193

Disparando 216.198.79.193 com 32 bytes de dados:
Resposta de 216.198.79.193: bytes=32 tempo=22ms TTL=246
Resposta de 216.198.79.193: bytes=32 tempo=29ms TTL=246
Resposta de 216.198.79.193: bytes=32 tempo=21ms TTL=246
Resposta de 216.198.79.193: bytes=32 tempo=21ms TTL=246

Estatísticas do Ping para 216.198.79.193:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 21ms, Máximo = 29ms, Média = 23ms
±--------------------------------------

±--------------------------------------
±------ 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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 64.29.17.1 (64.29.17.1) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7289

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:10:07 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::hm6rd-1777421407115-e8c70ad70541

<

{ [1552 bytes data]

Connection #0 to host 64.29.17.1 left intact

Checking ping to 64.29.17.1

Disparando 64.29.17.1 com 32 bytes de dados:
Resposta de 64.29.17.1: bytes=32 tempo=19ms TTL=246
Resposta de 64.29.17.1: bytes=32 tempo=29ms TTL=246
Resposta de 64.29.17.1: bytes=32 tempo=31ms TTL=246
Resposta de 64.29.17.1: bytes=32 tempo=20ms TTL=246

Estatísticas do Ping para 64.29.17.1:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 19ms, Máximo = 31ms, Média = 24ms
±--------------------------------------

±--------------------------------------
±------ 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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 64.29.17.65 (64.29.17.65) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7292

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:10:10 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::8xsmg-1777421410749-a83f2aaf93aa

<

{ [1552 bytes data]

Connection #0 to host 64.29.17.65 left intact

Checking ping to 64.29.17.65

Disparando 64.29.17.65 com 32 bytes de dados:
Resposta de 64.29.17.65: bytes=32 tempo=22ms TTL=246
Resposta de 64.29.17.65: bytes=32 tempo=21ms TTL=246
Resposta de 64.29.17.65: bytes=32 tempo=21ms TTL=246
Resposta de 64.29.17.65: bytes=32 tempo=20ms TTL=246

Estatísticas do Ping para 64.29.17.65:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 20ms, Máximo = 22ms, Média = 21ms
±--------------------------------------

±--------------------------------------
±------ 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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 64.29.17.129 (64.29.17.129) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7296

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:10:14 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::x67vj-1777421414138-6881a8ba85d5

<

{ [1552 bytes data]

Connection #0 to host 64.29.17.129 left intact

Checking ping to 64.29.17.129

Disparando 64.29.17.129 com 32 bytes de dados:
Resposta de 64.29.17.129: bytes=32 tempo=18ms TTL=246
Resposta de 64.29.17.129: bytes=32 tempo=19ms TTL=246
Resposta de 64.29.17.129: bytes=32 tempo=18ms TTL=246
Resposta de 64.29.17.129: bytes=32 tempo=18ms TTL=246

Estatísticas do Ping para 64.29.17.129:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 18ms, Máximo = 19ms, Média = 18ms
±--------------------------------------

±--------------------------------------
±------ 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…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to 64.29.17.193 (64.29.17.193) port 443
using HTTP/1.x

GET / HTTP/1.1

Host: www.trabalheila.com.br

User-Agent: curl/8.13.0

Accept: /

Request completely sent off
< HTTP/1.1 200 OK

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

< Age: 7299

< Cache-Control: public, max-age=0, must-revalidate

< Content-Disposition: inline

< Content-Length: 1552

< Content-Type: text/html; charset=utf-8

< Date: Wed, 29 Apr 2026 00:10:17 GMT

< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”

< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT

< Server: Vercel

< Strict-Transport-Security: max-age=63072000

< X-Vercel-Cache: HIT

< X-Vercel-Id: gru1::4q9q5-1777421417566-720e7ae0c418

<

{ [1552 bytes data]

Connection #0 to host 64.29.17.193 left intact

Checking ping to 64.29.17.193

Disparando 64.29.17.193 com 32 bytes de dados:
Resposta de 64.29.17.193: bytes=32 tempo=20ms TTL=246
Resposta de 64.29.17.193: bytes=32 tempo=20ms TTL=246
Resposta de 64.29.17.193: bytes=32 tempo=20ms TTL=246
Resposta de 64.29.17.193: bytes=32 tempo=20ms TTL=246

Estatísticas do Ping para 64.29.17.193:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 20ms, Máximo = 20ms, Média = 20ms
±--------------------------------------

±--------------------------------------
±------ nslookup debug www.trabalheila.com.br

Não é resposta autoritativa:

Got answer:
HEADER:
opcode = QUERY, id = 1, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0

QUESTIONS:
    1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa, type = PTR, class = IN
AUTHORITY RECORDS:
->  ip6.arpa
    ttl = 260 (4 mins 20 secs)
    primary name server = b.ip6-servers.arpa
    responsible mail addr = nstld.iana.org
    serial  = 2026022245
    refresh = 1800 (30 mins)
    retry   = 900 (15 mins)
    expire  = 604800 (7 days)
    default TTL = 3600 (1 hour)

Servidor: UnKnown
Address: fe80::1

Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 3, authority records = 0, additional = 0

QUESTIONS:
    www.trabalheila.com.br, type = A, class = IN
ANSWERS:
->  www.trabalheila.com.br
    canonical name = 2c27b3c62dd43e9b.vercel-dns-017.com
    ttl = 403 (6 mins 43 secs)
->  2c27b3c62dd43e9b.vercel-dns-017.com
    internet address = 216.198.79.1
    ttl = 300 (5 mins)
->  2c27b3c62dd43e9b.vercel-dns-017.com
    internet address = 64.29.17.1
    ttl = 300 (5 mins)

Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 1, additional = 0

QUESTIONS:
    www.trabalheila.com.br, type = AAAA, class = IN
ANSWERS:
->  www.trabalheila.com.br
    canonical name = 2c27b3c62dd43e9b.vercel-dns-017.com
    ttl = 403 (6 mins 43 secs)
AUTHORITY RECORDS:
->  vercel-dns-017.com
    ttl = 300 (5 mins)
    primary name server = ns1.vercel-dns-017.com
    responsible mail addr = awsdns-hostmaster.amazon.com
    serial  = 1
    refresh = 3600 (1 hour)
    retry   = 900 (15 mins)
    expire  = 1209600 (14 days)
    default TTL = 900 (15 mins)

Nome: 2c27b3c62dd43e9b.vercel-dns-017.com
Addresses: 216.198.79.1
64.29.17.1
Aliases: www.trabalheila.com.br

±--------------------------------------

±--------------------------------------
±------ nslookup www.trabalheila.com.br via 8.8.8.8

Não é resposta autoritativa:
Servidor: dns.google
Address: 8.8.8.8

Nome: 2c27b3c62dd43e9b.vercel-dns-017.com
Addresses: 64.29.17.65
216.198.79.65
Aliases: www.trabalheila.com.br

±--------------------------------------

±--------------------------------------
±------ Output of www.trabalheila.com.br

Host www.trabalheila.com.br:443 was resolved.
IPv6: (none)
IPv4: 64.29.17.1, 216.198.79.1
Trying 64.29.17.1:443…
schannel: disabled automatic use of client certificate
ALPN: curl offers http/1.1
ALPN: server accepted http/1.1
Connected to www.trabalheila.com.br (64.29.17.1) port 443
using HTTP/1.x

GET / HTTP/1.1
Host: www.trabalheila.com.br
User-Agent: curl/8.13.0
Accept: /

Request completely sent off
< HTTP/1.1 200 OK
< Accept-Ranges: bytes
< Access-Control-Allow-Origin: *
< Age: 7303
< Cache-Control: public, max-age=0, must-revalidate
< Content-Disposition: inline
< Content-Length: 1552
< Content-Type: text/html; charset=utf-8
< Date: Wed, 29 Apr 2026 00:10:21 GMT
< Etag: “f33cbc2dbc7c065fcfb78b2d2354a54e”
< Last-Modified: Tue, 28 Apr 2026 22:08:37 GMT
< Server: Vercel
< Strict-Transport-Security: max-age=63072000
< X-Vercel-Cache: HIT
< X-Vercel-Id: gru1::x9nfv-1777421421797-0bc75ced1b15
<
{ [1552 bytes data]
Trabalhei L├íVoc├¬ precisa habilitar o JavaScript para rodar este aplicativo.* Connection #0 to host www.trabalheila.com.br left intact

±--------------------------------------

±--------------------------------------
| Time elapsed: 28.7 seconds
|
±------ FINISHED
±--------------------------------------

system · April 29, 2026, 12:26am

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

You can also use v0 to narrow down the possibilities.

pawlean · April 29, 2026, 10:29am

Looks like it works now!

caiocad-4192 · April 29, 2026, 12:40pm

Hi Pauline,

Thank you for the update and for marking the issue as “SOLVED”.

However, I’m still encountering the 404: NOT_FOUND error with the DEPLOYMENT_NOT_FOUND code when trying to access www.trabalheila.com.br. I’ve attached a screenshot of the error page I’m seeing.

Additionally, I’ve noticed a message “Trabalhei L… precisa habilitar o JavaScript para rodar este aplicativo.” (Trabalhei L… needs to enable JavaScript to run this application) appearing, which might be related to the application not loading correctly.

Previously, the Vercel AI diagnosed this as a “potential internal routing issue” and an “infrastructure-level issue” that wasn’t visible through standard diagnostics. It seems this underlying problem might still be present.

Could you please re-open the case and investigate further? I’m happy to provide any additional information or run more debug scripts if needed.

Thank you for your continued support.

Best regards,

Caio (Brazil)

pawlean · April 29, 2026, 3:52pm

Ah, I see the issue now!

Can you go through this guide?

Topic		Replies	Views
404: not_found Help domains	4	210	August 12, 2024
Vercel projects inaccessible with timeout errors on Hobby plan in Brazil Help domains , account , monitoring , cdn	15	157	February 26, 2026
All my new and old development domains are not working Help nextjs , react	15	478	April 10, 2025
Todos os projetos estão retornando 404 NOT_FOUND com deploy "Ready" Help	3	98	September 28, 2025
Vercel deployment returns DEPLOYMENT_NOT_FOUND 404 error on custom domain v0 v0 , domains , builds	2	84	March 6, 2026

DEPLOYMENT_NOT_FOUND despite READY deployment with alias assigned

Não é resposta autoritativa:

Related topics