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!
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?
Vercel Alum
Hi ,
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!
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!
Vercel Alum
Hi, !
Did you follow the steps above?
Hi ,
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
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
└───────────────────────────────────────
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
└───────────────────────────────────────
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
└───────────────────────────────────────
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
└───────────────────────────────────────
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
└───────────────────────────────────────
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
└───────────────────────────────────────
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
└───────────────────────────────────────
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
└───────────────────────────────────────
┌───────────────────────────────────────
├─────── 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
└───────────────────────────────────────
Vercel Staff
. 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.
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
1Domain to test (e.g. example.com): 2┌───────────────────────────────────────3├─────── STARTING4│5│ Domain to test: videoo.ai 6│ Timestamp (UTC): Wed Dec 11 06:05:15 UTC 20247| Timestamp (Local): Wed Dec 11 10:05:15 +04 20248└───────────────────────────────────────910┌───────────────────────────────────────11├─────── IP Information 1213{14 "ip": "87.20.79.79",15 "city": "Dubai",16 "region": "Dubai",17 "country": "AE",18 "loc": "25.0772,55.3093",19 "org": "AS15802 Emirates Integrated Telecommunications Company PJSC",20 "postal": "28506 74783",21 "timezone": "Asia/Dubai",22 "readme": "https://ipinfo.io/missingauth"23}24└───────────────────────────────────────2526┌───────────────────────────────────────27├─────── Testing 76.76.21.21 2829PING 76.76.21.21 (76.76.21.21): 56 data bytes3064 bytes from 76.76.21.21: icmp_seq=0 ttl=246 time=11.081 ms3164 bytes from 76.76.21.21: icmp_seq=1 ttl=246 time=9.705 ms3264 bytes from 76.76.21.21: icmp_seq=2 ttl=246 time=10.168 ms3364 bytes from 76.76.21.21: icmp_seq=3 ttl=246 time=9.904 ms3435--- 76.76.21.21 ping statistics ---364 packets transmitted, 4 packets received, 0.0% packet loss37round-trip min/avg/max/stddev = 9.705/10.215/11.081/0.527 ms3839 1 linksys02200 (192.168.1.1) 4.263 ms 2.675 ms 2.070 ms40 2 192.168.70.1 (192.168.70.1) 3.374 ms 3.380 ms 3.165 ms41 3 * * *42 4 10.100.136.154 (10.100.136.154) 9.629 ms 8.289 ms 7.862 ms43 5 10.100.35.78 (10.100.35.78) 8.444 ms 9.112 ms 9.188 ms44 6 10.53.17.77 (10.53.17.77) 10.037 ms 11.737 ms 10.039 ms45 7 * * *46 8 * * *47 9 * * *4810 * * *4911 52.93.68.81 (52.93.68.81) 11.790 ms 10.603 ms 9.884 ms5012 52.93.68.48 (52.93.68.48) 11.550 ms 10.195 ms 75.737 ms5113 76.76.21.21 (76.76.21.21) 13.481 ms 8.705 ms 8.627 ms52└───────────────────────────────────────5354┌───────────────────────────────────────55├─────── Testing 76.76.21.9 5657PING 76.76.21.9 (76.76.21.9): 56 data bytes5864 bytes from 76.76.21.9: icmp_seq=0 ttl=246 time=11.135 ms5964 bytes from 76.76.21.9: icmp_seq=1 ttl=246 time=11.280 ms6064 bytes from 76.76.21.9: icmp_seq=2 ttl=246 time=11.260 ms6164 bytes from 76.76.21.9: icmp_seq=3 ttl=246 time=11.737 ms6263--- 76.76.21.9 ping statistics ---644 packets transmitted, 4 packets received, 0.0% packet loss65round-trip min/avg/max/stddev = 11.135/11.353/11.737/0.229 ms66└───────────────────────────────────────6768┌───────────────────────────────────────69├─────── Testing 76.76.21.22 7071PING 76.76.21.22 (76.76.21.22): 56 data bytes7264 bytes from 76.76.21.22: icmp_seq=0 ttl=246 time=12.872 ms7364 bytes from 76.76.21.22: icmp_seq=1 ttl=246 time=11.969 ms7464 bytes from 76.76.21.22: icmp_seq=2 ttl=246 time=12.372 ms7564 bytes from 76.76.21.22: icmp_seq=3 ttl=246 time=11.993 ms7677--- 76.76.21.22 ping statistics ---784 packets transmitted, 4 packets received, 0.0% packet loss79round-trip min/avg/max/stddev = 11.969/12.302/12.872/0.366 ms80└───────────────────────────────────────8182┌───────────────────────────────────────83├─────── Testing 76.76.21.61 8485PING 76.76.21.61 (76.76.21.61): 56 data bytes8664 bytes from 76.76.21.61: icmp_seq=0 ttl=246 time=12.010 ms8764 bytes from 76.76.21.61: icmp_seq=1 ttl=246 time=11.846 ms8864 bytes from 76.76.21.61: icmp_seq=2 ttl=246 time=12.027 ms8964 bytes from 76.76.21.61: icmp_seq=3 ttl=246 time=11.571 ms9091--- 76.76.21.61 ping statistics ---924 packets transmitted, 4 packets received, 0.0% packet loss93round-trip min/avg/max/stddev = 11.571/11.864/12.027/0.183 ms94└───────────────────────────────────────9596┌───────────────────────────────────────97├─────── Testing 76.76.21.93 9899PING 76.76.21.93 (76.76.21.93): 56 data bytes10064 bytes from 76.76.21.93: icmp_seq=0 ttl=246 time=13.421 ms10164 bytes from 76.76.21.93: icmp_seq=1 ttl=246 time=15.036 ms10264 bytes from 76.76.21.93: icmp_seq=2 ttl=246 time=12.916 ms10364 bytes from 76.76.21.93: icmp_seq=3 ttl=246 time=12.602 ms104105--- 76.76.21.93 ping statistics ---1064 packets transmitted, 4 packets received, 0.0% packet loss107round-trip min/avg/max/stddev = 12.602/13.494/15.036/0.937 ms108└───────────────────────────────────────109110┌───────────────────────────────────────111├─────── Testing 76.76.21.98 112113PING 76.76.21.98 (76.76.21.98): 56 data bytes11464 bytes from 76.76.21.98: icmp_seq=0 ttl=246 time=13.278 ms11564 bytes from 76.76.21.98: icmp_seq=1 ttl=246 time=12.964 ms11664 bytes from 76.76.21.98: icmp_seq=2 ttl=246 time=12.242 ms11764 bytes from 76.76.21.98: icmp_seq=3 ttl=246 time=13.496 ms118119--- 76.76.21.98 ping statistics ---1204 packets transmitted, 4 packets received, 0.0% packet loss121round-trip min/avg/max/stddev = 12.242/12.995/13.496/0.474 ms122└───────────────────────────────────────123124┌───────────────────────────────────────125├─────── Testing 76.76.21.123 126127PING 76.76.21.123 (76.76.21.123): 56 data bytes12864 bytes from 76.76.21.123: icmp_seq=0 ttl=246 time=11.871 ms12964 bytes from 76.76.21.123: icmp_seq=1 ttl=246 time=11.028 ms13064 bytes from 76.76.21.123: icmp_seq=2 ttl=246 time=12.689 ms13164 bytes from 76.76.21.123: icmp_seq=3 ttl=246 time=12.899 ms132133--- 76.76.21.123 ping statistics ---1344 packets transmitted, 4 packets received, 0.0% packet loss135round-trip min/avg/max/stddev = 11.028/12.122/12.899/0.739 ms136└───────────────────────────────────────137138┌───────────────────────────────────────139├─────── Testing 76.76.21.142 140141PING 76.76.21.142 (76.76.21.142): 56 data bytes14264 bytes from 76.76.21.142: icmp_seq=0 ttl=246 time=10.898 ms14364 bytes from 76.76.21.142: icmp_seq=1 ttl=246 time=10.194 ms14464 bytes from 76.76.21.142: icmp_seq=2 ttl=246 time=10.652 ms14564 bytes from 76.76.21.142: icmp_seq=3 ttl=246 time=9.634 ms146147--- 76.76.21.142 ping statistics ---1484 packets transmitted, 4 packets received, 0.0% packet loss149round-trip min/avg/max/stddev = 9.634/10.345/10.898/0.482 ms150└───────────────────────────────────────151152┌───────────────────────────────────────153├─────── Testing 76.76.21.164 154155PING 76.76.21.164 (76.76.21.164): 56 data bytes15664 bytes from 76.76.21.164: icmp_seq=0 ttl=246 time=13.552 ms15764 bytes from 76.76.21.164: icmp_seq=1 ttl=246 time=13.610 ms15864 bytes from 76.76.21.164: icmp_seq=2 ttl=246 time=12.893 ms15964 bytes from 76.76.21.164: icmp_seq=3 ttl=246 time=13.365 ms160161--- 76.76.21.164 ping statistics ---1624 packets transmitted, 4 packets received, 0.0% packet loss163round-trip min/avg/max/stddev = 12.893/13.355/13.610/0.282 ms164└───────────────────────────────────────165166┌───────────────────────────────────────167├─────── Testing 76.76.21.241 168169PING 76.76.21.241 (76.76.21.241): 56 data bytes17064 bytes from 76.76.21.241: icmp_seq=0 ttl=246 time=13.885 ms17164 bytes from 76.76.21.241: icmp_seq=1 ttl=246 time=11.831 ms17264 bytes from 76.76.21.241: icmp_seq=2 ttl=246 time=11.723 ms17364 bytes from 76.76.21.241: icmp_seq=3 ttl=246 time=11.495 ms174175--- 76.76.21.241 ping statistics ---1764 packets transmitted, 4 packets received, 0.0% packet loss177round-trip min/avg/max/stddev = 11.495/12.233/13.885/0.961 ms178└───────────────────────────────────────179180┌───────────────────────────────────────181├─────── dig videoo.ai 182183184; <<>> DiG 9.10.6 <<>> videoo.ai185;; global options: +cmd186;; Got answer:187;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47961188;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 2189190;; OPT PSEUDOSECTION:191; EDNS: version: 0, flags:; udp: 1220192;; QUESTION SECTION:193;videoo.ai. IN A194195;; ADDITIONAL SECTION:196infoblox-base.rpz.infoblox.local. 900 IN SOA ns1-rpz.csp.infoblox.com. support.infoblox.com. 1733895357 900 300 2592001 900197198;; Query time: 33 msec199;; SERVER: 192.168.1.1#53(192.168.1.1)200;; WHEN: Wed Dec 11 10:06:01 +04 2024201;; MSG SIZE rcvd: 138202203└───────────────────────────────────────204205┌───────────────────────────────────────206├─────── dig videoo.ai via 8.8.8.8207208209; <<>> DiG 9.10.6 <<>> videoo.ai @8.8.8.8210;; global options: +cmd211;; Got answer:212;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10765213;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1214215;; OPT PSEUDOSECTION:216; EDNS: version: 0, flags:; udp: 512217;; QUESTION SECTION:218;videoo.ai. IN A219220;; ANSWER SECTION:221videoo.ai. 1800 IN A 76.76.21.93222videoo.ai. 1800 IN A 76.76.21.98223224;; Query time: 274 msec225;; SERVER: 8.8.8.8#53(8.8.8.8)226;; WHEN: Wed Dec 11 10:06:01 +04 2024227;; MSG SIZE rcvd: 70228229└───────────────────────────────────────230231┌───────────────────────────────────────232├─────── dig videoo.ai via trace233234235; <<>> DiG 9.10.6 <<>> videoo.ai +trace236;; global options: +cmd237;; connection timed out; no servers could be reached238└───────────────────────────────────────239240┌───────────────────────────────────────241├─────── Output of videoo.ai242243* Could not resolve host: videoo.ai244* Closing connection245246└───────────────────────────────────────247248249┌───────────────────────────────────────250│ Time elapsed: 61 seconds251│252├─────── FINISHED253└───────────────────────────────────────254255256257File can be found at /Users/ash/vercel-debug.txt258259
Also, I've already asked my ISP and they said they don't know and I should "just restart the router".
reply to #10
If I understand this right, there is no way to get help about this issue unless you are on a paid Vercel plan, right?
Vercel Alum
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.
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.
(edited)
I am here in Lima, Peru, developing a project for which I have chosen Vercel as my frontend platform. I have not yet purchased a plan because I am in the early testing stage. Today I have not been able to connect to my project or even to vercel.com. This has only happened today, until yesterday everything was fine. My IP is 190.236.202.175, I recently restarted the router. I had some errors with CORS, I have also tried to test the assignment of a domain to my project without results, but it was just a test, I still have time for that. The other unusual thing that happened yesterday is that I connected for a few hours to an external VPN.
Today I could not connect to vercel.com anymore. I hope you can help me.
thanks
This is the result of the tests not complete because is a limit of 32k
1+---------------------------------------2+------- STARTING3|4| Domain to test: vercel.com 5| Timestamp (UTC): 03/01/2025 01:54:556| Timestamp (Local): 02/28/2025 20:54:557+---------------------------------------89+---------------------------------------10+------- IP Information 1112{13 "ip": "190.236.202.175",14 "city": "Lima",15 "region": "Lima Province",16 "country": "PE",17 "loc": "-12.0432,-77.0282",18 "org": "AS6147 Telefonica del Peru S.A.A.",19 "postal": "15001",20 "timezone": "America/Lima",21 "readme": "https://ipinfo.io/missingauth"22}2324+---------------------------------------2526+---------------------------------------27+------- Testing 76.76.21.21 282930Haciendo ping a 76.76.21.21 con 32 bytes de datos:31Tiempo de espera agotado para esta solicitud.32Tiempo de espera agotado para esta solicitud.33Tiempo de espera agotado para esta solicitud.34Tiempo de espera agotado para esta solicitud.3536Estadísticas de ping para 76.76.21.21:37 Paquetes: enviados = 4, recibidos = 0, perdidos = 438 (100% perdidos),394041Traza a 76.76.21.21 sobre caminos de 30 saltos como máximo.4243 1 1 ms 1 ms 1 ms 192.168.1.1 44 2 7 ms 3 ms 5 ms 10.115.222.33 45 3 2 ms 1 ms 1 ms 10.115.7.124 46 4 7 ms 3 ms 2 ms 10.111.5.9 47 5 4 ms 4 ms 3 ms 84.16.7.226 48 6 * * * Tiempo de espera agotado para esta solicitud.49 7 * * * Tiempo de espera agotado para esta solicitud.50 8 * * * Tiempo de espera agotado para esta solicitud.51 9 * * * Tiempo de espera agotado para esta solicitud.52 10 * * * Tiempo de espera agotado para esta solicitud.53 11 * * * Tiempo de espera agotado para esta solicitud.54 12 * * * Tiempo de espera agotado para esta solicitud.55 13 * * * Tiempo de espera agotado para esta solicitud.56 14 * * * Tiempo de espera agotado para esta solicitud.57 15 * * * Tiempo de espera agotado para esta solicitud.58 16 * * * Tiempo de espera agotado para esta solicitud.59 17 * * * Tiempo de espera agotado para esta solicitud.60 18 * * * Tiempo de espera agotado para esta solicitud.61 19 * * * Tiempo de espera agotado para esta solicitud.62 20 * * * Tiempo de espera agotado para esta solicitud.63 21 * * * Tiempo de espera agotado para esta solicitud.64 22 * * * Tiempo de espera agotado para esta solicitud.65 23 * * * Tiempo de espera agotado para esta solicitud.66 24 * * * Tiempo de espera agotado para esta solicitud.67 25 * * * Tiempo de espera agotado para esta solicitud.68 26 * * * Tiempo de espera agotado para esta solicitud.69 27 * * * Tiempo de espera agotado para esta solicitud.70 28 * * * Tiempo de espera agotado para esta solicitud.71 29 * * * Tiempo de espera agotado para esta solicitud.72 30 * * * Tiempo de espera agotado para esta solicitud.7374Traza completa.75+---------------------------------------7677+---------------------------------------78+------- Testing 66.33.60.33 798081Haciendo ping a 66.33.60.33 con 32 bytes de datos:82Respuesta desde 66.33.60.33: bytes=32 tiempo=4ms TTL=24583Respuesta desde 66.33.60.33: bytes=32 tiempo=3ms TTL=24584Respuesta desde 66.33.60.33: bytes=32 tiempo=4ms TTL=24585Respuesta desde 66.33.60.33: bytes=32 tiempo=3ms TTL=2458687Estadísticas de ping para 66.33.60.33:88 Paquetes: enviados = 4, recibidos = 4, perdidos = 089 (0% perdidos),90Tiempos aproximados de ida y vuelta en milisegundos:91 Mínimo = 3ms, Máximo = 4ms, Media = 3ms92+---------------------------------------9394+---------------------------------------95+------- Testing 66.33.60.34 969798Haciendo ping a 66.33.60.34 con 32 bytes de datos:99Tiempo de espera agotado para esta solicitud.100Tiempo de espera agotado para esta solicitud.101Tiempo de espera agotado para esta solicitud.102Tiempo de espera agotado para esta solicitud.103104Estadísticas de ping para 66.33.60.34:105 Paquetes: enviados = 4, recibidos = 0, perdidos = 4106 (100% perdidos),107108109Traza a 66.33.60.34 sobre caminos de 30 saltos como máximo.110111 1 1 ms 1 ms <1 ms 192.168.1.1 112 2 3 ms 2 ms 2 ms 10.115.222.33 113 3 2 ms 2 ms 2 ms 10.115.7.124 114 4 2 ms 2 ms 2 ms 10.111.5.9 115 5 3 ms 3 ms 31 ms 84.16.7.226 116 6 * * * Tiempo de espera agotado para esta solicitud.117 7 * * * Tiempo de espera agotado para esta solicitud.118 8 * * * Tiempo de espera agotado para esta solicitud.119 9 * * * Tiempo de espera agotado para esta solicitud.120 10 * * * Tiempo de espera agotado para esta solicitud.121 11 * * * Tiempo de espera agotado para esta solicitud.122 12 * * * Tiempo de espera agotado para esta solicitud.123 13 * * * Tiempo de espera agotado para esta solicitud.124 14 * * * Tiempo de espera agotado para esta solicitud.125 15 * * * Tiempo de espera agotado para esta solicitud.126 16 * * * Tiempo de espera agotado para esta solicitud.127 17 * * * Tiempo de espera agotado para esta solicitud.128 18 * * * Tiempo de espera agotado para esta solicitud.129 19 * * * Tiempo de espera agotado para esta solicitud.130 20 * * * Tiempo de espera agotado para esta solicitud.131 21 * * * Tiempo de espera agotado para esta solicitud.132 22 * * * Tiempo de espera agotado para esta solicitud.133 23 * * * Tiempo de espera agotado para esta solicitud.134 24 * * * Tiempo de espera agotado para esta solicitud.135 25 * * * Tiempo de espera agotado para esta solicitud.136 26 * * * Tiempo de espera agotado para esta solicitud.137 27 * * * Tiempo de espera agotado para esta solicitud.138 28 * * * Tiempo de espera agotado para esta solicitud.139 29 * * * Tiempo de espera agotado para esta solicitud.140 30 * * * Tiempo de espera agotado para esta solicitud.141142Traza completa.143+---------------------------------------144145+---------------------------------------146+------- Testing 66.33.60.35 147148149Haciendo ping a 66.33.60.35 con 32 bytes de datos:150Tiempo de espera agotado para esta solicitud.151Tiempo de espera agotado para esta solicitud.152Tiempo de espera agotado para esta solicitud.153Tiempo de espera agotado para esta solicitud.154155Estadísticas de ping para 66.33.60.35:156 Paquetes: enviados = 4, recibidos = 0, perdidos = 4157 (100% perdidos),158159160Traza a 66.33.60.35 sobre caminos de 30 saltos como máximo.161162 1 85 ms 2 ms 1 ms 192.168.1.1 163 2 3 ms 2 ms 2 ms 10.115.222.33 164 3 2 ms 2 ms 2 ms 10.115.7.124 165 4 2 ms 2 ms 2 ms 10.111.5.9 166 5 4 ms 3 ms 3 ms 84.16.7.226 167 6 * * * Tiempo de espera agotado para esta solicitud.168 7 * * * Tiempo de espera agotado para esta solicitud.169 8 * * * Tiempo de espera agotado para esta solicitud.170 9 * * * Tiempo de espera agotado para esta solicitud.171 10 * * * Tiempo de espera agotado para esta solicitud.172 11 * * * Tiempo de espera agotado para esta solicitud.173 12 * * * Tiempo de espera agotado para esta solicitud.174 13 * * * Tiempo de espera agotado para esta solicitud.175 14 * * * Tiempo de espera agotado para esta solicitud.176 15 * * * Tiempo de espera agotado para esta solicitud.177 16 * * * Tiempo de espera agotado para esta solicitud.178 17 * * * Tiempo de espera agotado para esta solicitud.179 18 * * * Tiempo de espera agotado para esta solicitud.180 19 * * * Tiempo de espera agotado para esta solicitud.181 20 * * * Tiempo de espera agotado para esta solicitud.182 21 * * * Tiempo de espera agotado para esta solicitud.183 22 * * * Tiempo de espera agotado para esta solicitud.184 23 * * * Tiempo de espera agotado para esta solicitud.185 24 * * * Tiempo de espera agotado para esta solicitud.186 25 * * * Tiempo de espera agotado para esta solicitud.187 26 * * * Tiempo de espera agotado para esta solicitud.188 27 * * * Tiempo de espera agotado para esta solicitud.189 28 * * * Tiempo de espera agotado para esta solicitud.190 29 * * * Tiempo de espera agotado para esta solicitud.191 30 * * * Tiempo de espera agotado para esta solicitud.192193Traza completa.194+---------------------------------------195196+---------------------------------------197+------- Testing 66.33.60.65 198199200Haciendo ping a 66.33.60.65 con 32 bytes de datos:201Tiempo de espera agotado para esta solicitud.202Tiempo de espera agotado para esta solicitud.203Tiempo de espera agotado para esta solicitud.204Tiempo de espera agotado para esta solicitud.205206Estadísticas de ping para 66.33.60.65:207 Paquetes: enviados = 4, recibidos = 0, perdidos = 4208 (100% perdidos),209210211Traza a 66.33.60.65 sobre caminos de 30 saltos como máximo.212213 1 <1 ms 1 ms 1 ms 192.168.1.1 214 2 4 ms 2 ms 2 ms 10.115.222.33 215 3 2 ms 2 ms 2 ms 10.115.7.124 216 4 3 ms 2 ms 3 ms 10.111.5.9 217 5 3 ms 2 ms 3 ms 84.16.7.226 218 6 * * * Tiempo de espera agotado para esta solicitud.219 7 * * * Tiempo de espera agotado para esta solicitud.220 8 * * * Tiempo de espera agotado para esta solicitud.221 9 * * * Tiempo de espera agotado para esta solicitud.222 10 * * * Tiempo de espera agotado para esta solicitud.223 11 * * * Tiempo de espera agotado para esta solicitud.224 12 * * * Tiempo de espera agotado para esta solicitud.225 13 * * * Tiempo de espera agotado para esta solicitud.226 14 * * * Tiempo de espera agotado para esta solicitud.227 15 * * * Tiempo de espera agotado para esta solicitud.228 16 * * * Tiempo de espera agotado para esta solicitud.229 17 * * * Tiempo de espera agotado para esta solicitud.230 18 * * * Tiempo de espera agotado para esta solicitud.231 19 * * * Tiempo de espera agotado para esta solicitud.232 20 * * * Tiempo de espera agotado para esta solicitud.233 21 * * * Tiempo de espera agotado para esta solicitud.234 22 * * * Tiempo de espera agotado para esta solicitud.235 23 * * * Tiempo de espera agotado para esta solicitud.236 24 * * * Tiempo de espera agotado para esta solicitud.237 25 * * * Tiempo de espera agotado para esta solicitud.238 26 * * * Tiempo de espera agotado para esta solicitud.239 27 * * * Tiempo de espera agotado para esta solicitud.240 28 * * * Tiempo de espera agotado para esta solicitud.241 29 * * * Tiempo de espera agotado para esta solicitud.242 30 * * * Tiempo de espera agotado para esta solicitud.243244Traza completa.245+---------------------------------------246247+---------------------------------------248+------- Testing 66.33.60.66 249250251Haciendo ping a 66.33.60.66 con 32 bytes de datos:252Tiempo de espera agotado para esta solicitud.253Tiempo de espera agotado para esta solicitud.254Tiempo de espera agotado para esta solicitud.255Tiempo de espera agotado para esta solicitud.256257Estadísticas de ping para 66.33.60.66:258 Paquetes: enviados = 4, recibidos = 0, perdidos = 4259 (100% perdidos),260261262Traza a 66.33.60.66 sobre caminos de 30 saltos como máximo.263264 1 1 ms 1 ms 1 ms 192.168.1.1 265 2 5 ms 3 ms 7 ms 10.115.222.33 266 3 3 ms 1 ms 2 ms 10.115.7.124 267 4 34 ms 4 ms 2 ms 10.111.5.9 268 5 4 ms 4 ms 3 ms 84.16.7.226 269 6 * * * Tiempo de espera agotado para esta solicitud.270 7 * * * Tiempo de espera agotado para esta solicitud.271 8 * * * Tiempo de espera agotado para esta solicitud.272 9 * * * Tiempo de espera agotado para esta solicitud.273 10 * * * Tiempo de espera agotado para esta solicitud.274 11 * * * Tiempo de espera agotado para esta solicitud.275 12 * * * Tiempo de espera agotado para esta solicitud.276 13 * * * Tiempo de espera agotado para esta solicitud.277 14 * * * Tiempo de espera agotado para esta solicitud.278 15 * * * Tiempo de espera agotado para esta solicitud.279 16 * * * Tiempo de espera agotado para esta solicitud.280 17 * * * Tiempo de espera agotado para esta solicitud.281 18 * * * Tiempo de espera agotado para esta solicitud.282 19 * * * Tiempo de espera agotado para esta solicitud.283 20 * * * Tiempo de espera agotado para esta solicitud.284 21 * * * Tiempo de espera agotado para esta solicitud.285 22 * * * Tiempo de espera agotado para esta solicitud.286 23 * * * Tiempo de espera agotado para esta solicitud.287 24 * * * Tiempo de espera agotado para esta solicitud.288 25 * * * Tiempo de espera agotado para esta solicitud.289 26 * * * Tiempo de espera agotado para esta solicitud.290 27 * * * Tiempo de espera agotado para esta solicitud.291 28 * * * Tiempo de espera agotado para esta solicitud.292 29 * * * Tiempo de espera agotado para esta solicitud.293 30 * * * Tiempo de espera agotado para esta solicitud.294295Traza completa.296+---------------------------------------297298+---------------------------------------299+------- Testing 66.33.60.67 300301302Haciendo ping a 66.33.60.67 con 32 bytes de datos:303Tiempo de espera agotado para esta solicitud.304Tiempo de espera agotado para esta solicitud.305Tiempo de espera agotado para esta solicitud.306Tiempo de espera agotado para esta solicitud.307308Estadísticas de ping para 66.33.60.67:309 Paquetes: enviados = 4, recibidos = 0, perdidos = 4310 (100% perdidos),311312313Traza a 66.33.60.67 sobre caminos de 30 saltos como máximo.314315 1 1 ms 1 ms 1 ms 192.168.1.1 316 2 3 ms 3 ms 3 ms 10.115.222.33 317 3 25 ms 9 ms 3 ms 10.115.7.124 318 4 * 3 ms 2 ms 10.111.5.9 319 5 3 ms 3 ms 3 ms 84.16.7.226 320 6 * * * Tiempo de espera agotado para esta solicitud.321 7 * * * Tiempo de espera agotado para esta solicitud.322 8 * * * Tiempo de espera agotado para esta solicitud.323 9 * * * Tiempo de espera agotado para esta solicitud.324 10 * * * Tiempo de espera agotado para esta solicitud.325 11 * * * Tiempo de espera agotado para esta solicitud.326 12 * * * Tiempo de espera agotado para esta solicitud.327 13 * * * Tiempo de espera agotado para esta solicitud.328 14 * * * Tiempo de espera agotado para esta solicitud.329 15 * * * Tiempo de espera agotado para esta solicitud.330 16 * * * Tiempo de espera agotado para esta solicitud.331 17 * * * Tiempo de espera agotado para esta solicitud.332 18 * * * Tiempo de espera agotado para esta solicitud.333 19 * * * Tiempo de espera agotado para esta solicitud.334 20 * * * Tiempo de espera agotado para esta solicitud.335 21 * * * Tiempo de espera agotado para esta solicitud.336 22 * * * Tiempo de espera agotado para esta solicitud.337 23 * * * Tiempo de espera agotado para esta solicitud.338 24 * * * Tiempo de espera agotado para esta solicitud.339 25 * * * Tiempo de espera agotado para esta solicitud.340 26 * * * Tiempo de espera agotado para esta solicitud.341 27 * * * Tiempo de espera agotado para esta solicitud.342 28 * * * Tiempo de espera agotado para esta solicitud.343 29 * * * Tiempo de espera agotado para esta solicitud.344 30 * * * Tiempo de espera agotado para esta solicitud.345346Traza completa.347+---------------------------------------348349+---------------------------------------350+------- Testing 66.33.60.129 351352353Haciendo ping a 66.33.60.129 con 32 bytes de datos:354Tiempo de espera agotado para esta solicitud.355Tiempo de espera agotado para esta solicitud.356Tiempo de espera agotado para esta solicitud.357Tiempo de espera agotado para esta solicitud.358359Estadísticas de ping para 66.33.60.129:360 Paquetes: enviados = 4, recibidos = 0, perdidos = 4361 (100% perdidos),362363364Traza a 66.33.60.129 sobre caminos de 30 saltos como máximo.365366 1 2 ms 1 ms 3 ms 192.168.1.1 367 2 2 ms 3 ms 2 ms 10.115.222.33 368 3 2 ms 2 ms 2 ms 10.115.7.124 369 4 3 ms 2 ms 2 ms 10.111.5.9 370 5 4 ms 4 ms 3 ms 84.16.7.226 371 6 * * * Tiempo de espera agotado para esta solicitud.372 7 * * * Tiempo de espera agotado para esta solicitud.373 8 * * * Tiempo de espera agotado para esta solicitud.374 9 * * * Tiempo de espera agotado para esta solicitud.375 10 * * * Tiempo de espera agotado para esta solicitud.376 11 * * * Tiempo de espera agotado para esta solicitud.377 12 * * * Tiempo de espera agotado para esta solicitud.378 13 * * * Tiempo de espera agotado para esta solicitud.379 14 * * * Tiempo de espera agotado para esta solicitud.380 15 * * * Tiempo de espera agotado para esta solicitud.381 16 * * * Tiempo de espera agotado para esta solicitud.382 17 * * * Tiempo de espera agotado para esta solicitud.383 18 * * * Tiempo de espera agotado para esta solicitud.384 19 * * * Tiempo de espera agotado para esta solicitud.385 20 * * * Tiempo de espera agotado para esta solicitud.386 21 * * * Tiempo de espera agotado para esta solicitud.387 22 * * * Tiempo de espera agotado para esta solicitud.388 23 * * * Tiempo de espera agotado para esta solicitud.389 24 * * * Tiempo de espera agotado para esta solicitud.390 25 * * * Tiempo de espera agotado para esta solicitud.391 26 * * * Tiempo de espera agotado para esta solicitud.392 27 * * * Tiempo de espera agotado para esta solicitud.393 28 * * * Tiempo de espera agotado para esta solicitud.394 29 * * * Tiempo de espera agotado para esta solicitud.395 30 * * * Tiempo de espera agotado para esta solicitud.396397Traza completa.398+---------------------------------------399400+---------------------------------------401+------- Testing 66.33.60.130 402403404Haciendo ping a 66.33.60.130 con 32 bytes de datos:405Tiempo de espera agotado para esta solicitud.406Tiempo de espera agotado para esta solicitud.407Tiempo de espera agotado para esta solicitud.408Tiempo de espera agotado para esta solicitud.409410Estadísticas de ping para 66.33.60.130:411 Paquetes: enviados = 4, recibidos = 0, perdidos = 4412 (100% perdidos),413414415Traza a 66.33.60.130 sobre caminos de 30 saltos como máximo.416417 1 1 ms 1 ms 1 ms 192.168.1.1 418 2 3 ms 3 ms 6 ms 10.115.222.33 419 3 2 ms 3 ms 1 ms 10.115.7.124 420 4 27 ms 2 ms 2 ms 10.111.5.9 421 5 4 ms 3 ms 3 ms 84.16.7.226 422 6 * * * Tiempo de espera agotado para esta solicitud.423 7 * * * Tiempo de espera agotado para esta solicitud.424 8 * * * Tiempo de espera agotado para esta solicitud.425 9 * * * Tiempo de espera agotado para esta solicitud.426 10 * * * Tiempo de espera agotado para esta solicitud.427 11 * * * Tiempo de espera agotado para esta solicitud.428 12 * * * Tiempo de espera agotado para esta solicitud.429 13 * * * Tiempo de espera agotado para esta solicitud.430 14 * * * Tiempo de espera agotado para esta solicitud.431 15 * * * Tiempo de espera agotado para esta solicitud.432 16 * * * Tiempo de espera agotado para esta solicitud.433 17 * * * Tiempo de espera agotado para esta solicitud.434 18 * * * Tiempo de espera agotado para esta solicitud.435 19 * * * Tiempo de espera agotado para esta solicitud.436 20 * * * Tiempo de espera agotado para esta solicitud.437 21 * * * Tiempo de espera agotado para esta solicitud.438 22 * * * Tiempo de espera agotado para esta solicitud.439 23 * * * Tiempo de espera agotado para esta solicitud.440 24 * * * Tiempo de espera agotado para esta solicitud.441 25 * * * Tiempo de espera agotado para esta solicitud.442 26 * * * Tiempo de espera agotado para esta solicitud.443 27 * * * Tiempo de espera agotado para esta solicitud.444 28 * * * Tiempo de espera agotado para esta solicitud.445 29 * * * Tiempo de espera agotado para esta solicitud.446 30 * * * Tiempo de espera agotado para esta solicitud.447448Traza completa.449+---------------------------------------450451+---------------------------------------452+------- Testing 66.33.60.193 453454455Haciendo ping a 66.33.60.193 con 32 bytes de datos:456Tiempo de espera agotado para esta solicitud.457Tiempo de espera agotado para esta solicitud.458Tiempo de espera agotado para esta solicitud.459Tiempo de espera agotado para esta solicitud.460461Estadísticas de ping para 66.33.60.193:462 Paquetes: enviados = 4, recibidos = 0, perdidos = 4463 (100% perdidos),464465466Traza a 66.33.60.193 sobre caminos de 30 saltos como máximo.467468 1 1 ms 1 ms 1 ms 192.168.1.1 469 2 3 ms 2 ms 2 ms 10.115.222.33 470 3 2 ms 1 ms 2 ms 10.115.7.124 471 4 5 ms 4 ms 3 ms 10.111.5.9 472 5 4 ms 3 ms 5 ms 84.16.7.226 473 6 * * * Tiempo de espera agotado para esta solicitud.474 7 * * * Tiempo de espera agotado para esta solicitud.475 8 * * * Tiempo de espera agotado para esta solicitud.476 9 * * * Tiempo de espera agotado para esta solicitud.477 10 * * * Tiempo de espera agotado para esta solicitud.478 11 * * * Tiempo de espera agotado para esta solicitud.479 12 * * * Tiempo de espera agotado para esta solicitud.480 13 * * * Tiempo de espera agotado para esta solicitud.481 14 * * * Tiempo de espera agotado para esta solicitud.482 15 * * * Tiempo de espera agotado para esta solicitud.483 16 * * * Tiempo de espera agotado para esta solicitud.484 17 * * * Tiempo de espera agotado para esta solicitud.485 18 * * * Tiempo de espera agotado para esta solicitud.486 19 * * * Tiempo de espera agotado para esta solicitud.487 20 * * * Tiempo de espera agotado para esta solicitud.488 21 * * * Tiempo de espera agotado para esta solicitud.489 22 * * * Tiempo de espera agotado para esta solicitud.490 23 * * * Tiempo de espera agotado para esta solicitud.491 24 * * * Tiempo de espera agotado para esta solicitud.492 25 * * * Tiempo de espera agotado para esta solicitud.493 26 * * * Tiempo de espera agotado para esta solicitud.494 27 * * * Tiempo de espera agotado para esta solicitud.495 28 * * * Tiempo de espera agotado para esta solicitud.496 29 * * * Tiempo de espera agotado para esta solicitud.497 30 * * * Tiempo de espera agotado para esta solicitud.498499Traza completa.500+---------------------------------------501502+---------------------------------------503+------- Testing 66.33.60.194 504505506Haciendo ping a 66.33.60.194 con 32 bytes de datos:507Tiempo de espera agotado para esta solicitud.508Tiempo de espera agotado para esta solicitud.509Tiempo de espera agotado para esta solicitud.510Tiempo de espera agotado para esta solicitud.511512Estadísticas de ping para 66.33.60.194:513 Paquetes: enviados = 4, recibidos = 0, perdidos = 4514 (100% perdidos),515516517Traza a 66.33.60.194 sobre caminos de 30 saltos como máximo.518519 1 2 ms 1 ms 1 ms 192.168.1.1 520 2 6 ms 10 ms 3 ms 10.115.222.33 521 3 6 ms 3 ms 4 ms 10.115.7.124 522 4 3 ms 2 ms 2 ms 10.111.5.9 523 5 4 ms 3 ms 4 ms 84.16.7.226 524 6 * * * Tiempo de espera agotado para esta solicitud.525 7 * * * Tiempo de espera agotado para esta solicitud.526 8 * * * Tiempo de espera agotado para esta solicitud.527 9 * * * Tiempo de espera agotado para esta solicitud.528 10 * * * Tiempo de espera agotado para esta solicitud.529 11 * * * Tiempo de espera agotado para esta solicitud.530 12 * * * Tiempo de espera agotado para esta solicitud.531 13 * * * Tiempo de espera agotado para esta solicitud.532 14 * * * Tiempo de espera agotado para esta solicitud.533 15 * * * Tiempo de espera agotado para esta solicitud.534 16 * * * Tiempo de espera agotado para esta solicitud.535 17 * * * Tiempo de espera agotado para esta solicitud.536 18 * * * Tiempo de espera agotado para esta solicitud.537 19 * * * Tiempo de espera agotado para esta solicitud.538 20 * * * Tiempo de espera agotado para esta solicitud.539 21 * * * Tiempo de espera agotado para esta solicitud.540 22 * * * Tiempo de espera agotado para esta solicitud.541 23 * * * Tiempo de espera agotado para esta solicitud.542 24 * * * Tiempo de espera agotado para esta solicitud.543 25 * * * Tiempo de espera agotado para esta solicitud.544 26 * * * Tiempo de espera agotado para esta solicitud.545 27 * * * Tiempo de espera agotado para esta solicitud.546 28 * * * Tiempo de espera agotado para esta solicitud.547 29 * * * Tiempo de espera agotado para esta solicitud.548 30 * * * Tiempo de espera agotado para esta solicitud.549550Traza completa.551+---------------------------------------552553+---------------------------------------554+------- Testing 76.76.21.9 555556557Haciendo ping a 76.76.21.9 con 32 bytes de datos:558Tiempo de espera agotado para esta solicitud.559Tiempo de espera agotado para esta solicitud.560Tiempo de espera agotado para esta solicitud.561Tiempo de espera agotado para esta solicitud.562
(edited)
this is the test results from another machine this a Macbook
1┌───────────────────────────────────────2├─────── STARTING3│4│ Domain to test: vercel.com 5│ Timestamp (UTC): Sat Mar 1 02:04:59 UTC 20256| Timestamp (Local): Fri Feb 28 21:04:59 -05 20257└───────────────────────────────────────89┌───────────────────────────────────────10├─────── IP Information 1112{13 "ip": "190.236.202.175",14 "city": "Lima",15 "region": "Lima Province",16 "country": "PE",17 "loc": "-12.0432,-77.0282",18 "org": "AS6147 Telefonica del Peru S.A.A.",19 "postal": "15001",20 "timezone": "America/Lima",21 "readme": "https://ipinfo.io/missingauth"22}23└───────────────────────────────────────2425┌───────────────────────────────────────26├─────── Testing 76.76.21.21 2728PING 76.76.21.21 (76.76.21.21): 56 data bytes29Request timeout for icmp_seq 030Request timeout for icmp_seq 131Request timeout for icmp_seq 23233--- 76.76.21.21 ping statistics ---344 packets transmitted, 0 packets received, 100.0% packet loss3536 1 192.168.1.1 (192.168.1.1) 10.871 ms 4.920 ms 3.674 ms37 2 10.115.222.33 (10.115.222.33) 10.047 ms 10.353 ms 6.634 ms38 3 10.115.7.124 (10.115.7.124) 4.758 ms 5.760 ms 8.949 ms39 4 10.111.5.9 (10.111.5.9) 4.948 ms 11.305 ms 4.611 ms40 5 84.16.7.226 (84.16.7.226) 5.530 ms 5.532 ms 5.038 ms41 6 * * *42 7 * * *43 8 * * *44 9 * * *4510 * * *4611 * * *4712 * * *4813 * * *4914 * * *5015 * * *5116 * * *5217 * * *5318 * * *5419 * * *5520 * * *5621 * * *5722 * * *5823 * * *5924 * * *6025 * * *6126 * * *6227 * * *6328 * * *6429 * * *6530 * * *66└───────────────────────────────────────6768┌───────────────────────────────────────69├─────── Testing 66.33.60.33 7071PING 66.33.60.33 (66.33.60.33): 56 data bytes7264 bytes from 66.33.60.33: icmp_seq=0 ttl=245 time=12.888 ms7364 bytes from 66.33.60.33: icmp_seq=1 ttl=245 time=13.465 ms7464 bytes from 66.33.60.33: icmp_seq=2 ttl=245 time=6.243 ms7564 bytes from 66.33.60.33: icmp_seq=3 ttl=245 time=8.384 ms7677--- 66.33.60.33 ping statistics ---784 packets transmitted, 4 packets received, 0.0% packet loss79round-trip min/avg/max/stddev = 6.243/10.245/13.465/3.035 ms80└───────────────────────────────────────8182┌───────────────────────────────────────83├─────── Testing 66.33.60.34 8485PING 66.33.60.34 (66.33.60.34): 56 data bytes86Request timeout for icmp_seq 087Request timeout for icmp_seq 188Request timeout for icmp_seq 28990--- 66.33.60.34 ping statistics ---914 packets transmitted, 0 packets received, 100.0% packet loss9293 1 192.168.1.1 (192.168.1.1) 11.553 ms 3.606 ms 3.883 ms94 2 10.115.222.33 (10.115.222.33) 5.879 ms 5.621 ms 7.227 ms95 3 10.115.7.124 (10.115.7.124) 4.779 ms 5.974 ms 5.107 ms96 4 10.111.5.9 (10.111.5.9) 5.210 ms 6.525 ms 5.358 ms97 5 84.16.7.226 (84.16.7.226) 6.457 ms 6.033 ms 6.138 ms98 6 * * *99 7 * * *100 8 * * *101 9 * * *10210 * * *10311 * * *10412 * * *10513 * * *10614 * * *10715 * * *10816 * * *10917 * * *11018 * * *11119 * * *11220 * * *11321 * * *11422 * * *11523 * * *11624 * * *11725 * * *11826 * * *11927 * * *12028 * * *12129 * * *12230 * * *123└───────────────────────────────────────124125┌───────────────────────────────────────126├─────── Testing 66.33.60.35 127128PING 66.33.60.35 (66.33.60.35): 56 data bytes129Request timeout for icmp_seq 0130Request timeout for icmp_seq 1131Request timeout for icmp_seq 2132133--- 66.33.60.35 ping statistics ---1344 packets transmitted, 0 packets received, 100.0% packet loss135136 1 192.168.1.1 (192.168.1.1) 27.996 ms 4.179 ms 3.815 ms137 2 10.115.222.33 (10.115.222.33) 5.205 ms 5.758 ms 5.119 ms138 3 10.115.7.124 (10.115.7.124) 4.296 ms 4.166 ms 4.081 ms139 4 10.111.5.9 (10.111.5.9) 6.029 ms 4.916 ms 4.710 ms140 5 84.16.7.226 (84.16.7.226) 5.186 ms 4.896 ms 5.765 ms141 6 * * *142 7 * * *143 8 * * *144 9 * * *14510 * * *14611 * * *14712 * * *14813 * * *14914 * * *15015 * * *15116 * * *15217 * * *15318 * * *15419 * * *15520 * * *15621 * * *15722 * * *15823 * * *15924 * * *16025 * * *16126 * * *16227 * * *16328 * * *16429 * * *16530 * * *166└───────────────────────────────────────167168┌───────────────────────────────────────169├─────── Testing 66.33.60.65 170171PING 66.33.60.65 (66.33.60.65): 56 data bytes172Request timeout for icmp_seq 0173Request timeout for icmp_seq 1174Request timeout for icmp_seq 2175176--- 66.33.60.65 ping statistics ---1774 packets transmitted, 0 packets received, 100.0% packet loss178179 1 192.168.1.1 (192.168.1.1) 8.267 ms 31.354 ms 3.590 ms180 2 10.115.222.33 (10.115.222.33) 7.660 ms 6.566 ms 5.238 ms181 3 10.115.7.124 (10.115.7.124) 17.713 ms 5.189 ms 5.197 ms182 4 10.111.5.9 (10.111.5.9) 4.972 ms 11.732 ms 4.445 ms183 5 84.16.7.226 (84.16.7.226) 5.306 ms 12.247 ms 5.382 ms184 6 * * *185 7 * * *186 8 * * *187 9 * * *18810 * * *18911 * * *19012 * * *19113 * * *19214 * * *19315 * * *19416 * * *19517 * * *19618 * * *19719 * * *19820 * * *19921 * * *20022 * * *20123 * * *20224 * * *20325 * * *20426 * * *20527 * * *20628 * * *20729 * * *20830 * * *209└───────────────────────────────────────210211┌───────────────────────────────────────212├─────── Testing 66.33.60.66 213214PING 66.33.60.66 (66.33.60.66): 56 data bytes215Request timeout for icmp_seq 0216Request timeout for icmp_seq 1217Request timeout for icmp_seq 2218219--- 66.33.60.66 ping statistics ---2204 packets transmitted, 0 packets received, 100.0% packet loss221222 1 192.168.1.1 (192.168.1.1) 5.814 ms 4.580 ms 3.855 ms223 2 10.115.222.33 (10.115.222.33) 8.642 ms 5.659 ms 7.902 ms224 3 10.115.7.124 (10.115.7.124) 26.933 ms 3.835 ms 5.108 ms225 4 10.111.5.9 (10.111.5.9) 4.504 ms 4.846 ms 3.753 ms226 5 84.16.7.226 (84.16.7.226) 5.400 ms 5.154 ms 5.199 ms227 6 * * *228 7 * * *229 8 * * *230 9 * * *23110 * * *23211 * * *23312 * * *23413 * * *23514 * * *23615 * * *23716 * * *23817 * * *23918 * * *24019 * * *24120 * * *24221 * * *24322 * * *24423 * * *24524 * * *24625 * * *24726 * * *24827 * * *24928 * * *25029 * * *25130 * * *252└───────────────────────────────────────253254┌───────────────────────────────────────255├─────── Testing 66.33.60.67 256257PING 66.33.60.67 (66.33.60.67): 56 data bytes258Request timeout for icmp_seq 0259Request timeout for icmp_seq 1260Request timeout for icmp_seq 2261262--- 66.33.60.67 ping statistics ---2634 packets transmitted, 0 packets received, 100.0% packet loss264265 1 192.168.1.1 (192.168.1.1) 12.831 ms 3.875 ms 4.103 ms266 2 10.115.222.33 (10.115.222.33) 5.613 ms 5.567 ms 6.187 ms267 3 10.115.7.124 (10.115.7.124) 5.148 ms 9.536 ms 5.060 ms268 4 10.111.5.9 (10.111.5.9) 31.720 ms 5.446 ms 7.844 ms269 5 84.16.7.226 (84.16.7.226) 5.194 ms 5.567 ms 6.020 ms270 6 * * *271 7 * * *272 8 * * *273 9 * * *27410 * * *27511 * * *27612 * * *27713 * * *27814 * * *27915 * * *28016 * * *28117 * * *28218 * * *28319 * * *28420 * * *28521 * * *28622 * * *28723 * * *28824 * * *28925 * * *29026 * * *29127 * * *29228 * * *29329 * * *29430 * * *295└───────────────────────────────────────296297┌───────────────────────────────────────298├─────── Testing 66.33.60.129 299300PING 66.33.60.129 (66.33.60.129): 56 data bytes301Request timeout for icmp_seq 0302Request timeout for icmp_seq 1303Request timeout for icmp_seq 2304305--- 66.33.60.129 ping statistics ---3064 packets transmitted, 0 packets received, 100.0% packet loss307308 1 192.168.1.1 (192.168.1.1) 10.971 ms 4.264 ms 4.146 ms309 2 10.115.222.33 (10.115.222.33) 5.477 ms 8.134 ms 6.626 ms310 3 10.115.7.124 (10.115.7.124) 5.517 ms 5.401 ms 5.558 ms311 4 10.111.5.9 (10.111.5.9) 5.869 ms 5.331 ms 3.748 ms312 5 84.16.7.226 (84.16.7.226) 5.639 ms * 11.966 ms313 6 * * *314 7 * * *315 8 * * *316 9 * * *31710 * * *31811 * * *31912 * * *32013 * * *32114 * * *32215 * * *32316 * * *32417 * * *32518 * * *32619 * * *32720 * * *32821 * * *32922 * * *33023 * * *33124 * * *33225 * * *33326 * * *33427 * * *33528 * * *33629 * * *33730 * * *338└───────────────────────────────────────339340┌───────────────────────────────────────341├─────── Testing 66.33.60.130 342343PING 66.33.60.130 (66.33.60.130): 56 data bytes344Request timeout for icmp_seq 0345Request timeout for icmp_seq 1346Request timeout for icmp_seq 2347348--- 66.33.60.130 ping statistics ---3494 packets transmitted, 0 packets received, 100.0% packet loss350351 1 192.168.1.1 (192.168.1.1) 20.884 ms 4.137 ms 3.923 ms352 2 10.115.222.33 (10.115.222.33) 6.427 ms 5.741 ms 7.848 ms353 3 10.115.7.124 (10.115.7.124) 5.160 ms 5.731 ms 4.889 ms354 4 10.111.5.9 (10.111.5.9) 8.129 ms 8.622 ms 10.218 ms355 5 84.16.7.226 (84.16.7.226) 5.513 ms 5.111 ms 5.445 ms356 6 * * *357 7 * * *358 8 * * *359 9 * * *36010 * * *36111 * * *36212 * * *36313 * * *36414 * * *36515 * * *36616 * * *36717 * * *36818 * * *36919 * * *37020 * * *37121 * * *37222 * * *37323 * * *37424 * * *37525 * * *37626 * * *37727 * * *37828 * * *37929 * * *38030 * * *381└───────────────────────────────────────382383┌───────────────────────────────────────384├─────── Testing 66.33.60.193 385386PING 66.33.60.193 (66.33.60.193): 56 data bytes387Request timeout for icmp_seq 0388Request timeout for icmp_seq 1389Request timeout for icmp_seq 2390391--- 66.33.60.193 ping statistics ---3924 packets transmitted, 0 packets received, 100.0% packet loss393394 1 192.168.1.1 (192.168.1.1) 8.172 ms 3.862 ms 3.933 ms395 2 10.115.222.33 (10.115.222.33) 6.004 ms 12.120 ms 6.759 ms396 3 10.115.7.124 (10.115.7.124) 5.576 ms 5.178 ms 4.902 ms397 4 10.111.5.9 (10.111.5.9) 5.437 ms 5.389 ms 4.463 ms398 5 84.16.7.226 (84.16.7.226) 5.464 ms 5.423 ms 5.327 ms399 6 * * *400 7 * * *401 8 * * *402 9 * * *40310 * * *40411 * * *40512 * * *40613 * * *40714 * * *40815 * * *40916 * * *41017 * * *41118 * * *41219 * * *41320 * * *41421 * * *41522 * * *41623 * * *41724 * * *41825 * * *41926 * * *42027 * * *42128 * * *42229 * * *42330 * * *424└───────────────────────────────────────425426┌───────────────────────────────────────427├─────── Testing 66.33.60.194 428429PING 66.33.60.194 (66.33.60.194): 56 data bytes430Request timeout for icmp_seq 0431Request timeout for icmp_seq 1432Request timeout for icmp_seq 2433434--- 66.33.60.194 ping statistics ---4354 packets transmitted, 0 packets received, 100.0% packet loss436437 1 192.168.1.1 (192.168.1.1) 11.020 ms 3.626 ms 3.871 ms438 2 10.115.222.33 (10.115.222.33) 7.902 ms 6.265 ms 4.748 ms439 3 10.115.7.124 (10.115.7.124) 4.210 ms 5.178 ms 4.673 ms440 4 10.111.5.9 (10.111.5.9) 5.664 ms 4.664 ms 5.261 ms441 5 84.16.7.226 (84.16.7.226) 5.820 ms 6.448 ms 5.990 ms442 6 * * *443 7 * * *444 8 * * *445 9 * * *44610 * * *44711 * * *44812 * * *44913 * * *45014 * * *45115 * * *45216 * * *45317 * * *45418 * * *45519 * * *45620 * * *45721 * * *45822 * * *45923 * * *46024 * * *46125 * * *46226 * * *46327 * * *46428 * * *46529 * * *46630 * * *467└───────────────────────────────────────468469┌───────────────────────────────────────470├─────── Testing 76.76.21.9 471472PING 76.76.21.9 (76.76.21.9): 56 data bytes473Request timeout for icmp_seq 0474Request timeout for icmp_seq 1475Request timeout for icmp_seq 2476477--- 76.76.21.9 ping statistics ---4784 packets transmitted, 0 packets received, 100.0% packet loss479480 1 192.168.1.1 (192.168.1.1) 405.671 ms 3.831 ms 3.912 ms481 2 10.115.222.33 (10.115.222.33) 5.736 ms 6.183 ms 5.562 ms482 3 10.115.7.124 (10.115.7.124) 5.115 ms 5.181 ms 5.265 ms483 4 10.111.5.9 (10.111.5.9) 58.644 ms 5.569 ms 7.270 ms484 5 84.16.7.226 (84.16.7.226) 6.463 ms 6.020 ms 5.870 ms485 6 * * *486 7 * * *487 8 * * *488 9 * * *48910 * * *49011 * * *49112 * * *49213 * * *49314 * * *49415 * * *49516 * * *49617 * * *49718 * * *49819 * * *49920 * * *50021 * * *50122 * * *50223 * * *50324 * * *50425 * * *50526 * * *50627 * * *50728 * * *50829 * * *50930 * * *510└───────────────────────────────────────511512┌───────────────────────────────────────513├─────── Testing 76.76.21.22 514515PING 76.76.21.22 (76.76.21.22): 56 data bytes516Request timeout for icmp_seq 0517Request timeout for icmp_seq 1518Request timeout for icmp_seq 2519520--- 76.76.21.22 ping statistics ---5214 packets transmitted, 0 packets received, 100.0% packet loss522523 1 192.168.1.1 (192.168.1.1) 10.123 ms 3.762 ms 3.704 ms524 2 10.115.222.33 (10.115.222.33) 6.415 ms 5.637 ms 4.877 ms525 3 10.115.7.124 (10.115.7.124) 5.205 ms 4.496 ms 4.974 ms526 4 10.111.5.9 (10.111.5.9) 5.447 ms 7.035 ms 23.752 ms527 5 84.16.7.226 (84.16.7.226) 5.626 ms 5.481 ms 5.432 ms528 6 * * *529 7 * * *530 8 * * *531 9 * * *53210 * * *53311 * * *53412 * * *53513 * * *53614 * * *53715 * * *53816 * * *53917 * * *54018 * * *54119 * * *54220 * * *54321 * * *54422 * * *54523 * * *54624 * * *54725 * * *54826 * * *54927 * * *55028 * * *55129 * * *55230 * * *553└───────────────────────────────────────554555┌───────────────────────────────────────556├─────── Testing 76.76.21.61 557558PING 76.76.21.61 (76.76.21.61): 56 data bytes559Request timeout for icmp_seq 0560Request timeout for icmp_seq 1561Request timeout for icmp_seq 2562563--- 76.76.21.61 ping statistics ---5644 packets transmitted, 0 packets received, 100.0% packet loss565566 1 192.168.1.1 (192.168.1.1) 10.597 ms 4.602 ms 4.642 ms567 2 10.115.222.33 (10.115.222.33) 5.550 ms 5.727 ms 7.784 ms568 3 10.115.7.124 (10.115.7.124) 5.190 ms 5.298 ms 4.694 ms569 4 10.111.5.9 (10.111.5.9) 5.642 ms 5.552 ms 4.330 ms570 5 84.16.7.226 (84.16.7.226) 5.531 ms 5.080 ms 4.805 ms571 6 * * *572 7 * * *573 8 * * *574 9 * * *57510 * * *57611 * * *57712 * * *57813 * * *57914 * * *58015 * * *58116 * * *58217 * * *58318 * * *58419 * * *58520 * * *58621 * * *58722 * * *58823 * * *58924 * * *59025 * * *59126 * * *59227 * * *59328 * * *59429 * * *59530 * * *596└───────────────────────────────────────597598┌───────────────────────────────────────599├─────── Testing 76.76.21.93 600601PING 76.76.21.93 (76.76.21.93): 56 data bytes602Request timeout for icmp_seq 0603Request timeout for icmp_seq 1604Request timeout for icmp_seq 2605606--- 76.76.21.93 ping statistics ---6074 packets transmitted, 0 packets received, 100.0% packet loss608609 1 192.168.1.1 (192.168.1.1) 4.631 ms 3.685 ms 3.636 ms610 2 10.115.222.33 (10.115.222.33) 5.684 ms 6.740 ms 5.963 ms611 3 10.115.7.124 (10.115.7.124) 6.216 ms 4.642 ms 5.024 ms612 4 10.111.5.9 (10.111.5.9) 5.461 ms 5.062 ms 5.035 ms613 5 84.16.7.226 (84.16.7.226) 6.207 ms 5.021 ms 5.538 ms614 6 * * *615 7 * * *616 8 * * *617 9 * * *61810 * * *61911 * * *62012 * * *62113 * * *62214 * * *62315 * * *62416 * * *62517 * * *62618 * * *62719 * * *62820 * * *62921 * * *63022 * * *63123 * * *63224 * * *63325 * * *63426 * * *63527 * * *63628 * * *63729 * * *63830 * * *639└───────────────────────────────────────640641┌───────────────────────────────────────642├─────── Testing 76.76.21.98 643644PING 76.76.21.98 (76.76.21.98): 56 data bytes645Request timeout for icmp_seq 0646Request timeout for icmp_seq 1647Request timeout for icmp_seq 2648649--- 76.76.21.98 ping statistics ---6504 packets transmitted, 0 packets received, 100.0% packet loss651652 1 192.168.1.1 (192.168.1.1) 10.313 ms 4.184 ms 3.971 ms653 2 10.115.222.33 (10.115.222.33) 9.028 ms 5.892 ms 5.717 ms654 3 10.115.7.124 (10.115.7.124) 5.666 ms 6.472 ms 4.773 ms655 4 10.111.5.9 (10.111.5.9) 5.325 ms 5.376 ms 4.214 ms656 5 84.16.7.226 (84.16.7.226) 6.515 ms 5.430 ms 5.862 ms657 6 * * *658 7 * * *659 8 * * *660 9 * * *66110 * * *66211 * * *66312 * * *66413 * * *66514 * * *66615 * * *66716 * * *66817 * * *66918 * * *67019 * * *67120 * * *67221 * * *67322 * * *67423 * * *67524 * * *67625 * * *67726 * * *67827 * * *67928 * * *68029 * * *68130 * * *682└───────────────────────────────────────683684┌───────────────────────────────────────685├─────── Testing 76.76.21.123 686687PING 76.76.21.123 (76.76.21.123): 56 data bytes688Request timeout for icmp_seq 0689Request timeout for icmp_seq 1690Request timeout for icmp_seq 2691692--- 76.76.21.123 ping statistics ---6934 packets transmitted, 0 packets received, 100.0% packet loss694695 1 192.168.1.1 (192.168.1.1) 3.975 ms 3.664 ms 3.933 ms696 2 10.115.222.33 (10.115.222.33) 6.718 ms 6.558 ms 5.741 ms697 3 10.115.7.124 (10.115.7.124) 4.314 ms 4.219 ms 5.035 ms698 4 10.111.5.9 (10.111.5.9) 7.197 ms 5.316 ms 4.269 ms699 5 84.16.7.226 (84.16.7.226) 5.590 ms 5.348 ms 5.337 ms700 6 * * *701 7 * * *702 8 * * *703 9 * * *70410 * * *70511 * * *70612 * * *70713 * * *70814 * * *70915 * * *71016 * * *71117 * * *71218 * * *71319 * * *71420 * * *71521 * * *71622 * * *71723 * * *71824 * * *71925 * * *72026 * * *72127 * * *72228 * * *72329 * * *72430 * * *725└───────────────────────────────────────726727┌───────────────────────────────────────728├─────── Testing 76.76.21.142 729730PING 76.76.21.142 (76.76.21.142): 56 data bytes731Request timeout for icmp_seq 0732Request timeout for icmp_seq 1733Request timeout for icmp_seq 2734735--- 76.76.21.142 ping statistics ---7364 packets transmitted, 0 packets received, 100.0% packet loss737738 1 192.168.1.1 (192.168.1.1) 10.344 ms 4.540 ms 3.789 ms739 2 10.115.222.33 (10.115.222.33) 5.826 ms 5.118 ms 5.776 ms740 3 10.115.7.124 (10.115.7.124) 5.457 ms 5.540 ms 6.229 ms741 4 10.111.5.9 (10.111.5.9) 8.111 ms 5.737 ms 5.078 ms742 5 84.16.7.226 (84.16.7.226) 5.907 ms 5.764 ms 6.319 ms743 6 * * *744 7 * * *745 8 * * *746 9 * * *74710 * * *74811 * * *74912 * * *75013 * * *75114 * * *75215 * * *75316 * * *75417 * * *75518 * * *75619 * * *75720 * * *75821 * * *75922 * * *76023 * * *76124 * * *76225 * * *76326 * * *76427 * * *76528 * * *76629 * * *76730 * * *768└───────────────────────────────────────769770┌───────────────────────────────────────771├─────── Testing 76.76.21.164 772773PING 76.76.21.164 (76.76.21.164): 56 data bytes774Request timeout for icmp_seq 0775Request timeout for icmp_seq 1776Request timeout for icmp_seq 2777778--- 76.76.21.164 ping statistics ---7794 packets transmitted, 0 packets received, 100.0% packet loss780781 1 192.168.1.1 (192.168.1.1) 3.954 ms 3.742 ms 3.074 ms782 2 10.115.222.33 (10.115.222.33) 5.402 ms 8.100 ms 6.493 ms783 3 10.115.7.124 (10.115.7.124) 5.603 ms 5.580 ms 6.091 ms784 4 10.111.5.9 (10.111.5.9) 9.932 ms 5.113 ms 4.660 ms785 5 84.16.7.226 (84.16.7.226) 5.365 ms 5.987 ms 5.510 ms786 6 * * *787 7 * * *788 8 * * *789 9 * * *79010 * * *79111 * * *79212 * * *79313 * * *79414 * * *79515 * * *79616 * * *79717 * * *79818 * * *79919 * * *80020 * * *80121 * * *80222 * * *80323 * * *80424 * * *80525 * * *80626 * * *80727 * * *80828 * * *80929 * * *81030 * * *811└───────────────────────────────────────812813┌───────────────────────────────────────814├─────── Testing 76.76.21.241 815816PING 76.76.21.241 (76.76.21.241): 56 data bytes817Request timeout for icmp_seq 0818Request timeout for icmp_seq 1819Request timeout for icmp_seq 2820821--- 76.76.21.241 ping statistics ---8224 packets transmitted, 0 packets received, 100.0% packet loss823824 1 192.168.1.1 (192.168.1.1) 11.479 ms 10.425 ms 7.989 ms825 2 10.115.222.33 (10.115.222.33) 6.598 ms 6.958 ms 5.907 ms826 3 10.115.7.124 (10.115.7.124) 5.271 ms 6.842 ms 4.656 ms827 4 10.111.5.9 (10.111.5.9) 5.456 ms 5.734 ms 4.469 ms828 5 84.16.7.226 (84.16.7.226) 5.687 ms 5.673 ms 5.290 ms829 6 * * *830 7 * * *831 8 * * *832 9 * * *83310 * * *83411 * * *83512 * * *83613 * * *83714 * * *83815 * * *83916 * * *84017 * * *84118 * * *84219 * * *84320 * * *84421 * * *84522 * * *84623 * * *84724 * * *84825 * * *84926 * * *85027 * * *85128 * * *85229 * * *85330 * * *854└───────────────────────────────────────855856┌───────────────────────────────────────857├─────── dig vercel.com 858859860; <<>> DiG 9.10.6 <<>> vercel.com861;; global options: +cmd862;; Got answer:863;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29623864;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1865866;; OPT PSEUDOSECTION:867; EDNS: version: 0, flags:; udp: 512868;; QUESTION SECTION:869;vercel.com. IN A870871;; ANSWER SECTION:872vercel.com. 1800 IN A 64.239.109.1873vercel.com. 1800 IN A 64.239.123.65874875;; Query time: 105 msec876;; SERVER: 200.48.225.130#53(200.48.225.130)877;; WHEN: Fri Feb 28 21:33:25 -05 2025878;; MSG SIZE rcvd: 71879880└───────────────────────────────────────881882┌───────────────────────────────────────883├─────── dig vercel.com via 8.8.8.8884885886; <<>> DiG 9.10.6 <<>> vercel.com @8.8.8.8887;; global options: +cmd888;; Got answer:889;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44138890;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1891892;; OPT PSEUDOSECTION:893; EDNS: version: 0, flags:; udp: 512894;; QUESTION SECTION:895;vercel.com. IN A896897;; ANSWER SECTION:898vercel.com. 1192 IN A 64.239.123.65899vercel.com. 1192 IN A 64.239.123.129900901;; Query time: 59 msec902;; SERVER: 8.8.8.8#53(8.8.8.8)903;; WHEN: Fri Feb 28 21:33:25 -05 2025904;; MSG SIZE rcvd: 71905906└───────────────────────────────────────907908┌───────────────────────────────────────909├─────── dig vercel.com via trace910911912; <<>> DiG 9.10.6 <<>> vercel.com +trace913;; global options: +cmd914. 493404 IN NS f.root-servers.net.915. 493404 IN NS g.root-servers.net.916. 493404 IN NS h.root-servers.net.917. 493404 IN NS i.root-servers.net.918. 493404 IN NS j.root-servers.net.919. 493404 IN NS k.root-servers.net.920. 493404 IN NS l.root-servers.net.921. 493404 IN NS m.root-servers.net.922. 493404 IN NS a.root-servers.net.923. 493404 IN NS b.root-servers.net.924. 493404 IN NS c.root-servers.net.925. 493404 IN NS d.root-servers.net.926. 493404 IN NS e.root-servers.net.927;; Received 723 bytes from 200.48.225.130#53(200.48.225.130) in 21 ms928929com. 172800 IN NS f.gtld-servers.net.930com. 172800 IN NS h.gtld-servers.net.931com. 172800 IN NS k.gtld-servers.net.932com. 172800 IN NS a.gtld-servers.net.933com. 172800 IN NS b.gtld-servers.net.934com. 172800 IN NS l.gtld-servers.net.935com. 172800 IN NS d.gtld-servers.net.936com. 172800 IN NS e.gtld-servers.net.937com. 172800 IN NS c.gtld-servers.net.938com. 172800 IN NS g.gtld-servers.net.939com. 172800 IN NS i.gtld-servers.net.940com. 172800 IN NS j.gtld-servers.net.941com. 172800 IN NS m.gtld-servers.net.942com. 86400 IN DS 19718 13 2 8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D7 71D7805A943com. 86400 IN RRSIG DS 8 1 86400 20250313220000 20250228210000 26470 . VPLKcy8nY2cBEE4gM8inZrR0qRppMLbOxElXYQq/b+A2F0BpuXeZrqCI BD6betQoTB3KgQXjze1w700CBecW9LUWTTtCEYM6kaTSfs/yyk78wuOq QYgOSSKh9qElxCUXWILFZTJXIZp70coYK9wQOpFmbNrrXoOC/D3i9vUi 7SZgElFoaT5cAeQ9EKHz5z8mzvnb4DSzCS1jLIVBqIi85qrvuw58SRrj 8XR+waEY8NbytVYoPwznhaWg3Ezrt7jI5BPl1NBrn+rBq1KfELcywhlr UJAvYpvnpzD/KzTgVi39sGUVmYaz0O8SzfW9IaglFfMcXZGJPFuFYrse pmSrog==944;; Received 1170 bytes from 2001:dc3::35#53(m.root-servers.net) in 138 ms945946vercel.com. 172800 IN NS e.zeit-world.com.947vercel.com. 172800 IN NS f.zeit-world.net.948vercel.com. 172800 IN NS b.zeit-world.org.949vercel.com. 172800 IN NS a.zeit-world.co.uk.950CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 900 IN NSEC3 1 1 0 - CK0Q3UDG8CEKKAE7RUKPGCT1DVSSH8LL NS SOA RRSIG DNSKEY NSEC3PARAM951CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 900 IN RRSIG NSEC3 13 2 900 20250308002634 20250228231634 23202 com. FENDpXH940LnYKfuY8mQq2+M0ji9l/bJM/Pr40eeu3ENtRBWMNvk9jEt uQOBCMpVlcpPh6PyJXnkfhNaZ37l+A==952H36GB6V84FDAH774M1P3C86GO3UI3NLL.com. 900 IN NSEC3 1 1 0 - H36H4M8561H05ISFKACG22O8OCD16855 NS DS RRSIG953H36GB6V84FDAH774M1P3C86GO3UI3NLL.com. 900 IN RRSIG NSEC3 13 2 900 20250305022234 20250226011234 23202 com. djotAXYR0uqwjOYtw7mJkFGw3IopRUnp8mvhWJ13RzePXnhPXFNna+qm fTzBb2pmcYIfVio75Gy/9IqvewTNwg==954;; Received 559 bytes from 192.33.14.30#53(b.gtld-servers.net) in 96 ms955956vercel.com. 1800 IN A 64.239.109.129957vercel.com. 1800 IN A 64.239.123.193958;; Received 71 bytes from 198.51.44.13#53(a.zeit-world.co.uk) in 76 ms959960└───────────────────────────────────────961962┌───────────────────────────────────────963├─────── Output of vercel.com964965* Host vercel.com:443 was resolved.966* IPv6: (none)967* IPv4: 64.239.109.1, 64.239.123.1968* Trying 64.239.109.1:443...969* connect to 64.239.109.1 port 443 from 192.168.1.61 port 64710 failed: Operation timed out970* Trying 64.239.123.1:443...971* connect to 64.239.123.1 port 443 from 192.168.1.61 port 64788 failed: Operation timed out972* Failed to connect to vercel.com port 443 after 150120 ms: Couldn't connect to server973* Closing connection974975└───────────────────────────────────────976977978┌───────────────────────────────────────979│ Time elapsed: 1860 seconds980│981├─────── FINISHED982└───────────────────────────────────────
File can be found at /Users/lennymmm/p/vercel-debug.txt
Pls I need help resolving this issue, am also facing same problem
I am having same issue at https://www.theninja-rpg.com/ . Previously I don't need to use VPN to connect to game, Since last month , it can't connect regularly and require VPN. I am from Myanmar. All other Myanmar players are having same issue now.
When I ask to my isp, there is no issue from isp side.
When I contact to game's administration team and owner , they replied it was blocked from Vercel .
Therefore, please help to solve my issue.
With Best Regards
Victor
reply to #19
I'm the owner of this site, and indeed it seems to not be working, despite me having white-listed the IPs in question in the firewall.. this is quite frustrating to have users actually being blocked from our services in a manner which seems completely out of our control.
(edited)
Hi!
I am facing this issue as well, for the past 3 weeks. I tried clearing out my cookies, accessing from a different browser, clearing out cache, but nothing worked.
I tried allowing my IP on CF and skipping all the security rules, but after thorough investigation, i figured out it was vercel blocking my IP address.
I tried running the script that was suggested on this thread:
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
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
+---------------------------------------
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
+---------------------------------------
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
+---------------------------------------
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
+---------------------------------------
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
+---------------------------------------
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
+---------------------------------------
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
+---------------------------------------
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
+---------------------------------------
1QUESTIONS:2saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app, type = A, class = IN3ANSWERS:4-> saccor-stock-management-phwfjvd7t-josemanuelsilvas-projects.vercel.app5internet address = 175.139.142.256ttl = 0 (0 secs)
It is showing after using it in cmd
How to do? Please help me. It is not output vercel-debug.text.
Hello. Facing the same issue. All my hosted vercel sites stoped working on a mobile proviedrs. They are working just fine via vpn or through wifi, but not on mobile. Some of my websites switched to 216.150.1.1, but problem still persists. Unfortunately, because it's mobile problem i can't run debug script, at least not in standart way.
Hey I can't access vercel without turning on vpn , fix this problem
Vercel Alum
Hey, ! Sorry to hear you're seeing this issue. Can you follow the post above and get back to us on findings?
(edited)
Hello there, ! I’ve have problems with IP assigned to my domain (A record) - 216.198.79.1 it is blocked in Russia. I know this is absolutely not a Vercel problem, but what can i do to get access to my website?
Is this working atm? Because i’ve need to move my domain to another registrar in order to change CNAME for root-romain because of RFC-2181, also if i use Vercel’s NS-servers to manage domain i will be able to point CNAME record to root-domain, eg domain.com?
Thank you.
(edited)
Hi!
I have an issue loading my website using cellular daya. VPN and in-house ISP works pretty good, but mobile is no go.
✅ Pings to Vercel IP’s are okay
✅ Vercel domains qurle.vercel.app or qurle-d2v38ez6o-qurles.vercel.app works good
❌ Custom domains on Vercel NS loads 6KB of data then stops loading without network errors
❌ Custom domains on 3rd party NS with A-record (216.198.79.1) does the same
I live in Russia, so there may be some access problems with DNS, I guess?
vercel.app domain is not reachable from Turkey. If you use Vodafone Turkey, here are my logs:
1Domain to test (e.g. example.com): 2┌───────────────────────────────────────3├─────── Fetching IP Addresses4│5│ facelessvideo-be.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.1956└───────────────────────────────────────78┌───────────────────────────────────────9├─────── STARTING10│11│ Domain to test: facelessvideo-be.vercel.app 12│ Timestamp (UTC): Tue Jan 13 12:50:54 UTC 202613│ Timestamp (Local): Tue Jan 13 15:50:54 +03 202614└───────────────────────────────────────1516┌───────────────────────────────────────17├─────── IP Information 1819{20 "ip": "176.216.173.213",21 "city": "Ankara",22 "region": "Ankara",23 "country": "TR",24 "loc": "39.9199,32.8543",25 "org": "AS15897 Vodafone Telekomunikasyon A.S.",26 "postal": "06420",27 "timezone": "Europe/Istanbul",28 "readme": "https://ipinfo.io/missingauth"29}30└───────────────────────────────────────3132┌───────────────────────────────────────33├─────── Testing 216.198.79.3 34Checking headers via 216.198.79.335* Connecting to hostname: 216.198.79.336* Trying 216.198.79.3:443...37* Connected to 216.198.79.3 (216.198.79.3) port 44338* ALPN: curl offers h2,http/1.139* (304) (OUT), TLS handshake, Client hello (1):40} [332 bytes data]41* Recv failure: Connection reset by peer42* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer43* Closing connection4445Checking ping to 216.198.79.346PING 216.198.79.3 (216.198.79.3): 56 data bytes4764 bytes from 216.198.79.3: icmp_seq=0 ttl=245 time=68.389 ms4864 bytes from 216.198.79.3: icmp_seq=1 ttl=245 time=154.696 ms4964 bytes from 216.198.79.3: icmp_seq=2 ttl=245 time=57.147 ms5064 bytes from 216.198.79.3: icmp_seq=3 ttl=245 time=1388.870 ms5152--- 216.198.79.3 ping statistics ---534 packets transmitted, 4 packets received, 0.0% packet loss54round-trip min/avg/max/stddev = 57.147/417.275/1388.870/562.218 ms55└───────────────────────────────────────5657┌───────────────────────────────────────58├─────── Testing 216.198.79.67 59Checking headers via 216.198.79.6760* Connecting to hostname: 216.198.79.6761* Trying 216.198.79.67:443...62* Connected to 216.198.79.67 (216.198.79.67) port 44363* ALPN: curl offers h2,http/1.164* (304) (OUT), TLS handshake, Client hello (1):65} [332 bytes data]66* Recv failure: Connection reset by peer67* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer68* Closing connection6970Checking ping to 216.198.79.6771PING 216.198.79.67 (216.198.79.67): 56 data bytes7264 bytes from 216.198.79.67: icmp_seq=0 ttl=245 time=50.481 ms7364 bytes from 216.198.79.67: icmp_seq=1 ttl=245 time=844.619 ms74Request timeout for icmp_seq 27564 bytes from 216.198.79.67: icmp_seq=2 ttl=245 time=1263.287 ms7664 bytes from 216.198.79.67: icmp_seq=3 ttl=245 time=261.493 ms7778--- 216.198.79.67 ping statistics ---794 packets transmitted, 4 packets received, 0.0% packet loss80round-trip min/avg/max/stddev = 50.481/604.970/1263.287/478.604 ms81└───────────────────────────────────────8283┌───────────────────────────────────────84├─────── Testing 216.198.79.131 85Checking headers via 216.198.79.13186* Connecting to hostname: 216.198.79.13187* Trying 216.198.79.131:443...88* Connected to 216.198.79.131 (216.198.79.131) port 44389* ALPN: curl offers h2,http/1.190* (304) (OUT), TLS handshake, Client hello (1):91} [332 bytes data]92* Recv failure: Connection reset by peer93* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer94* Closing connection9596Checking ping to 216.198.79.13197PING 216.198.79.131 (216.198.79.131): 56 data bytes9864 bytes from 216.198.79.131: icmp_seq=0 ttl=245 time=44.539 ms9964 bytes from 216.198.79.131: icmp_seq=1 ttl=245 time=42.633 ms10064 bytes from 216.198.79.131: icmp_seq=2 ttl=245 time=148.205 ms10164 bytes from 216.198.79.131: icmp_seq=3 ttl=245 time=51.230 ms102103--- 216.198.79.131 ping statistics ---1044 packets transmitted, 4 packets received, 0.0% packet loss105round-trip min/avg/max/stddev = 42.633/71.652/148.205/44.313 ms106└───────────────────────────────────────107108┌───────────────────────────────────────109├─────── Testing 216.198.79.195 110Checking headers via 216.198.79.195111* Connecting to hostname: 216.198.79.195112* Trying 216.198.79.195:443...113* Connected to 216.198.79.195 (216.198.79.195) port 443114* ALPN: curl offers h2,http/1.1115* (304) (OUT), TLS handshake, Client hello (1):116} [332 bytes data]117* Recv failure: Connection reset by peer118* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer119* Closing connection120121Checking ping to 216.198.79.195122PING 216.198.79.195 (216.198.79.195): 56 data bytes12364 bytes from 216.198.79.195: icmp_seq=0 ttl=245 time=111.144 ms12464 bytes from 216.198.79.195: icmp_seq=1 ttl=245 time=190.278 ms12564 bytes from 216.198.79.195: icmp_seq=2 ttl=245 time=475.559 ms12664 bytes from 216.198.79.195: icmp_seq=3 ttl=245 time=118.352 ms127128--- 216.198.79.195 ping statistics ---1294 packets transmitted, 4 packets received, 0.0% packet loss130round-trip min/avg/max/stddev = 111.144/223.833/475.559/148.591 ms131└───────────────────────────────────────132133┌───────────────────────────────────────134├─────── Testing 64.29.17.3 135Checking headers via 64.29.17.3136* Connecting to hostname: 64.29.17.3137* Trying 64.29.17.3:443...138* Connected to 64.29.17.3 (64.29.17.3) port 443139* ALPN: curl offers h2,http/1.1140* (304) (OUT), TLS handshake, Client hello (1):141} [332 bytes data]142* Recv failure: Connection reset by peer143* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer144* Closing connection145146Checking ping to 64.29.17.3147PING 64.29.17.3 (64.29.17.3): 56 data bytes14864 bytes from 64.29.17.3: icmp_seq=0 ttl=245 time=633.421 ms14964 bytes from 64.29.17.3: icmp_seq=1 ttl=245 time=648.917 ms15064 bytes from 64.29.17.3: icmp_seq=2 ttl=245 time=299.205 ms151152--- 64.29.17.3 ping statistics ---1534 packets transmitted, 3 packets received, 25.0% packet loss154round-trip min/avg/max/stddev = 299.205/527.181/648.917/161.327 ms155└───────────────────────────────────────156157┌───────────────────────────────────────158├─────── Testing 64.29.17.67 159Checking headers via 64.29.17.67160* Connecting to hostname: 64.29.17.67161* Trying 64.29.17.67:443...162* Connected to 64.29.17.67 (64.29.17.67) port 443163* ALPN: curl offers h2,http/1.1164* (304) (OUT), TLS handshake, Client hello (1):165} [332 bytes data]166* Connection timed out after 3006 milliseconds167* Closing connection168169Checking ping to 64.29.17.67170PING 64.29.17.67 (64.29.17.67): 56 data bytes17164 bytes from 64.29.17.67: icmp_seq=0 ttl=245 time=357.520 ms172Request timeout for icmp_seq 117364 bytes from 64.29.17.67: icmp_seq=1 ttl=245 time=1011.245 ms17464 bytes from 64.29.17.67: icmp_seq=2 ttl=245 time=326.102 ms17564 bytes from 64.29.17.67: icmp_seq=3 ttl=245 time=291.255 ms176177--- 64.29.17.67 ping statistics ---1784 packets transmitted, 4 packets received, 0.0% packet loss179round-trip min/avg/max/stddev = 291.255/496.530/1011.245/298.093 ms180└───────────────────────────────────────181182┌───────────────────────────────────────183├─────── Testing 64.29.17.131 184Checking headers via 64.29.17.131185* Connecting to hostname: 64.29.17.131186* Trying 64.29.17.131:443...187* Connected to 64.29.17.131 (64.29.17.131) port 443188* ALPN: curl offers h2,http/1.1189* (304) (OUT), TLS handshake, Client hello (1):190} [332 bytes data]191* Recv failure: Connection reset by peer192* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer193* Closing connection194195Checking ping to 64.29.17.131196PING 64.29.17.131 (64.29.17.131): 56 data bytes197Request timeout for icmp_seq 0198Request timeout for icmp_seq 1199Request timeout for icmp_seq 220064 bytes from 64.29.17.131: icmp_seq=0 ttl=245 time=3213.094 ms20164 bytes from 64.29.17.131: icmp_seq=1 ttl=245 time=2206.926 ms20264 bytes from 64.29.17.131: icmp_seq=2 ttl=245 time=1203.980 ms20364 bytes from 64.29.17.131: icmp_seq=3 ttl=245 time=200.294 ms204205--- 64.29.17.131 ping statistics ---2064 packets transmitted, 4 packets received, 0.0% packet loss207round-trip min/avg/max/stddev = 200.294/1706.073/3213.094/1122.657 ms208└───────────────────────────────────────209210┌───────────────────────────────────────211├─────── Testing 64.29.17.195 212Checking headers via 64.29.17.195213* Connecting to hostname: 64.29.17.195214* Trying 64.29.17.195:443...215* Connection timed out after 3006 milliseconds216* Closing connection217218Checking ping to 64.29.17.195219PING 64.29.17.195 (64.29.17.195): 56 data bytes220Request timeout for icmp_seq 0221Request timeout for icmp_seq 1222Request timeout for icmp_seq 222364 bytes from 64.29.17.195: icmp_seq=0 ttl=245 time=5743.162 ms22464 bytes from 64.29.17.195: icmp_seq=1 ttl=245 time=4737.642 ms22564 bytes from 64.29.17.195: icmp_seq=2 ttl=245 time=3734.315 ms22664 bytes from 64.29.17.195: icmp_seq=3 ttl=245 time=2816.645 ms227228--- 64.29.17.195 ping statistics ---2294 packets transmitted, 4 packets received, 0.0% packet loss230round-trip min/avg/max/stddev = 2816.645/4257.941/5743.162/1094.019 ms231└───────────────────────────────────────232233┌───────────────────────────────────────234├─────── dig facelessvideo-be.vercel.app 235236237; <<>> DiG 9.10.6 <<>> facelessvideo-be.vercel.app238;; global options: +cmd239;; Got answer:240;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31368241;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1242243;; OPT PSEUDOSECTION:244; EDNS: version: 0, flags:; udp: 4096245;; QUESTION SECTION:246;facelessvideo-be.vercel.app. IN A247248;; ANSWER SECTION:249facelessvideo-be.vercel.app. 274 IN A 216.198.79.131250facelessvideo-be.vercel.app. 274 IN A 64.29.17.131251252;; Query time: 8 msec253;; SERVER: fe80::30d5:3eff:fe95:cf64%14#53(fe80::30d5:3eff:fe95:cf64%14)254;; WHEN: Tue Jan 13 15:51:36 +03 2026255;; MSG SIZE rcvd: 88256257└───────────────────────────────────────258259┌───────────────────────────────────────260├─────── dig facelessvideo-be.vercel.app via 8.8.8.8261262263; <<>> DiG 9.10.6 <<>> facelessvideo-be.vercel.app @8.8.8.8264;; global options: +cmd265;; Got answer:266;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10383267;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1268269;; OPT PSEUDOSECTION:270; EDNS: version: 0, flags:; udp: 512271;; QUESTION SECTION:272;facelessvideo-be.vercel.app. IN A273274;; ANSWER SECTION:275facelessvideo-be.vercel.app. 300 IN A 216.198.79.195276facelessvideo-be.vercel.app. 300 IN A 64.29.17.195277278;; Query time: 528 msec279;; SERVER: 8.8.8.8#53(8.8.8.8)280;; WHEN: Tue Jan 13 15:51:36 +03 2026281;; MSG SIZE rcvd: 88282283└───────────────────────────────────────284285┌───────────────────────────────────────286├─────── dig facelessvideo-be.vercel.app via trace287288289; <<>> DiG 9.10.6 <<>> facelessvideo-be.vercel.app +trace290;; global options: +cmd291. 4502 IN NS e.root-servers.net.292. 4502 IN NS m.root-servers.net.293. 4502 IN NS c.root-servers.net.294. 4502 IN NS k.root-servers.net.295. 4502 IN NS j.root-servers.net.296. 4502 IN NS l.root-servers.net.297. 4502 IN NS i.root-servers.net.298. 4502 IN NS d.root-servers.net.299. 4502 IN NS f.root-servers.net.300. 4502 IN NS g.root-servers.net.301. 4502 IN NS b.root-servers.net.302. 4502 IN NS a.root-servers.net.303. 4502 IN NS h.root-servers.net.304;; Received 239 bytes from fe80::30d5:3eff:fe95:cf64%14#53(fe80::30d5:3eff:fe95:cf64%14) in 260 ms305306;; Received 56 bytes from 199.7.83.42#53(l.root-servers.net) in 177 ms307308└───────────────────────────────────────309310┌───────────────────────────────────────311├─────── Output of facelessvideo-be.vercel.app312313* Host facelessvideo-be.vercel.app:443 was resolved.314* IPv6: (none)315* IPv4: 216.198.79.131, 64.29.17.131316* Trying 216.198.79.131:443...317* Connected to facelessvideo-be.vercel.app (216.198.79.131) port 443318* ALPN: curl offers h2,http/1.1319* (304) (OUT), TLS handshake, Client hello (1):320} [332 bytes data]321* Recv failure: Connection reset by peer322* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer323* Closing connection324325└───────────────────────────────────────326327328┌───────────────────────────────────────329│ Time elapsed: 45 seconds330│331├─────── FINISHED332└───────────────────────────────────────333334335336File can be found at /Users/xxx/vercel-debug.txt337338
Hi ,
Please see the attached vercel-debug.txt file. The custom domain set up with a Vercel deployment is not accessible from Russia. While *.vercel.app works.
±--------------------------------------
±------ Fetching IP Addresses
|
| www.teleios.bible IP range: 216.150.1.1, 216.150.1.65, 216.150.1.129, 216.150.1.193, 216.150.16.1, 216.150.16.65, 216.150.16.129, 216.150.16.193
±--------------------------------------
Operation timed out after 3004 milliseconds with 10020 bytes received
closing connection #0
Checking ping to 216.150.1.1
Обмен пакетами с 216.150.1.1 по с 32 байтами данных:
Ответ от 216.150.1.1: число байт=32 время=106мс TTL=244
Ответ от 216.150.1.1: число байт=32 время=106мс TTL=244
Ответ от 216.150.1.1: число байт=32 время=106мс TTL=244
Ответ от 216.150.1.1: число байт=32 время=106мс TTL=244
Operation timed out after 3002 milliseconds with 17136 bytes received
closing connection #0
Checking ping to 216.150.1.65
Обмен пакетами с 216.150.1.65 по с 32 байтами данных:
Ответ от 216.150.1.65: число байт=32 время=90мс TTL=244
Ответ от 216.150.1.65: число байт=32 время=88мс TTL=244
Ответ от 216.150.1.65: число байт=32 время=88мс TTL=244
Ответ от 216.150.1.65: число байт=32 время=89мс TTL=244
Operation timed out after 3006 milliseconds with 17136 bytes received
closing connection #0
Checking ping to 216.150.1.129
Обмен пакетами с 216.150.1.129 по с 32 байтами данных:
Ответ от 216.150.1.129: число байт=32 время=120мс TTL=246
Ответ от 216.150.1.129: число байт=32 время=105мс TTL=246
Ответ от 216.150.1.129: число байт=32 время=105мс TTL=246
Ответ от 216.150.1.129: число байт=32 время=105мс TTL=246
Operation timed out after 3008 milliseconds with 17136 bytes received
closing connection #0
Checking ping to 216.150.1.193
Обмен пакетами с 216.150.1.193 по с 32 байтами данных:
Ответ от 216.150.1.193: число байт=32 время=88мс TTL=244
Ответ от 216.150.1.193: число байт=32 время=87мс TTL=244
Ответ от 216.150.1.193: число байт=32 время=87мс TTL=244
Ответ от 216.150.1.193: число байт=32 время=87мс TTL=244
Operation timed out after 3003 milliseconds with 0 bytes received
closing connection #0
Checking ping to 216.150.16.1
Обмен пакетами с 216.150.16.1 по с 32 байтами данных:
Ответ от 216.150.16.1: число байт=32 время=92мс TTL=244
Ответ от 216.150.16.1: число байт=32 время=93мс TTL=244
Ответ от 216.150.16.1: число байт=32 время=94мс TTL=244
Ответ от 216.150.16.1: число байт=32 время=94мс TTL=244
Operation timed out after 3009 milliseconds with 17136 bytes received
closing connection #0
Checking ping to 216.150.16.65
Обмен пакетами с 216.150.16.65 по с 32 байтами данных:
Ответ от 216.150.16.65: число байт=32 время=103мс TTL=244
Ответ от 216.150.16.65: число байт=32 время=102мс TTL=244
Ответ от 216.150.16.65: число байт=32 время=102мс TTL=244
Ответ от 216.150.16.65: число байт=32 время=102мс TTL=244
Operation timed out after 3013 milliseconds with 17136 bytes received
closing connection #0
Checking ping to 216.150.16.129
Обмен пакетами с 216.150.16.129 по с 32 байтами данных:
Ответ от 216.150.16.129: число байт=32 время=92мс TTL=244
Ответ от 216.150.16.129: число байт=32 время=92мс TTL=244
Ответ от 216.150.16.129: число байт=32 время=92мс TTL=244
Ответ от 216.150.16.129: число байт=32 время=92мс TTL=244
Operation timed out after 3013 milliseconds with 17136 bytes received
closing connection #0
Checking ping to 216.150.16.193
Обмен пакетами с 216.150.16.193 по с 32 байтами данных:
Ответ от 216.150.16.193: число байт=32 время=105мс TTL=244
Ответ от 216.150.16.193: число байт=32 время=104мс TTL=244
Ответ от 216.150.16.193: число байт=32 время=105мс TTL=244
Ответ от 216.150.16.193: число байт=32 время=105мс TTL=244
±--------------------------------------
| Time elapsed: 655.2 seconds
|
±------ FINISHED
±--------------------------------------
File can be found at C:\Users\RTarbeev.CROC\vercel-debug.txt
I’m having the same issue others are having… here’s the file from my local coffeeshop in Red Hook, NY, which blocks my custom domain (but not the Vercel domain directly). I emailed with support, and they said there’s nothing more they can do, but I find it very worrying that multiple locations are blocking the Vercel anycast. My friend in Richmond, VA couldn’t access my site, either… same error everyone’s getting above.