Internet Problems Between 7:30-11pm PST Daily

[boneill92]

For the last two weeks I have been experiencing internet issues. This is mainly regarding my ping, I have Frontier Fios (they purchased Verizon in my state). When my internet is stable I usually get around a 7-12 ping and a 30/30. The last two weeks my internet has been acting up and speedtest results have been really inconsistent, but its the ping that is bothering me. It goes up to anywhere between 40 to as high as 120 to my local server and this causes online gaming to be pretty much unplayable. I usually play on a xbox one that is hardwired and the game I play has a server that tells me the ping I have to the server and it rises up to 3-4 times what it is when my internet is stable. When speed testing the down and up is sometimes affected, but lowest I've really seen it is 15/20. I replaced my router thinking that could be the problem, but it still occurs. After numerous of night talking to Frontier customer support they finally sent out a technician and according to him he discovered nothing regarding their end. I looked online and saw people talking about virus and malware, I did a check on all computers and they are clean. Trying the forums and internet for help now because I am tired of frontier customer support not knowing and always wanting me to do their pointless router reset troubleshoots.
Thanks

 

[bill001g]

Time of day issues generally are a overload issue. The time you have is the prime home internet usage.

Run tracert and run pings to the first 2 hops and see if those too show the problem. The first is your router and the second if you have a common installation is the ISP first router. This represents the shared connection to yours and your neighbors houses.

You can continue on the trace and ping various things but the farther you get from your house the less likely you are going to get it fixed or even acknowledged if it is a issue between ISP.

If it is actually a over utilization condition it is almost impossible for the ISP to rectify quickly. This is not as large a issue as it once was.

 

[boneill92]

Alright I will run a tracert in a few hours when it starts to happen. One of the customer support people had me do it about a week ago and told me to use google.com as my server. Does any matter? Also I don't think it is an overload issue because I think it would start earlier and end earlier. It starts usually anywhere between 7:30-8:00pm PST and I've seen it end anytime between 10:00-11:30pm PST.

 

[jwritchey]

Alright I will run a tracert in a few hours when it starts to happen. One of the customer support people had me do it about a week ago and told me to use google.com as my server. Does any matter? Also I don't think it is an overload issue because I think it would start earlier and end earlier. It starts usually anywhere between 7:30-8:00pm PST and I've seen it end anytime between 10:00-11:30pm PST.

I think using google's dns will be fine.

If you can grab a capture of it when you're not exhibiting the issue and again when you're seeing high ping/latency issues.
Evidence is king when trying to convince telecoms there is a problem (i know).

also, if you add pipe tee filename.txt after the tracert, it will write the results out to a file

Example:

C:\Users\Jerem>tracert 8.8.8.8 | tee out.txt

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 10 ms 12 ms 96.120.19.33
3 10 ms 9 ms 9 ms Te0-7-0-6-sur02.huntsville.al.hunts.comcast.net [68.85.121.1]
4 11 ms 8 ms 11 ms xe-0-1-7-0-ar04.huntsville.al.hunts.comcast.net [162.151.13.53]
5 18 ms 15 ms 15 ms xe-4-0-3-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.85.232.105]
6 17 ms 16 ms 16 ms hu-0-4-0-3-cr02.56marietta.ga.ibone.comcast.net [68.86.87.201]
7 19 ms 16 ms 15 ms 68.86.87.230
8 51 ms 50 ms 50 ms as174.ashburn.va.ibone.comcast.net [66.208.229.138]
9 15 ms 14 ms 16 ms 209.85.253.229
10 19 ms 17 ms 16 ms 216.239.63.15
11 17 ms 16 ms 16 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

 

[boneill92]

C:\Users\Brendon>tracert google.com

Tracing route to google.com [216.58.193.78]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms Wireless_Broadband_Router.home [192.168.1.1]
2 56 ms 63 ms 72 ms static-50-46-224-1.evrt.wa.frontiernet.net [50.4
6.224.1]
3 27 ms 22 ms 20 ms xe--0-1-0---0.fdr01.both.wa.frontiernet.net [50.
35.7.185]
4 19 ms 20 ms 16 ms ae8---0.car01.evrt.wa.frontiernet.net [74.40.70.
57]
5 30 ms 28 ms 27 ms ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.1
01]
6 8 ms 14 ms 23 ms ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
26]
7 23 ms 21 ms 21 ms 74.40.26.131
8 55 ms 64 ms 58 ms 216.239.42.165
9 22 ms 21 ms 20 ms 64.233.174.17
10 32 ms 33 ms 43 ms sea15s07-in-f14.1e100.net [216.58.193.78]

Trace complete.

C:\Users\Brendon>

This is right now, I'll post later tonight when it starts.

 

[boneill92]

C:\Users\Brendon>tracert google.com

Tracing route to google.com [216.58.216.174]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 6 ms 7 ms static-50-46-224-1.evrt.wa.frontiernet.net [50.4
6.224.1]
3 59 ms 59 ms 58 ms xe--0-1-0---0.fdr01.both.wa.frontiernet.net [50.
35.7.185]
4 69 ms 71 ms 71 ms ae8---0.car01.evrt.wa.frontiernet.net [74.40.70.
57]
5 65 ms 79 ms 72 ms ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.1
01]
6 69 ms 71 ms 68 ms ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
26]
7 71 ms 72 ms 73 ms 74.40.26.131
8 68 ms 65 ms 60 ms 216.239.42.167
9 49 ms 50 ms 57 ms 216.239.51.161
10 69 ms 68 ms 63 ms sea15s02-in-f174.1e100.net [216.58.216.174]

Trace complete.

An example of it during the problems.

 

[boneill92]

C:\Users\Brendon>tracert google.com

Tracing route to google.com [216.58.193.78]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 7 ms static-50-46-224-1.evrt.wa.frontiernet.net [50.4
6.224.1]
3 84 ms 87 ms 91 ms xe--0-1-0---0.fdr01.both.wa.frontiernet.net [50.
35.7.185]
4 97 ms 124 ms 103 ms ae8---0.car01.evrt.wa.frontiernet.net [74.40.70.
57]
5 86 ms 83 ms 87 ms ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.1
01]
6 89 ms 90 ms 100 ms ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
26]
7 84 ms 81 ms 82 ms 74.40.26.131
8 81 ms 87 ms 82 ms 216.239.42.165
9 89 ms 87 ms 102 ms 64.233.174.17
10 87 ms 87 ms 96 ms sea15s07-in-f14.1e100.net [216.58.193.78]

Trace complete.

Tested it again immediately after I posted that and got even worse results.

 

[bill001g]

You really should not use tracert you need to actually run a bunch of open continuous ping windows to each hop. Tracert does not send enough data to really be sure.

Still your problem starts in hop3 which is likely some large juniper router in the ISP network. The interface on the router is 10gig from the description. It is unlikely they have overloaded a 10g interface.

I am going to guess wa means washington but unsure what cities but it is not like the traffic is going across the country.

So you know know there is a problem between the ISP router in hop 2 and the ISP router in hop 3. Other than interesting information there is little you can do with it. You can try to call up the ISP but how do you get past the guys that will ask if you have rebooted your pc. You yourself do not have the ability to read these traces so it will be almost impossible to get to a tech guy that will talk to you.

 

[boneill92]

Yes, I am located in Washington. Customer support is a joke. They were supposed to have a network tech investigate the issue tonight and instead I come home to a new router and found that the ticket is closed. They'll never admit it's on their end when I know it is.