[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Unable to access Vercel servers from home Internet connection

129 views · 0 likes · 4 posts


dvdkon (@dvdkon) · 2024-08-07

This is related to [@zbycz's issues](https://community.vercel.com/t/my-ip-address-behind-nat-is-blocked/411), but since my traceroute output is very different, I though it best to create my own thread here, as recommended by @pawlean .

Info from ipinfo.io:

```
{
  "ip": "178.255.168.23",
  "hostname": "nat-23.starnet.cz",
  "city": "Prague",
  "region": "Prague",
  "country": "CZ",
  "loc": "50.0880,14.4208",
  "org": "AS44489 STARNET, s.r.o.",
  "postal": "110 00",
  "timezone": "Europe/Prague",
  "readme": "https://ipinfo.io/missingauth"
}
```

Lookup of vercel.com:

```
# host vercel.com
vercel.com has address 76.76.21.22
vercel.com has address 76.76.21.164
```

TCP traceroutes:

```
# sudo traceroute -T -p 443 76.76.21.22
traceroute to 76.76.21.22 (76.76.21.22), 30 hops max, 60 byte packets
 1  _gateway (10.0.1.1)  1.390 ms  1.357 ms  1.344 ms
 2  10.43.238.97 (10.43.238.97)  9.826 ms  9.813 ms  9.803 ms
 3  100.100.115.254 (100.100.115.254)  10.627 ms  10.616 ms  10.605 ms
 4  cust-starnet.supernetwork (88.86.97.209)  10.592 ms  10.579 ms cust-starnet.supernetwork.cz (88.86.97.137)  9.756 ms
 5  151.148.13.110 (151.148.13.110)  9.679 ms * *
 6  * 150.222.81.25 (150.222.81.25)  15.903 ms *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

# sudo traceroute -T -p 443 76.76.21.164
traceroute to 76.76.21.164 (76.76.21.164), 30 hops max, 60 byte packets
 1  _gateway (10.0.1.1)  1.388 ms  1.355 ms  1.345 ms
 2  10.43.238.97 (10.43.238.97)  11.630 ms  11.569 ms  11.561 ms
 3  100.100.115.254 (100.100.115.254)  11.497 ms  11.680 ms *
 4  cust-starnet.supernetwork.cz (88.86.97.137)  11.526 ms  11.517 ms cust-starnet.supernetwork (88.86.97.209)  11.508 ms
 5  151.148.13.110 (151.148.13.110)  11.500 ms * *
 6  150.222.81.31 (150.222.81.31)  11.603 ms * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
```


Pauline P. Narvas (@pawlean) · 2024-08-08

Hi, @dvdkon!

Could you also just follow the steps outlined in https://community.vercel.com/t/resolving-ip-blocking-issues/171?


dvdkon (@dvdkon) · 2024-08-09

Hi, I've looked at those instructions before. I'm certain this is not a problem with my device(s). Given the traceroute output above ends with an AWS IP address, it also seems to not be a straightforward block from my ISP (which another customer has already confirmed in [a GitHub issue](https://github.com/orgs/vercel/discussions/7403)), but I can't rule out some other problem on their part.

At this point, I feel I've exhausted my possibilities. If there's anything more specific that you think I should try, please tell me.


Pauline P. Narvas (@pawlean) · 2024-08-12

Thanks for your patience, @dvdkon!

I'll raise this internally.