Resolving IP Blocking Issues

pawlean · July 16, 2024, 8:53am

Overview

If you have problems where your IP addresses are suddenly blocked, you may see:

Inability to access certain Vercel hosted sites
Debugging tools indicating blocked IP addresses
Users on both personal and shared networks experiencing similar issues

Typically, this is not a block from us, but an internet service provider (ISP) or network policy issue. This guide will help you understand and resolve these issues.

Common Scenarios

High Traffic Times: Some ISPs may block or throttle access to certain websites during peak usage hours.
Network Policies: Universities, offices, or other shared networks often have strict policies that might inadvertently block certain sites.

Solution

Identify Your Network Type

Determine if you are on a shared network (e.g., university, office) or a personal/home network.

For Shared Networks
Reach out to the network administrators or IT department managing the shared network. Inform them about the issue and provide any debugging information.

For Personal Networks
Get in touch with your Internet Service Provider’s customer support. Explain the issue and ask that they unblock vercel.com, vercel.app, and 76.76.21.21.

General Steps for All Users

Use a VPN Service: A VPN will provide you with a different IP address, potentially resolving the access issue. Consider reliable VPNs like NordVPN or ExpressVPN. Follow their setup guides to get started.
Disable Antivirus Software or Browser Extensions: Temporarily disable these to rule out as causes of the issue.
Check Upstream Routing Devices: Examine routers or modems for block lists. Here’s a common way to do it:
- Log into your router’s web interface (usually by typing 192.168.1.1 into your browser).
- Navigate to the security or firewall settings.
- Look for any block lists and remove entries related to Vercel.
Flush DNS Cache: Open Command Prompt and type ipconfig /flushdns to clear your DNS cache.
Reset Network Settings: Go to your network settings and select “Reset Network” to restore default settings.

Still Facing Issues?

If you’ve already run through the steps above and you’re still facing issues, let us know below and we’ll be in touch. Please be ready to share the vercel-debug.txt output from our debug script.

Feel free to share your experiences and solutions in the comments below!

muridil · July 24, 2024, 1:47pm

I am still facing the same issue. ISP confirmed it is not blocked on their side. What should I do?
Can you pls look into it?

pawlean · July 30, 2024, 5:46pm

Hi @muridil,

Can you follow the steps above?

If you’ve already run through the steps above and you’re still facing issues, let us know below and we’ll be in touch. Please be ready to share the vercel-debug.txt output from our debug script .

Let me know if you have any questions!

gkpo · August 22, 2024, 12:26pm

I have the same issue.
Trying to contact the vercel support team but I always get sent back to the AI assistant.

Using a VPN works temporarily to access help center, but this is not a solution for me
Need help please!

pawlean · August 22, 2024, 3:47pm

Hi, @gkpo!

Did you follow the steps above?

oscar-bundoapp · November 7, 2024, 12:09pm

Hi @pawlean,

I’ve tried all the steps above you mentioned, but they don’t work. Below is the vercel-debug.txt of our site on Vercel having these problems:

Domain to test (e.g. example.com):
┌───────────────────────────────────────
├─────── STARTING
│
│ Domain to test: bundo.app
│ Timestamp (UTC): Thu Nov 7 11:58:41 UTC 2024
| Timestamp (Local): Thu Nov 7 12:58:41 WAT 2024
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── IP Information

{
“ip”: “102.88.34.111”,
“city”: “Lagos”,
“region”: “Lagos”,
“country”: “NG”,
“loc”: “6.4541,3.3947”,
“org”: “AS29465 MTN NIGERIA Communication limited”,
“timezone”: “Africa/Lagos”,
“readme”: “IP Address data API - IPinfo.io”
}
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.21

PING 76.76.21.21 (76.76.21.21): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2

— 76.76.21.21 ping statistics —
4 packets transmitted, 0 packets received, 100.0% packet loss

1 192.168.3.204 (192.168.3.204) 14.885 ms 1.880 ms 1.121 ms
2 * * *
3 10.10.25.77 (10.10.25.77) 42.085 ms 16.523 ms 17.072 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.9

PING 76.76.21.9 (76.76.21.9): 56 data bytes
64 bytes from 76.76.21.9: icmp_seq=0 ttl=245 time=32.008 ms
64 bytes from 76.76.21.9: icmp_seq=1 ttl=245 time=37.320 ms
64 bytes from 76.76.21.9: icmp_seq=2 ttl=245 time=34.479 ms
64 bytes from 76.76.21.9: icmp_seq=3 ttl=245 time=37.584 ms

— 76.76.21.9 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 32.008/35.348/37.584/2.280 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.22

PING 76.76.21.22 (76.76.21.22): 56 data bytes
64 bytes from 76.76.21.22: icmp_seq=0 ttl=244 time=48.360 ms
64 bytes from 76.76.21.22: icmp_seq=1 ttl=244 time=31.959 ms
64 bytes from 76.76.21.22: icmp_seq=2 ttl=244 time=18.305 ms
64 bytes from 76.76.21.22: icmp_seq=3 ttl=244 time=32.180 ms

— 76.76.21.22 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.305/32.701/48.360/10.645 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.61

PING 76.76.21.61 (76.76.21.61): 56 data bytes
64 bytes from 76.76.21.61: icmp_seq=0 ttl=244 time=34.048 ms
64 bytes from 76.76.21.61: icmp_seq=1 ttl=244 time=18.144 ms
64 bytes from 76.76.21.61: icmp_seq=2 ttl=244 time=71.571 ms
64 bytes from 76.76.21.61: icmp_seq=3 ttl=244 time=64.247 ms

— 76.76.21.61 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.144/47.002/71.571/21.804 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.93

PING 76.76.21.93 (76.76.21.93): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2

— 76.76.21.93 ping statistics —
4 packets transmitted, 0 packets received, 100.0% packet loss

1 192.168.3.204 (192.168.3.204) 3.604 ms 3.739 ms 1.659 ms
2 * * *
3 10.10.25.77 (10.10.25.77) 483.686 ms 20.084 ms 39.906 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.98

PING 76.76.21.98 (76.76.21.98): 56 data bytes
64 bytes from 76.76.21.98: icmp_seq=0 ttl=244 time=25.545 ms
Request timeout for icmp_seq 1
64 bytes from 76.76.21.98: icmp_seq=2 ttl=244 time=34.243 ms
64 bytes from 76.76.21.98: icmp_seq=3 ttl=244 time=23.684 ms

— 76.76.21.98 ping statistics —
4 packets transmitted, 3 packets received, 25.0% packet loss
round-trip min/avg/max/stddev = 23.684/27.824/34.243/4.602 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.123

PING 76.76.21.123 (76.76.21.123): 56 data bytes
64 bytes from 76.76.21.123: icmp_seq=0 ttl=245 time=33.136 ms
64 bytes from 76.76.21.123: icmp_seq=1 ttl=245 time=49.627 ms
64 bytes from 76.76.21.123: icmp_seq=2 ttl=245 time=49.505 ms
64 bytes from 76.76.21.123: icmp_seq=3 ttl=245 time=25.007 ms

— 76.76.21.123 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 25.007/39.319/49.627/10.643 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.142

PING 76.76.21.142 (76.76.21.142): 56 data bytes
64 bytes from 76.76.21.142: icmp_seq=0 ttl=244 time=32.996 ms
64 bytes from 76.76.21.142: icmp_seq=1 ttl=244 time=34.631 ms
64 bytes from 76.76.21.142: icmp_seq=2 ttl=244 time=23.643 ms

— 76.76.21.142 ping statistics —
4 packets transmitted, 3 packets received, 25.0% packet loss
round-trip min/avg/max/stddev = 23.643/30.423/34.631/4.841 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.164

PING 76.76.21.164 (76.76.21.164): 56 data bytes
64 bytes from 76.76.21.164: icmp_seq=0 ttl=244 time=126.194 ms
64 bytes from 76.76.21.164: icmp_seq=1 ttl=244 time=28.628 ms
64 bytes from 76.76.21.164: icmp_seq=2 ttl=244 time=32.787 ms
64 bytes from 76.76.21.164: icmp_seq=3 ttl=244 time=21.113 ms

— 76.76.21.164 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 21.113/52.181/126.194/42.936 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.241

PING 76.76.21.241 (76.76.21.241): 56 data bytes
64 bytes from 76.76.21.241: icmp_seq=0 ttl=244 time=30.522 ms
64 bytes from 76.76.21.241: icmp_seq=1 ttl=244 time=53.296 ms
64 bytes from 76.76.21.241: icmp_seq=2 ttl=244 time=26.894 ms
64 bytes from 76.76.21.241: icmp_seq=3 ttl=244 time=24.649 ms

— 76.76.21.241 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 24.649/33.840/53.296/11.427 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig bundo.app

; <<>> DiG 9.10.6 <<>> bundo.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14192
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;bundo.app. IN A

;; ANSWER SECTION:
bundo.app. 1799 IN A 76.76.21.21

;; Query time: 281 msec
;; SERVER: 192.168.3.204#53(192.168.3.204)
;; WHEN: Thu Nov 07 13:02:28 WAT 2024
;; MSG SIZE rcvd: 54

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig bundo.app via 8.8.8.8

; <<>> DiG 9.10.6 <<>> bundo.app @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22664
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;bundo.app. IN A

;; ANSWER SECTION:
bundo.app. 1799 IN A 76.76.21.21

;; Query time: 308 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Nov 07 13:02:29 WAT 2024
;; MSG SIZE rcvd: 54

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig bundo.app via trace

; <<>> DiG 9.10.6 <<>> bundo.app +trace
;; global options: +cmd
. 84683 IN NS h.root-servers.net.
. 84683 IN NS b.root-servers.net.
. 84683 IN NS a.root-servers.net.
. 84683 IN NS f.root-servers.net.
. 84683 IN NS e.root-servers.net.
. 84683 IN NS m.root-servers.net.
. 84683 IN NS k.root-servers.net.
. 84683 IN NS g.root-servers.net.
. 84683 IN NS i.root-servers.net.
. 84683 IN NS l.root-servers.net.
. 84683 IN NS j.root-servers.net.
. 84683 IN NS d.root-servers.net.
. 84683 IN NS c.root-servers.net.
. 79385 IN RRSIG NS 8 0 518400 20241115050000 20241102040000 61050 . qtis0lIYScCMUQ+c0nXL27rTs2ItauP/iABdSLKW7svMs1zagi9HnXiu DkGtnbkgXtQg0BXgXTNFnJW5SugH1Em/cyNsmGD7HG2CaoKtLWjHmClv BcDZKEBHhCYg0V5Z1a4uK24DGzSFohG7cfnyWicRJ4dzf/9+Nq2cT40Q b6GGAveubgcHbH/XmUzAwS1Z82bZ0ybaRB40V+9SLYmdVL2PO+0Q1G5i 6tWcQPqtDevcK7IfTAnNxueTPoLbtDXvkpoeuycc2qzHjNRkqSRr0gzx E7h+5JKbo2xeAhfnDyIuN9Pf4ndJVVrxofFxZkQnE5v3wT1JcP4L1OzZ zVLgDQ==
;; Received 525 bytes from 192.168.3.204#53(192.168.3.204) in 52 ms

app. 172800 IN NS ns-tld2.charlestonroadregistry.com.
app. 172800 IN NS ns-tld4.charlestonroadregistry.com.
app. 172800 IN NS ns-tld3.charlestonroadregistry.com.
app. 172800 IN NS ns-tld1.charlestonroadregistry.com.
app. 172800 IN NS ns-tld5.charlestonroadregistry.com.
app. 86400 IN DS 23684 8 2 3A5CC8A31E02C94ABA6461912FABB7E9F5E34957BB6114A55A864D96 AEC31836
app. 86400 IN RRSIG DS 8 1 86400 20241120050000 20241107040000 61050 . T+Gtj9CU9KV0qHDEX7nEBI5fxlViGZL70LAeoqEag+kt3QS4Zqrs6137 nBWzKRMNkgVhS/eft5pHx8GAJPZ1kJ4Glv6r055BMYeB7gu3GBt+pL12 hyWqMLU9Om5+tXuiieoKexi+FYpmL0++LZOHUn8NGx9d3t4O1DcOMX5l r8wEts0Bm8OwRbHc7/DOwMrjYt5yFkaBfnQLjFVw31mXUuoG+HUhj9vt xo+uAgY2rJRJCvjDdduFUdNllLEoEPRMAucmb7fRykQCwmo3RId4+uru 9gIAuJ2jz+NBjpL6MM+mY+IeY2fmp72ITMOLR3Zk/nwky7EjnEQL7PKG l2ow+Q==
;; Received 729 bytes from 198.41.0.4#53(a.root-servers.net) in 181 ms

bundo.app. 10800 IN NS dns2.registrar-servers.com.
bundo.app. 10800 IN NS dns1.registrar-servers.com.
kighuu28gth3dplje8bl0muj4r3nuou1.app. 900 IN NSEC3 1 0 1 139FCA6C02909936 KIGIOM26H9L3CUKB8HVE2UBPBR4RJSVN NS
kighuu28gth3dplje8bl0muj4r3nuou1.app. 900 IN RRSIG NSEC3 8 2 900 20241126171101 20241104171101 28036 app. AFbGb4fTxhfre8rfudoGMX0Br7k7bLshsubeT1bEcMjVLM8yFKmlGZxk luvXE6R/i0H9kfntXopA0Dqhmmfsm9563RKV4//Li960LA3AY3UICRu6 AgcaiZVTVC2NRIKZdPrK9YQE8ZAXQo3rjbrn2YE1Y40PB7c9gzjug3mp 3UI=
;; Received 342 bytes from 216.239.36.105#53(ns-tld3.charlestonroadregistry.com) in 158 ms

bundo.app. 1799 IN A 76.76.21.21
bundo.app. 1800 IN NS dns1.registrar-servers.com.
bundo.app. 1800 IN NS dns2.registrar-servers.com.
;; Received 113 bytes from 156.154.132.200#53(dns1.registrar-servers.com) in 151 ms

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Output of bundo.app

Trying 76.76.21.21:443…
connect to 76.76.21.21 port 443 failed: Connection refused
Failed to connect to bundo.app port 443 after 27 ms: Couldn’t connect to server
Closing connection

└───────────────────────────────────────

┌───────────────────────────────────────
│ Time elapsed: 234 seconds
│
├─────── FINISHED
└───────────────────────────────────────

amyegan · November 14, 2024, 4:55pm

@oscar-bundoapp. Thanks for reaching out about this. Vercel’s 76.76.21.21 IP address is being blocked by MTN and we are working with them to resolve this issue. You may still be able to access Vercel hosted sites from a different network or by using a VPN service as suggested above. I use a different ISP and can confirm that I was able to access your site without error.

Others have shared workarounds that they used for their own sites. The most often recommended solutions are to use Vercel nameservers instead of A and CNAME records, or to use a service like Cloudflare with CNAME flattening.

we-shall · December 11, 2024, 6:13am

is the issue resolved? I am facing this issue. I am not able to access my site videoo.ai from Dubai.

This is the vercel-debug.txt

Domain to test (e.g. example.com): 
┌───────────────────────────────────────
├─────── STARTING
│
│ Domain to test: videoo.ai 
│ Timestamp (UTC): Wed Dec 11 06:05:15 UTC 2024
| Timestamp (Local): Wed Dec 11 10:05:15 +04 2024
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── IP Information 

{
  "ip": "87.20.79.79",
  "city": "Dubai",
  "region": "Dubai",
  "country": "AE",
  "loc": "25.0772,55.3093",
  "org": "AS15802 Emirates Integrated Telecommunications Company PJSC",
  "postal": "28506 74783",
  "timezone": "Asia/Dubai",
  "readme": "https://ipinfo.io/missingauth"
}
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.21 

PING 76.76.21.21 (76.76.21.21): 56 data bytes
64 bytes from 76.76.21.21: icmp_seq=0 ttl=246 time=11.081 ms
64 bytes from 76.76.21.21: icmp_seq=1 ttl=246 time=9.705 ms
64 bytes from 76.76.21.21: icmp_seq=2 ttl=246 time=10.168 ms
64 bytes from 76.76.21.21: icmp_seq=3 ttl=246 time=9.904 ms

--- 76.76.21.21 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 9.705/10.215/11.081/0.527 ms

 1  linksys02200 (192.168.1.1)  4.263 ms  2.675 ms  2.070 ms
 2  192.168.70.1 (192.168.70.1)  3.374 ms  3.380 ms  3.165 ms
 3  * * *
 4  10.100.136.154 (10.100.136.154)  9.629 ms  8.289 ms  7.862 ms
 5  10.100.35.78 (10.100.35.78)  8.444 ms  9.112 ms  9.188 ms
 6  10.53.17.77 (10.53.17.77)  10.037 ms  11.737 ms  10.039 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  52.93.68.81 (52.93.68.81)  11.790 ms  10.603 ms  9.884 ms
12  52.93.68.48 (52.93.68.48)  11.550 ms  10.195 ms  75.737 ms
13  76.76.21.21 (76.76.21.21)  13.481 ms  8.705 ms  8.627 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.9 

PING 76.76.21.9 (76.76.21.9): 56 data bytes
64 bytes from 76.76.21.9: icmp_seq=0 ttl=246 time=11.135 ms
64 bytes from 76.76.21.9: icmp_seq=1 ttl=246 time=11.280 ms
64 bytes from 76.76.21.9: icmp_seq=2 ttl=246 time=11.260 ms
64 bytes from 76.76.21.9: icmp_seq=3 ttl=246 time=11.737 ms

--- 76.76.21.9 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.135/11.353/11.737/0.229 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.22 

PING 76.76.21.22 (76.76.21.22): 56 data bytes
64 bytes from 76.76.21.22: icmp_seq=0 ttl=246 time=12.872 ms
64 bytes from 76.76.21.22: icmp_seq=1 ttl=246 time=11.969 ms
64 bytes from 76.76.21.22: icmp_seq=2 ttl=246 time=12.372 ms
64 bytes from 76.76.21.22: icmp_seq=3 ttl=246 time=11.993 ms

--- 76.76.21.22 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.969/12.302/12.872/0.366 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.61 

PING 76.76.21.61 (76.76.21.61): 56 data bytes
64 bytes from 76.76.21.61: icmp_seq=0 ttl=246 time=12.010 ms
64 bytes from 76.76.21.61: icmp_seq=1 ttl=246 time=11.846 ms
64 bytes from 76.76.21.61: icmp_seq=2 ttl=246 time=12.027 ms
64 bytes from 76.76.21.61: icmp_seq=3 ttl=246 time=11.571 ms

--- 76.76.21.61 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.571/11.864/12.027/0.183 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.93 

PING 76.76.21.93 (76.76.21.93): 56 data bytes
64 bytes from 76.76.21.93: icmp_seq=0 ttl=246 time=13.421 ms
64 bytes from 76.76.21.93: icmp_seq=1 ttl=246 time=15.036 ms
64 bytes from 76.76.21.93: icmp_seq=2 ttl=246 time=12.916 ms
64 bytes from 76.76.21.93: icmp_seq=3 ttl=246 time=12.602 ms

--- 76.76.21.93 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.602/13.494/15.036/0.937 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.98 

PING 76.76.21.98 (76.76.21.98): 56 data bytes
64 bytes from 76.76.21.98: icmp_seq=0 ttl=246 time=13.278 ms
64 bytes from 76.76.21.98: icmp_seq=1 ttl=246 time=12.964 ms
64 bytes from 76.76.21.98: icmp_seq=2 ttl=246 time=12.242 ms
64 bytes from 76.76.21.98: icmp_seq=3 ttl=246 time=13.496 ms

--- 76.76.21.98 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.242/12.995/13.496/0.474 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.123 

PING 76.76.21.123 (76.76.21.123): 56 data bytes
64 bytes from 76.76.21.123: icmp_seq=0 ttl=246 time=11.871 ms
64 bytes from 76.76.21.123: icmp_seq=1 ttl=246 time=11.028 ms
64 bytes from 76.76.21.123: icmp_seq=2 ttl=246 time=12.689 ms
64 bytes from 76.76.21.123: icmp_seq=3 ttl=246 time=12.899 ms

--- 76.76.21.123 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.028/12.122/12.899/0.739 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.142 

PING 76.76.21.142 (76.76.21.142): 56 data bytes
64 bytes from 76.76.21.142: icmp_seq=0 ttl=246 time=10.898 ms
64 bytes from 76.76.21.142: icmp_seq=1 ttl=246 time=10.194 ms
64 bytes from 76.76.21.142: icmp_seq=2 ttl=246 time=10.652 ms
64 bytes from 76.76.21.142: icmp_seq=3 ttl=246 time=9.634 ms

--- 76.76.21.142 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 9.634/10.345/10.898/0.482 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.164 

PING 76.76.21.164 (76.76.21.164): 56 data bytes
64 bytes from 76.76.21.164: icmp_seq=0 ttl=246 time=13.552 ms
64 bytes from 76.76.21.164: icmp_seq=1 ttl=246 time=13.610 ms
64 bytes from 76.76.21.164: icmp_seq=2 ttl=246 time=12.893 ms
64 bytes from 76.76.21.164: icmp_seq=3 ttl=246 time=13.365 ms

--- 76.76.21.164 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.893/13.355/13.610/0.282 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.241 

PING 76.76.21.241 (76.76.21.241): 56 data bytes
64 bytes from 76.76.21.241: icmp_seq=0 ttl=246 time=13.885 ms
64 bytes from 76.76.21.241: icmp_seq=1 ttl=246 time=11.831 ms
64 bytes from 76.76.21.241: icmp_seq=2 ttl=246 time=11.723 ms
64 bytes from 76.76.21.241: icmp_seq=3 ttl=246 time=11.495 ms

--- 76.76.21.241 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.495/12.233/13.885/0.961 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig videoo.ai 


; <<>> DiG 9.10.6 <<>> videoo.ai
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47961
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 2

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
;; QUESTION SECTION:
;videoo.ai.			IN	A

;; ADDITIONAL SECTION:
infoblox-base.rpz.infoblox.local. 900 IN SOA	ns1-rpz.csp.infoblox.com. support.infoblox.com. 1733895357 900 300 2592001 900

;; Query time: 33 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Dec 11 10:06:01 +04 2024
;; MSG SIZE  rcvd: 138

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig videoo.ai via 8.8.8.8


; <<>> DiG 9.10.6 <<>> videoo.ai @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10765
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;videoo.ai.			IN	A

;; ANSWER SECTION:
videoo.ai.		1800	IN	A	76.76.21.93
videoo.ai.		1800	IN	A	76.76.21.98

;; Query time: 274 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Dec 11 10:06:01 +04 2024
;; MSG SIZE  rcvd: 70

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig videoo.ai via trace


; <<>> DiG 9.10.6 <<>> videoo.ai +trace
;; global options: +cmd
;; connection timed out; no servers could be reached
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Output of videoo.ai

* Could not resolve host: videoo.ai
* Closing connection

└───────────────────────────────────────


┌───────────────────────────────────────
│ Time elapsed: 61 seconds
│
├─────── FINISHED
└───────────────────────────────────────



File can be found at /Users/ash/vercel-debug.txt

4gn2to2i4g · December 19, 2024, 5:27pm

Hi,
I cannot access vercel.com and many vercel-hosted sites from my home network. it works fine on mobile data(same ISP) and it also works on my phone from my home network.
Almost all the domains I can’t access only from my home network return 76.76.21.21 with dig.
Since another device can access vercel.com from the same network, I’m thinking that Vercel is blocking me, not the other way around.

vecel-debug file:

Domain to test (e.g. example.com):
┌───────────────────────────────────────
├─────── STARTING
│
│ Domain to test: tomorrowbureau.io
│ Timestamp (UTC): 2024. dec. 19., csütörtök, 17:19:44 UTC
| Timestamp (Local): 2024. dec. 19., csütörtök, 18:19:44 CET
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── IP Information

{
“ip”: “78.139.38.224”,
“hostname”: “catv-78-139-38-224.catv.fixed.vodafone.hu”,
“city”: “Balatonalmádi”,
“region”: “Veszprém”,
“country”: “HU”,
“loc”: “47.0353,18.0208”,
“org”: “AS21334 Vodafone Hungary Ltd.”,
“postal”: “8220”,
“timezone”: “Europe/Budapest”,
“readme”: “IP Address data API - IPinfo.io”
}
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.21

PING 76.76.21.21 (76.76.21.21) 56(84) bytes of data.
64 bytes from 76.76.21.21: icmp_seq=1 ttl=248 time=16.9 ms
64 bytes from 76.76.21.21: icmp_seq=2 ttl=248 time=13.0 ms
64 bytes from 76.76.21.21: icmp_seq=3 ttl=248 time=12.8 ms
64 bytes from 76.76.21.21: icmp_seq=4 ttl=248 time=13.0 ms

— 76.76.21.21 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 12.829/13.929/16.894/1.713 ms

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.9

PING 76.76.21.9 (76.76.21.9) 56(84) bytes of data.
64 bytes from 76.76.21.9: icmp_seq=1 ttl=248 time=16.8 ms
64 bytes from 76.76.21.9: icmp_seq=2 ttl=248 time=12.5 ms
64 bytes from 76.76.21.9: icmp_seq=3 ttl=248 time=14.0 ms
64 bytes from 76.76.21.9: icmp_seq=4 ttl=248 time=12.8 ms

— 76.76.21.9 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 12.470/14.015/16.789/1.696 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.22

PING 76.76.21.22 (76.76.21.22) 56(84) bytes of data.
64 bytes from 76.76.21.22: icmp_seq=1 ttl=243 time=20.2 ms
64 bytes from 76.76.21.22: icmp_seq=2 ttl=243 time=17.7 ms
64 bytes from 76.76.21.22: icmp_seq=3 ttl=243 time=16.9 ms
64 bytes from 76.76.21.22: icmp_seq=4 ttl=243 time=17.7 ms

— 76.76.21.22 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 16.906/18.131/20.192/1.234 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.61

PING 76.76.21.61 (76.76.21.61) 56(84) bytes of data.
64 bytes from 76.76.21.61: icmp_seq=1 ttl=243 time=25.9 ms
64 bytes from 76.76.21.61: icmp_seq=2 ttl=243 time=20.4 ms
64 bytes from 76.76.21.61: icmp_seq=3 ttl=243 time=21.4 ms
64 bytes from 76.76.21.61: icmp_seq=4 ttl=243 time=21.3 ms

— 76.76.21.61 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 20.424/22.262/25.906/2.138 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.93

PING 76.76.21.93 (76.76.21.93) 56(84) bytes of data.
64 bytes from 76.76.21.93: icmp_seq=1 ttl=243 time=25.7 ms
64 bytes from 76.76.21.93: icmp_seq=2 ttl=243 time=20.0 ms
64 bytes from 76.76.21.93: icmp_seq=3 ttl=243 time=19.5 ms
64 bytes from 76.76.21.93: icmp_seq=4 ttl=243 time=19.6 ms

— 76.76.21.93 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 19.544/21.201/25.683/2.593 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.98

PING 76.76.21.98 (76.76.21.98) 56(84) bytes of data.
64 bytes from 76.76.21.98: icmp_seq=1 ttl=243 time=23.1 ms
64 bytes from 76.76.21.98: icmp_seq=2 ttl=243 time=19.6 ms

— 76.76.21.98 ping statistics —
4 packets transmitted, 2 received, 50% packet loss, time 3014ms
rtt min/avg/max/mdev = 19.550/21.337/23.124/1.787 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.123

PING 76.76.21.123 (76.76.21.123) 56(84) bytes of data.
64 bytes from 76.76.21.123: icmp_seq=3 ttl=243 time=18.6 ms
64 bytes from 76.76.21.123: icmp_seq=4 ttl=243 time=17.8 ms

— 76.76.21.123 ping statistics —
4 packets transmitted, 2 received, 50% packet loss, time 3037ms
rtt min/avg/max/mdev = 17.786/18.214/18.642/0.428 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.142

PING 76.76.21.142 (76.76.21.142) 56(84) bytes of data.
64 bytes from 76.76.21.142: icmp_seq=1 ttl=243 time=23.1 ms
64 bytes from 76.76.21.142: icmp_seq=2 ttl=243 time=20.0 ms
64 bytes from 76.76.21.142: icmp_seq=3 ttl=243 time=20.0 ms
64 bytes from 76.76.21.142: icmp_seq=4 ttl=243 time=20.0 ms

— 76.76.21.142 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 19.973/20.763/23.059/1.325 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.164

PING 76.76.21.164 (76.76.21.164) 56(84) bytes of data.
64 bytes from 76.76.21.164: icmp_seq=1 ttl=243 time=21.5 ms
64 bytes from 76.76.21.164: icmp_seq=2 ttl=243 time=17.9 ms
64 bytes from 76.76.21.164: icmp_seq=3 ttl=243 time=18.0 ms
64 bytes from 76.76.21.164: icmp_seq=4 ttl=243 time=17.9 ms

— 76.76.21.164 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 17.944/18.851/21.518/1.539 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.241

PING 76.76.21.241 (76.76.21.241) 56(84) bytes of data.
64 bytes from 76.76.21.241: icmp_seq=1 ttl=243 time=22.1 ms
64 bytes from 76.76.21.241: icmp_seq=2 ttl=243 time=22.4 ms
64 bytes from 76.76.21.241: icmp_seq=3 ttl=243 time=19.8 ms
64 bytes from 76.76.21.241: icmp_seq=4 ttl=243 time=18.3 ms

— 76.76.21.241 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 18.310/20.663/22.435/1.682 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig tomorrowbureau.io

; <<>> DiG 9.20.3 <<>> tomorrowbureau.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2840
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;tomorrowbureau.io. IN A

;; ANSWER SECTION:
tomorrowbureau.io. 300 IN A 76.76.21.21

;; Query time: 26 msec
;; SERVER: 192.168.1.1#53(192.168.1.1) (UDP)
;; WHEN: Thu Dec 19 18:20:17 CET 2024
;; MSG SIZE rcvd: 62

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig tomorrowbureau.io via 8.8.8.8

; <<>> DiG 9.20.3 <<>> tomorrowbureau.io @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6095
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;tomorrowbureau.io. IN A

;; ANSWER SECTION:
tomorrowbureau.io. 300 IN A 76.76.21.21

;; Query time: 40 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Thu Dec 19 18:20:17 CET 2024
;; MSG SIZE rcvd: 62

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig tomorrowbureau.io via trace

; <<>> DiG 9.20.3 <<>> tomorrowbureau.io +trace
;; global options: +cmd
. 463072 IN NS f.root-servers.net.
. 463072 IN NS g.root-servers.net.
. 463072 IN NS h.root-servers.net.
. 463072 IN NS i.root-servers.net.
. 463072 IN NS j.root-servers.net.
. 463072 IN NS k.root-servers.net.
. 463072 IN NS l.root-servers.net.
. 463072 IN NS m.root-servers.net.
. 463072 IN NS a.root-servers.net.
. 463072 IN NS b.root-servers.net.
. 463072 IN NS c.root-servers.net.
. 463072 IN NS d.root-servers.net.
. 463072 IN NS e.root-servers.net.
;; Received 811 bytes from 192.168.1.1#53(192.168.1.1) in 23 ms

io. 172800 IN NS a0.nic.io.
io. 172800 IN NS a2.nic.io.
io. 172800 IN NS b0.nic.io.
io. 172800 IN NS c0.nic.io.
io. 86400 IN DS 57355 8 2 95A57C3BAB7849DBCDDF7C72ADA71A88146B141110318CA5BE672057 E865C3E2
io. 86400 IN RRSIG DS 8 1 86400 20250101050000 20241219040000 61050 . hmGLR1wOxm70rgOU9/ZNSYbAQXGNbQLq0bpGThaWtrh9LJKzCpfv9dSk 2kuMAxrZF0FUTzncxsa7aKxfhpmHkzdicorpoxCUt5eJbvCqqwqWg218 WySHLKftmL9W1SbVeSlrCEqPItEUWeCqjm14cbSyIdRHSzoCaACCK9LS f5MAKz6Ry/0/xvQen6RQH7baGxkTyhcbjLvdBdXwelu8rYg4/CiTq9aM Ixj6vbqF1sEBJ+nU2MvK2ucCBqGATvhJmzkpmf6Iw9snNN2S14Byk7Dj o/11gWvvX5L0TR9rqJvtd0BvuGlFEvvOXqkmvT0RUdkZZL9FQ0C9T3J1 HqEpWg==
;; Received 629 bytes from 192.5.5.241#53(f.root-servers.net) in 16 ms

;; UDP setup with 2a01:8840:9e::17#53(2a01:8840:9e::17) for tomorrowbureau.io failed: network unreachable.
;; no servers could be reached
;; UDP setup with 2a01:8840:9e::17#53(2a01:8840:9e::17) for tomorrowbureau.io failed: network unreachable.
;; no servers could be reached
;; UDP setup with 2a01:8840:9e::17#53(2a01:8840:9e::17) for tomorrowbureau.io failed: network unreachable.
tomorrowbureau.io. 3600 IN NS paul.ns.cloudflare.com.
tomorrowbureau.io. 3600 IN NS dorthy.ns.cloudflare.com.
52ko96budrr3nmfkc8cbka2vfqnm5jps.io. 3600 IN NSEC3 1 1 0 73 52KQK0IL9IJ40ET2RNKVBVONSAGJ9T72 NS SOA RRSIG DNSKEY NSEC3PARAM
52ko96budrr3nmfkc8cbka2vfqnm5jps.io. 3600 IN RRSIG NSEC3 8 2 3600 20250109171810 20241219161810 22296 io. ULVWxHuCxUkT2q8ZK9GqneSC32kpZpg+Trd7n2E3bniF0GlYJ3bJ9Y4n hkV3fkM2dsZ42k9VlUIsBS7CYTmHDRtk4y82mqU3tkyZJc1HItzDoqOe I0+BG6e3ecfLN9Uw/aoqE/w5O/OvnRVEcCZOqI3U1WV66e2t1yUnd3iW kwY=
rg3g7a30fn0tgbb4kka3l72t111n3lsp.io. 3600 IN NSEC3 1 1 0 73 RG5DR8BVOCK3GI8A93KQ82QHA7T8L0UQ NS DS RRSIG
rg3g7a30fn0tgbb4kka3l72t111n3lsp.io. 3600 IN RRSIG NSEC3 8 2 3600 20250107154400 20241217144400 22296 io. pxUic74/a5OKAzoDpAwOY0PG6qdmnaA4VFd0b+Q0iHZTVIu11aY2+r4L qTxbEX28BLMDHoG19yQbym8gvEv7Lq2WgRTK6da3bnRkdiRJI8JOOlDI paIBS6PCWcvnrc6c6kAOkhXPlSkbP5/lSDxe/y7oMprlsV/4/WbuMx7P i6A=
;; Received 588 bytes from 65.22.162.17#53(c0.nic.io) in 46 ms

;; UDP setup with 2803:f800:50::6ca2:c187#53(2803:f800:50::6ca2:c187) for tomorrowbureau.io failed: network unreachable.
tomorrowbureau.io. 300 IN A 76.76.21.21
;; Received 62 bytes from 173.245.58.249#53(dorthy.ns.cloudflare.com) in 23 ms

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Output of tomorrowbureau.io

Host tomorrowbureau.io:443 was resolved.
IPv6: (none)
IPv4: 76.76.21.21
Trying 76.76.21.21:443…
ALPN: curl offers h2,http/1.1
} [5 bytes data]
TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [15 bytes data]
TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2579 bytes data]
TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
TLSv1.3 (IN), TLS handshake, Finished (20):
{ [36 bytes data]
TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
TLSv1.3 (OUT), TLS handshake, Finished (20):
} [36 bytes data]
SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / x25519 / RSASSA-PSS
ALPN: server accepted h2
Server certificate:
subject: CN=tomorrowbureau.io
start date: Dec 17 00:10:09 2024 GMT
expire date: Mar 17 00:10:08 2025 GMT
issuer: C=US; O=Let’s Encrypt; CN=R11
SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
Connected to tomorrowbureau.io (76.76.21.21) port 443
using HTTP/2
[HTTP/2] [1] OPENED stream for https://tomorrowbureau.io/
[HTTP/2] [1] [:method: GET]
[HTTP/2] [1] [:scheme: https]
[HTTP/2] [1] [:authority: tomorrowbureau.io]
[HTTP/2] [1] [:path: /]
[HTTP/2] [1] [user-agent: curl/8.11.1]
[HTTP/2] [1] [accept: /]
} [5 bytes data]

GET / HTTP/2
Host: tomorrowbureau.io
User-Agent: curl/8.11.1
Accept: /

{ [5 bytes data]

TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [122 bytes data]
Request completely sent off
{ [5 bytes data]
< HTTP/2 308
< cache-control: public, max-age=0, must-revalidate
< content-type: text/plain
< date: Thu, 19 Dec 2024 17:20:18 GMT
< location: https://www.tomorrowbureau.io/
< refresh: 0;url=https://www.tomorrowbureau.io/
< server: Vercel
< strict-transport-security: max-age=63072000
< x-vercel-id: fra1::v66t6-1734628818150-030f6a926174
<
} [5 bytes data]
Redirecting…
Connection #0 to host tomorrowbureau.io left intact

└───────────────────────────────────────

┌───────────────────────────────────────
│ Time elapsed: 34 seconds
│
├─────── FINISHED
└───────────────────────────────────────

File can be found at /home/aronkvh/vercel-debug.txt

4gn2to2i4g · December 20, 2024, 2:33pm

Also, I’ve already asked my ISP and they said they don’t know and I should “just restart the router”.

4gn2to2i4g · December 30, 2024, 5:30pm

If I understand this right, there is no way to get help about this issue unless you are on a paid Vercel plan, right?

pawlean · January 2, 2025, 2:18pm

Hi Aron! Thanks for the ping. Sorry, just been catching up after the break.

Let me share this with the team internally I’ll keep you updated via DMs.

galaczi · January 3, 2025, 2:28pm

I am having this issue for a year now only on my Linux desktop. I checked everything, even flushed DNS cache. My Windows laptop can reach Vercel from the same network easily. So my guess is it’s some kind of firewall since bot traffic is mostly Linux. Which is a shame becuase lots of programmers use Linux. I cannot access code documentation sites hosted on Vercel, and a lot of projects host their docs on Vercel.

Topic		Replies	Views
Trouble accessing my web application from Nigeria, and Dubai. From Nigeria, I am only able to use VPN to access it Help domains	3	36	August 14, 2024
Vercel's IP is blacklisted and inaccessible from some ISPs Help domains	2	39	October 17, 2024
Possible IP Block After Load Testing on Our Vercel Domain Help	3	18	August 1, 2024
IP blocked Help	7	78	August 22, 2024
I can open the website with VPN turned on, but I can't open it with VPN turned off Help react	4	25	December 12, 2024

Resolving IP Blocking Issues

Overview

Common Scenarios

Solution

Identify Your Network Type

General Steps for All Users

Still Facing Issues?

Related topics