My IP address (behind NAT) is blocked

[zbycz]

Summary

My ISP is using NAT – so there are lots of users behind 1 IP address. Recently (~1week) vercel has been blocking all requests to vercel.com or any other vercel deployed site. My IP: 178.255.168.23

When I connect through my cell phone service, everyhing works fine.

Example

No response

Steps to Reproduce

❯ ping vercel.com
PING vercel.com (76.76.21.9): 56 data bytes
Request timeout for icmp_seq 0

[pawlean]

Hi @zbycz!

We created a debugging tool here, can you please run it and send us the output? It'll help us understand what the problem is!

[OssianN]

Thank you, @pawlean! After having reached out to my ISP and done a traceroute to vercel.com they believe the issue is on Vercel's side. They will reach out to see what can be done.

[AstroboiSteve]

I ended up getting my ISP to take me off CG-NAT, resulting in a new IP address, and now I can access Vercel services again.
There really should be a better way to have these cases reviewed/resolved in a timely way.

[pawlean]

Appreciate all the updates, thank you everyone for your patience and feedback. 🙏🏼

[zbycz]

Hi @pawlean , i have unmarked the answer you chosen, because it is still not resolved in any way. All the websites running on vercel platform are still inaccessible from my ISP and they also believe that the issue is on the vercel side. (The same as @OssianN said)

Please is there still work being done on your side? thx. 🤞

[pawlean]

Apologises, @zbycz I had a few discussions open. We're still investigating your case!

[pawlean]

@zbycz Similar to @OssianN, could you execute TCP based traceroute: traceroute -T -p 443 vercel.com? BTW, feel free to drop into our new community (https://vercel.community) It might be easier to DM you directly on there.

[dvdkon]

I have the same ISP (and the same problem) as @zbycz, so I ran the command:

Output of sudo traceroute -T -p 443 vercel.com

traceroute to vercel.com (76.76.21.142), 30 hops max, 60 byte packets
 1  OpenWrt.lan (10.0.1.1)  3.964 ms  0.407 ms  0.390 ms
 2  * * *
 3  100.100.115.254 (100.100.115.254)  10.303 ms  10.406 ms  10.274 ms
 4  cust-starnet.supernetwork.cz (88.86.97.137)  16.102 ms cust-starnet.supernetwork (88.86.97.209)  7.809 ms  10.651 ms
 5  151.148.13.108 (151.148.13.108)  16.209 ms 151.148.13.110 (151.148.13.110)  10.611 ms 151.148.13.108 (151.148.13.108)  7.507 ms
 6  150.222.81.29 (150.222.81.29)  31.857 ms 150.222.81.13 (150.222.81.13)  31.516 ms 150.222.81.39 (150.222.81.39)  31.481 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  * * *

[pawlean]

Hi @dvdkon!

Can you head over to the vercel.community and post there? It'd help me manage this better :)

[zbycz]

Posted here https://vercel.community/t/my-ip-address-behind-nat-is-blocked/411 - thanks @pawlean 🤞

@dvdkon - as we don't share any hops, i guess we may be on different part of network..?

[github-actions[bot]]

This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community