The nareserva project times out when accessed via its deployment URL. The page does not load and eventually fails in the browser, despite deployments completing successfully. This behavior started after changing the project’s function region configuration.
The issue persists consistently and is not intermittent.
Expected Behavior
The nareserva project should load normally after a successful deployment, regardless of the configured region.
Steps to Reproduce
Update the project configuration to change the deployment region
Redeploy the nareserva project
Deployment completes successfully
Access the deployment URL
The request hangs and eventually times out
Configuration Details
Project:nareserva
Region: Explicitly changed (previously working before the change)
Firewall: No rules configured
Status: Issue persists even after reverting or testing different region settings
Code: No recent application-level code changes related to networking or routing
Project Information
Project name:nareserva
Environment: Production
Project settings:
Deployments complete successfully
DNS and SSL are valid
External health checks return HTTP 200
No firewall rules enabled
Geographic location: Brazil (Southeast). The issue was also reproduced from a different external network/provider.
Additional Notes
The issue persists across different networks and devices
The problem started only after modifying the region configuration
Behavior suggests a possible routing or account-level issue related to region changes
Other projects in the account may be affected, but this report is focused on nareserva
Is anyone else experiencing website downness? It simply won’t open anymore.
This site can’t be reached.
poke-monsters-rpg.vercel.app took too long to respond.
Try:
Checking your connection
Checking your proxy and firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT
Having the same issue. All my .vercel.app sites are timing out
I dug into it and .vercel.app resolves to IPs which just hang, no TLS handshake, nothing.
But if I override DNS in /etc/hosts to point to 76.76.21.21, everything loads fine.
So it looks like a DNS issue, .vercel.app is pointing to edge IPs that are down, at least from Brazil
PS C:\WINDOWS\system32> Invoke-RestMethod -Uri https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.ps1 | Invoke-Expression | tee vercel-debug.txt
Domain to test (e.g. example.com): : https://glassfitpro.vercel.app/
Domain to test (e.g. example.com): : glassfitpro.vercel.app/
Domain to test (e.g. example.com): : https://glassfitpro.vercel.app/
Domain to test (e.g. example.com): : glassfitpro.vercel.app
+---------------------------------------
+------- Fetching IP Addresses
|
| glassfitpro.vercel.app IP range: 216.198.79.3, 216.198.79.67, 216.198.79.131, 216.198.79.195, 64.29.17.3, 64.29.17.67, 64.29.17.131, 64.29.17.195
+---------------------------------------
+---------------------------------------
+------- STARTING
|
| Domain to test: glassfitpro.vercel.app
| Timestamp (UTC): 02/25/2026 23:37:02
| Timestamp (Local): 02/25/2026 20:37:02
+---------------------------------------
+---------------------------------------
+------- IP Information
{
"status": 429,
"error": {
"title": "Rate limit exceeded",
"message": "Sign up at ipinfo.io"
}
}
+---------------------------------------
+---------------------------------------
+------- Testing 216.198.79.3
Checking headers via 216.198.79.3
* Connecting to hostname: 216.198.79.3
* Trying 216.198.79.3:443...
* Connection timed out after 3007 milliseconds
* closing connection #0
Checking ping to 216.198.79.3
Disparando 216.198.79.3 com 32 bytes de dados:
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Estatísticas do Ping para 216.198.79.3:
Pacotes: Enviados = 4, Recebidos = 0, Perdidos = 4 (100% de
perda),
Checking tracert to 216.198.79.3
Rastreando a rota para 216.198.79.3 com no máximo 30 saltos
1 <1 ms <1 ms <1 ms 192.168.0.1
2 4 ms 2 ms 2 ms 100.90.0.1
3 2 ms 18 ms 19 ms 10.3.12.249
4 1 ms 1 ms 2 ms 10.3.12.162
5 4 ms 4 ms 3 ms 10.3.12.254
6 5 ms 5 ms 12 ms 10.253.0.37
7 5 ms 5 ms 5 ms 10.251.0.6
8 * * * Esgotado o tempo limite do pedido.
9 * * * Esgotado o tempo limite do pedido.
10 * * * Esgotado o tempo limite do pedido.
11 * * * Esgotado o tempo limite do pedido.
12 * * * Esgotado o tempo limite do pedido.
13 * * * Esgotado o tempo limite do pedido.
14 * * * Esgotado o tempo limite do pedido.
15 * * * Esgotado o tempo limite do pedido.
16 * * * Esgotado o tempo limite do pedido.
17 * * * Esgotado o tempo limite do pedido.
18 * * * Esgotado o tempo limite do pedido.
19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
23 * * * Esgotado o tempo limite do pedido.
24 * * * Esgotado o tempo limite do pedido.
25 * * * Esgotado o tempo limite do pedido.
26 * * * Esgotado o tempo limite do pedido.
27 * * * Esgotado o tempo limite do pedido.
28 * * * Esgotado o tempo limite do pedido.
29 * * * Esgotado o tempo limite do pedido.
30 * * * Esgotado o tempo limite do pedido.
Rastreamento concluído.
+---------------------------------------
+---------------------------------------
+------- Testing 216.198.79.67
Checking headers via 216.198.79.67
* Connecting to hostname: 216.198.79.67
* Trying 216.198.79.67:443...
* Connection timed out after 3006 milliseconds
* closing connection #0
Checking ping to 216.198.79.67
Disparando 216.198.79.67 com 32 bytes de dados:
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Estatísticas do Ping para 216.198.79.67:
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.