Child Item

Site Totals

61365 Questions Answered 267 Categories

Inconsistent Ping/Speed - Possible Tower issue?

We were using our connection to game on our PS4 and PC, and for the past handful of months I have been unable to due to an unreliable ping.

I test the ping to Google.com, Yahoo.com and 8.8.8.8 and will get under 100 Ms for a duration of time, and then it will spike to around 1000ms. I'll get ping results around 60ms for 15 minutes to an hour, then over 500ms to 1k for 15 minutes to an hour, and then it will go back and start the loop over again.

I have been trouble shooting on my end to try and narrow it down and I think it's likely it's the tower we use and was hoping to have Verizon Support look into it. The area code is 37874.

Steps I have taken is to make sure that nothing but the PC is connected to the network, Also to connect to the WIFI from the Verizon Router instead of the wired connection using our router. I have tried other PC's and a Laptop. I have even connected my phone and got the same results. Some times it's fantastic, other times it's not usable.

I have noticed the same results from my Verizon Wireless phone when it is not on the home network at all. I also enabled the hotspot from it and connected a laptop and would get similar results.

I am not sure if it's coincidental or not, but a tornado came through in November and destroyed several homes a couple of miles from me and it may have started around then.

Thanks in advance for any help.

Comments

7e18n1

What you're seeing maybe high latency and ping just shows high latency is there. Ping is usually the fastest way to see it, but it doesn't help much to diagnose a high latency issue. Blaming the tower is not supported by what ping has to say. What works better is a utility called Trace Route. From the command prompt, type:

Tracert 8.8.8.8

Tracert google.com

Tracert 4.2.2.1 >filespec

> is the redirect switch, filespec is the full file specification: c:\path\filename.ext of the file you want to send the output to. There is no screen output when the redirect switch is used.

Post the output from tracert 4.2.2.1 so we can see what you're talking about.

BPaille

Thank you for the help. I just got home and could barely pull a website, but did this tracert per your instructions.

Tracing route to a.resolvers.level3.net [4.2.2.1]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms cp.local.tld [192.168.0.1]

2 3 ms 3 ms 3 ms 192.168.1.1

3 1000 ms 1061 ms * 255.sub-66-174-175.myvzw.com [66.174.175.255]

4 * 628 ms 1028 ms 228.sub-69-83-49.myvzw.com [69.83.49.228]

5 550 ms 738 ms * 34.sub-69-83-60.myvzw.com [69.83.60.34]

6 535 ms * * 194.sub-69-83-63.myvzw.com [69.83.63.194]

7 579 ms * 447 ms 224.sub-69-83-32.myvzw.com [69.83.32.224]

8 435 ms 846 ms 661 ms 224.sub-69-83-32.myvzw.com [69.83.32.224]

9 654 ms 729 ms * 65.sub-69-83-32.myvzw.com [69.83.32.65]

10 * 646 ms * nash-b1-link.telia.net [62.115.44.117]

11 685 ms * * atl-b22-link.telia.net [62.115.138.214]

12 * * * Request timed out.

13 * * * Request timed out.

Then I got this one an hour later after the internet seemed to be functional again.

Tracing route to a.resolvers.level3.net [4.2.2.1]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms cp.local.tld [192.168.0.1]

2 4 ms 2 ms 2 ms 192.168.1.1

3 53 ms 57 ms 57 ms 136.sub-66-174-37.myvzw.com [66.174.37.136]

4 66 ms 60 ms 53 ms 228.sub-69-83-61.myvzw.com [69.83.61.228]

5 71 ms 36 ms 50 ms 34.sub-69-83-60.myvzw.com [69.83.60.34]

6 65 ms 44 ms 48 ms 194.sub-69-83-63.myvzw.com [69.83.63.194]

7 76 ms 64 ms 42 ms 224.sub-69-83-32.myvzw.com [69.83.32.224]

8 49 ms 56 ms 47 ms 224.sub-69-83-32.myvzw.com [69.83.32.224]

9 70 ms 54 ms 57 ms 65.sub-69-83-32.myvzw.com [69.83.32.65]

10 52 ms 53 ms 48 ms nash-b1-link.telia.net [62.115.44.117]

11 69 ms 57 ms 74 ms atl-b22-link.telia.net [62.115.138.204]

12 * 64 ms 74 ms level3-ic-319173-atl-b22.c.telia.net [213.248.84.35]

13 * * * Request timed out.

14 64 ms 73 ms 57 ms a.resolvers.level3.net [4.2.2.1]

Trace complete.

BPaille

After a few minutes of decent browsing I got this one.

Tracing route to a.resolvers.level3.net [4.2.2.1]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms cp.local.tld [192.168.0.1]

2 4 ms 3 ms 2 ms 192.168.1.1

3 1112 ms 647 ms 263 ms 136.sub-66-174-37.myvzw.com [66.174.37.136]

4 760 ms 389 ms 735 ms 228.sub-69-83-61.myvzw.com [69.83.61.228]

5 460 ms 577 ms 731 ms 34.sub-69-83-60.myvzw.com [69.83.60.34]

6 892 ms 104 ms 297 ms 194.sub-69-83-63.myvzw.com [69.83.63.194]

7 914 ms 462 ms * 224.sub-69-83-32.myvzw.com [69.83.32.224]

8 479 ms 333 ms 872 ms 224.sub-69-83-32.myvzw.com [69.83.32.224]

9 865 ms 1100 ms 567 ms 65.sub-69-83-32.myvzw.com [69.83.32.65]

10 947 ms 736 ms 666 ms nash-b1-link.telia.net [62.115.44.117]

11 371 ms 352 ms 348 ms atl-b22-link.telia.net [62.115.138.204]

12 * * * Request timed out.

13 * * * Request timed out.

14 936 ms 889 ms 1042 ms a.resolvers.level3.net [4.2.2.1]

Trace complete.

BPaille

Now again about 10 minutes later.

Tracing route to a.resolvers.level3.net [4.2.2.1]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms cp.local.tld [192.168.0.1]

2 4 ms 3 ms 2 ms 192.168.1.1

3 63 ms 49 ms 44 ms 136.sub-66-174-37.myvzw.com [66.174.37.136]

4 75 ms 51 ms 50 ms 228.sub-69-83-61.myvzw.com [69.83.61.228]

5 104 ms 83 ms 53 ms 34.sub-69-83-60.myvzw.com [69.83.60.34]

6 66 ms 74 ms 48 ms 194.sub-69-83-63.myvzw.com [69.83.63.194]

7 100 ms 99 ms 81 ms 224.sub-69-83-32.myvzw.com [69.83.32.224]

8 79 ms 60 ms 48 ms 224.sub-69-83-32.myvzw.com [69.83.32.224]

9 55 ms 59 ms 55 ms 65.sub-69-83-32.myvzw.com [69.83.32.65]

10 58 ms 66 ms 108 ms nash-b1-link.telia.net [62.115.44.117]

11 72 ms 63 ms 85 ms atl-b22-link.telia.net [62.115.138.204]

12 * * * Request timed out.

13 * * * Request timed out.

14 76 ms 71 ms 54 ms a.resolvers.level3.net [4.2.2.1]

Trace complete.

I'll await any further instructions without flooding the thread any more, hopefully this helps illustrate what I was describing. Thanks again for any help.

BPaille

OK. I think I found the reason, but not the fix.

My download speed has died. I get the decent pings when there is no internet usage at all. If even a webpage is pulled, it goes to [Removed]. So, I did some speed tests.

My download speed tested all below .5 Mbps. Normally around .1Mbps. Then my upload would be 7-10 Mbps. I'm not really sure what to do now.

inappropriate content removed as required by the Verizon Wireless Terms of Service

Message edited by Verizon Moderator

7e18n1

If you're sure you didn't change something when you moved the antenna, it sounds like the only thing you can do is complain to VzW. Don't mention you moved the antenna.

7e18n1

Are you on the unlimited data plan?

BPaille

I am, I had just switched. I spent two days going back in forth with Verizon tech support.

There solution is to send a tech out for 150 dollars. The fee is regardless of whether or not that person resolves my issue, and if the tech deems my equipment is the problem I will be charged for it.

Now, after all of this and keeping tabs of times and speeds and pings, I think I'm being throttled. I used 29 gig and after 22 gig it is supposed to take me down to 3g speeds during congested times. I am being dropped to 56k speeds. My bill cycle resets in a day or two, so I'm going to ride it out and see if it's cleared up. If it does I'll know it's not the equipment. Hopefully I can convince the right person that I am being throttled down too much and there's a fix for it. If it doesn't fix it once my data resets then I may be on the hook for the tech/fee or switch providers unfortunately.

7e18n1

Yes, let us know if it clears up when your bill recycles.

Child Item