[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)
[Help](/c/help/9)
# Vercel projects inaccessible with timeout errors on Hobby plan in Brazil
105 views · 4 likes · 15 posts
Projetos AMD (@altamarketing) · 2026-02-26 · ♥ 1
## Problem
All my projects stopped working suddenly about 30 minutes ago. I get a timeout error:
> **Error: took too long to respond**
## Current Behavior
- All projects show `live: false` which seems abnormal.
- Support bot confirmed domain returns `200` from `Vercel`’s side.
- Deployments show `READY` in the dashboard.
## Environment
- **Plan:** `Hobby`
- **Region:** Brazil
- **Devices:** Phone and PC
- **Networks:** Multiple Wi-Fi networks, 5G mobile data
## Troubleshooting Steps Taken
1. Tested on different browsers and incognito mode.
2. Verified access to [vercel.com](http://vercel.com) and [nextjs.org](http://nextjs.org) (both work normally).
3. Checked account status (active, no soft-blocks).
osamuelleal (@osamuelleal) · 2026-02-26
Yep, is not working for me too… I’m from Brazil as well
Projetos AMD (@altamarketing) · 2026-02-26
Have you received any response from support?
Leo Ornelas (@leo-ornelas) · 2026-02-26
Same here. A permanent solution I found is to set up your own domain instead of using `vercel.app`
Example:
new-project.vercel.app → DNS problems
new-project.com.br → Works fine
You can set it up here: /settings/domains
Washingtongomesgouvea (@washingtongomesgouve) · 2026-02-26
same problem here!
Pauline P. Narvas (@pawlean) · 2026-02-26 · ♥ 1
We’re aware of this issue and have deployed a fix. Are you still seeing this?
Cristhian Pen (@cristhian-pen) · 2026-02-26
## Problem
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
1. Update the project configuration to change the deployment region
2. Redeploy the `nareserva` project
3. Deployment completes successfully
4. Access the deployment URL
5. 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`
Elton (@efroefroefro-8912) · 2026-02-25 · ♥ 1
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
Guilherme (@guilehm2) · 2026-02-26
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
viccs (@pauloviccs) · 2026-02-26
```
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:
```
Veltcorp (@veltcorp) · 2026-02-26
Same problem here.. And support doesnt help.
I dont know what to do..
Pauline P. Narvas (@pawlean) · 2026-02-26
This should be working now folks, but let me know if you're still seeing issues!
João Oliveira (@ojoaovvictor) · 2026-02-26
Hi everyone, I’m from Brazil and I need urgent help with my Vercel project.
## Problem
- The deploy status is “Ready” and the build finishes without errors.
- The site works perfectly on localhost (`npm run dev`), but does not open on the domain `stela-joias.vercel.app` (nor on the secondary Vercel domains).
- The browser keeps loading and eventually returns:
> **Error: ERR_CONNECTION_TIMED_OUT**
## What I've Tried
- Creating a new project
- Removing `vercel.json`
- Redeploying and clearing cache
- Testing on different networks/devices
- Verified environment variables are correctly set
- Verified the static build is generated in the `dist` folder
- Confirmed the domain is correctly linked to the project
This project is already being used by a client and cannot stay offline. I need an urgent solution to restore access to the domain.
Thank you for any help or support from the team/community!
system (@system) · 2026-02-26
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](https://community.vercel.com/t/introducing-the-vercel-leaderboard/1358).
https://vercel.com/docs/projects/domains/troubleshooting
You can also use [v0](https://v0.dev/) to narrow down the possibilities.
Projetos AMD (@altamarketing) · 2026-02-26 · ♥ 1
Resolvido. Obrigado!