Verizon phones blocked from my websites
NathanLake
Contributor - Level 1

I am a website designer, and most of my sites are hosted by a company named InMotionHosting. About 3 months ago, people attempting to access my sites using their phone and the cellular data plan found they were being blocked. If they use WIFI, or any other internet connection they access the sites just fine.

I have worked with my host and they see no issues on their servers. It also does not appear that Verizon is directly at fault. I ran a traceroute from my phone and it appears that some servers between Verizon and InMotionHosting are blocking Verizon cellular data access.

I need this fixed.

To repro this issue, do this.

1. Using your cell phone, connect to a good WIFI source and go to thetravelwriters.net. You should connect with no problems.

2. Turn off your WIFI, and try to connect using the celluar data (4G/3G) system. You will get no response from the server at all. It will eventually time out.

I called Verizon tech support and they won't even try to look at this. I need help. I can't afford to lose this many prospective readers.

Labels (1)
0 Likes
Reply
9 Replies
vzw_customer_support
Customer Service Rep

We want your readers to access the site without an issue, NathanLake. I konw this is important for exposure and to market to others as well. After looking for the site on my phone I was able to access it using thetravelwriters.com site. This allowed me to access the site. Did you try using the .com address instead of the .net one?
JasperM_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

0 Likes
Reply
NathanLake
Contributor - Level 1

If there is a site with the address thetravelwriters.com, it is not mine. I own thetravelwriters.net and it cannot be accessed via a Verizon cell phone unless connected to wifi.

0 Likes
Reply
7e18n1
Specialist - Level 3

You’re right, thetravelwriters.com is completely different!

http://www.thetravelwriters.net

Who We Are

Once we were just writers or photographers, but no more. Today we are photojournalists. We are multimedia storytellers. We are the modern day troubadours, bringing words, photos, and video to you from all the places we go and the people we meet. We tell our stories and their stories. We tell stories of adventures you might have had, or will someday have. We seek to inspire and excite. We bring the world to you in case you can’t go to the world.
We encourage you to stop, look, and listen. And as Vyasa said, "If you listen carefully, at the end you'll be someone else."

It works when using a VPN Client. It should work without such tactics.

0 Likes
Reply
7e18n1
Specialist - Level 3

Your provider is Godaddy, are you saying they’re denying this? Godaddy has the .net TLD listed as described and the .com TLD as domaincontrol.com and when the .com TLD is used your site comes up with the .com TLD. Or is this NOT your site?

Whois shows:

Domain Name: THETRAVELWRITERS.NET
Registrar: GODADDY.COM, LLC
Sponsoring Registrar IANA ID: 146
Whois Server: whois.godaddy.com
Referral URL: http://registrar.godaddy.com

Name Server: NS.INMOTIONHOSTING.COM
Name Server: NS2.INMOTIONHOSTING.COM

Domain Name: THETRAVELWRITERS.COM
Registrar: GODADDY.COM, LLC
Sponsoring Registrar IANA ID: 146
Whois Server: whois.godaddy.com
Referral URL: http://registrar.godaddy.com

Name Server: NS37.DOMAINCONTROL.COM
Name Server: NS38.DOMAINCONTROL.COM

0 Likes
Reply
NathanLake
Contributor - Level 1

The registrar is GoDaddy, but they are not the host. The sites are all hosted by InMotionHosting.  I don't know for a fact, but I don't understand how GoDaddy would be involved.

0 Likes
Reply
7e18n1
Specialist - Level 3

> but I don't understand how GoDaddy would be involved.


Maybe so, but a trace (w/o VPN) doesn’t support Verizon as the cause.


Tracing route to thetravelwriters.net [216.194.169.100] over a maximum of 30 hops:


1    <1 ms   <1 ms    <1 ms  router.asus.com [192.168.2.1]

2     1 ms   <1 ms    <1 ms  192.168.1.1

3   280 ms   89 ms    56 ms  97.sub-66-174-23.myvzw.com [66.174.23.97]

4    48 ms   47 ms    31 ms  132.sub-69-83-9.myvzw.com [69.83.9.132]

5    60 ms   39 ms    40 ms  145.sub-69-83-9.myvzw.com [69.83.9.145]

6    80 ms   39 ms    42 ms  194.sub-69-83-9.myvzw.com [69.83.9.194]

7    70 ms   41 ms    36 ms  36.sub-69-83-18.myvzw.com [69.83.18.36]

8     *       *        *     Request timed out.

9    66 ms   39 ms    37 ms  45.sub-69-83-18.myvzw.com [69.83.18.45]

10    47 ms   39 ms    39 ms  xe-1-1-0.GW7.RIC2.ALTER.NET [157.130.57.245]

11    78 ms   70 ms    40 ms  0.ae2.BR1.IAD8.ALTER.NET [140.222.229.165]

12    78 ms   50 ms    73 ms  10ge13-1.core1.ash1.he.net [216.66.41.173]

13   124 ms  110 ms   122 ms  100ge13-1.core1.lax1.he.net [184.105.80.202]

14   106 ms  119 ms   121 ms  100ge11-1.core1.lax2.he.net [72.52.92.122]

15   141 ms   91 ms   118 ms  corporate-colocation-inc.gigabitethernet2-19.core1.lax2.he.net [184.105.140.162]

16   125 ms  124 ms   110 ms  205.134.225.38

17     *       *        *     Request timed out.

18     *       *        *     Request timed out.

19     *       *        *     Request timed out.

20   127 ms  118 ms   118 ms  biz141.inmotionhosting.com [216.194.169.100]

Trace complete.

0 Likes
Reply
pherson
Champion - Level 1

Go daddy notoriouslyhas issues, but noone ever wants to blame godaddy.

Whitcole
Newbie

I know this is old but how did you end up fixing it? No one knows how to help me and the same thing is happening to my website. 

0 Likes
Reply
kh-taylarie
Khoros Partner
Khoros Partner

Due to the age of this thread, it will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.

0 Likes
Reply