Resolving IP Blocking Issues

pawlean · June 6, 2025, 1:05pm

Thanks for sharing this, @eycis! Let me raise it internally

jose-manuel-silva · June 12, 2025, 5:10am

This is happening to me on all of my websites from people trying to access it in Malaysia.
It started around yesterday, heres the debug script output.

Vercel debug

±--------------------------------------
±------ STARTING
|
| Domain to test: saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app
| Timestamp (UTC): 06/12/2025 04:52:46
| Timestamp (Local): 06/12/2025 12:52:46
±--------------------------------------

±--------------------------------------
±------ IP Information

{
“ip”: “60.52.19.229”,
“city”: “Cyberjaya”,
“region”: “Selangor”,
“country”: “MY”,
“loc”: “2.9228,101.6572”,
“org”: “AS4788 TM TECHNOLOGY SERVICES SDN. BHD.”,
“postal”: “63100”,
“timezone”: “Asia/Kuala_Lumpur”,
“readme”: “IP Address data API - IPinfo.io”
}

±--------------------------------------

±--------------------------------------
±------ Testing 76.76.21.21

Pinging 76.76.21.21 with 32 bytes of data:
Reply from 76.76.21.21: bytes=32 time=11ms TTL=250
Reply from 76.76.21.21: bytes=32 time=10ms TTL=250
Reply from 76.76.21.21: bytes=32 time=11ms TTL=250
Reply from 76.76.21.21: bytes=32 time=11ms TTL=250

Ping statistics for 76.76.21.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

Tracing route to 76.76.21.21 over a maximum of 30 hops

1 2 ms 2 ms 2 ms home [192.168.1.1]
2 10 ms 5 ms 6 ms 60.52.19.254
3 14 ms 14 ms 13 ms 10.55.106.149
4 12 ms 11 ms * 10.55.108.98
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 14 ms 16 ms 16 ms 150.222.78.41
12 11 ms 11 ms 11 ms 76.76.21.21

Trace complete.
±--------------------------------------

±--------------------------------------
±------ Testing 216.198.79.1

Pinging 216.198.79.1 with 32 bytes of data:
Reply from 216.198.79.1: bytes=32 time=15ms TTL=250
Reply from 216.198.79.1: bytes=32 time=11ms TTL=250
Reply from 216.198.79.1: bytes=32 time=10ms TTL=250
Reply from 216.198.79.1: bytes=32 time=10ms TTL=250

Ping statistics for 216.198.79.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 15ms, Average = 11ms
±--------------------------------------

±--------------------------------------
±------ Testing 216.198.79.65

Pinging 216.198.79.65 with 32 bytes of data:
Reply from 216.198.79.65: bytes=32 time=11ms TTL=250
Reply from 216.198.79.65: bytes=32 time=11ms TTL=250
Reply from 216.198.79.65: bytes=32 time=11ms TTL=250
Reply from 216.198.79.65: bytes=32 time=10ms TTL=250

Ping statistics for 216.198.79.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms
±--------------------------------------

±--------------------------------------
±------ Testing 216.198.79.129

Pinging 216.198.79.129 with 32 bytes of data:
Reply from 216.198.79.129: bytes=32 time=11ms TTL=250
Reply from 216.198.79.129: bytes=32 time=11ms TTL=250
Reply from 216.198.79.129: bytes=32 time=11ms TTL=250
Reply from 216.198.79.129: bytes=32 time=11ms TTL=250

Ping statistics for 216.198.79.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms
±--------------------------------------

±--------------------------------------
±------ Testing 216.198.79.193

Pinging 216.198.79.193 with 32 bytes of data:
Reply from 216.198.79.193: bytes=32 time=11ms TTL=250
Reply from 216.198.79.193: bytes=32 time=11ms TTL=250
Reply from 216.198.79.193: bytes=32 time=11ms TTL=250
Reply from 216.198.79.193: bytes=32 time=11ms TTL=250

Ping statistics for 216.198.79.193:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms
±--------------------------------------

±--------------------------------------
±------ Testing 64.29.17.1

Pinging 64.29.17.1 with 32 bytes of data:
Reply from 64.29.17.1: bytes=32 time=11ms TTL=250
Reply from 64.29.17.1: bytes=32 time=11ms TTL=250
Reply from 64.29.17.1: bytes=32 time=11ms TTL=250
Reply from 64.29.17.1: bytes=32 time=13ms TTL=250

Ping statistics for 64.29.17.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 13ms, Average = 11ms
±--------------------------------------

±--------------------------------------
±------ Testing 64.29.17.65

Pinging 64.29.17.65 with 32 bytes of data:
Reply from 64.29.17.65: bytes=32 time=12ms TTL=250
Reply from 64.29.17.65: bytes=32 time=12ms TTL=250
Reply from 64.29.17.65: bytes=32 time=11ms TTL=250
Reply from 64.29.17.65: bytes=32 time=11ms TTL=250

Ping statistics for 64.29.17.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
±--------------------------------------

±--------------------------------------
±------ Testing 64.29.17.129

Pinging 64.29.17.129 with 32 bytes of data:
Reply from 64.29.17.129: bytes=32 time=11ms TTL=250
Reply from 64.29.17.129: bytes=32 time=10ms TTL=250
Reply from 64.29.17.129: bytes=32 time=10ms TTL=250
Reply from 64.29.17.129: bytes=32 time=10ms TTL=250

Ping statistics for 64.29.17.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms
±--------------------------------------

±--------------------------------------
±------ Testing 64.29.17.193

Pinging 64.29.17.193 with 32 bytes of data:
Reply from 64.29.17.193: bytes=32 time=11ms TTL=250
Reply from 64.29.17.193: bytes=32 time=11ms TTL=250
Reply from 64.29.17.193: bytes=32 time=12ms TTL=250
Reply from 64.29.17.193: bytes=32 time=11ms TTL=250

Ping statistics for 64.29.17.193:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
±--------------------------------------

±--------------------------------------
±------ nslookup debug saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app

Got answer:
HEADER:
opcode = QUERY, id = 1, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0, additional = 0

QUESTIONS:
1.1.168.192.in-addr.arpa, type = PTR, class = IN
ANSWERS:
->  1.1.168.192.in-addr.arpa
name = home
ttl = 0 (0 secs)

Server: home
Address: 192.168.1.1

Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0

QUESTIONS:
saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app.home, type = A, class = IN

Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0

QUESTIONS:
saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app.home, type = AAAA, class = IN

Got answer:
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0, additional = 0

QUESTIONS:
saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app, type = A, class = IN
ANSWERS:
->  saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app
internet address = 175.139.142.25
ttl = 0 (0 secs)

Got answer:
HEADER:
opcode = QUERY, id = 5, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0

QUESTIONS:
saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app, type = AAAA, class = IN

Name: saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app
Address: 175.139.142.25

±--------------------------------------

±--------------------------------------
±------ nslookup saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app via 8.8.8.8

Server: dns.google
Address: 8.8.8.8

Name: saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app
Addresses: 64.29.17.193
216.198.79.193

±--------------------------------------

±--------------------------------------
±------ Output of saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app

Host saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app:443 was resolved.
IPv6: (none)
IPv4: 175.139.142.25
Trying 175.139.142.25:443…
connect to 175.139.142.25 port 443 from 0.0.0.0 port 54912 failed: Timed out
Failed to connect to saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app port 443 after 21052 ms: Could not connect to server
closing connection #0

±--------------------------------------

±--------------------------------------
| Time elapsed: 00:01:29.9924164 seconds
|
±------ FINISHED
±--------------------------------------

File can be found at C:\Users\p3dro\vercel-debug.txt

alkhaiiri · June 12, 2025, 2:34pm

Happening also on my website, cannot access in Malaysia.

pawlean · June 12, 2025, 3:46pm

Hey, Eycis!

Your site is not resolving to Vercel and you can see in the curl that you’re hitting Cloudflare’s servers, so you need to speak to Cloudflare.

lintps-6482 · June 15, 2025, 9:36am

Dear Pauline,

Is it only req to copy and paste this test “Invoke-RestMethod -Uri https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.ps1 | Invoke-Expression | tee vercel-debug.txt” in cmd ?

It is showing after using it in cmd

How to do? Please help me. It is not output vercel-debug.text.

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	101	August 14, 2024
Vercel's IP is blacklisted and inaccessible from some ISPs Help domains	2	111	October 17, 2024
IP blocked Help	7	113	August 22, 2024
Possible IP Block After Load Testing on Our Vercel Domain Help firewall	3	39	August 2, 2024
I can open the website with VPN turned on, but I can't open it with VPN turned off Help react	4	62	December 12, 2024

Resolving IP Blocking Issues

Related topics