Bad ping at night

[Flipback012]

So for about a month now i've been experiencing terrible ping but it really only happens at night. During the day, on overwatch i get around 70ms ping but at around 5:00pm things start to take a turn for the worst. It gradually starts increasing until it lands somewhere around 230ms. this happens in nearly every online game as well. I've tested nearly everything; the router, changed out the modem, bought a new wifi adapter. I've ran a countless number of speed tests and traceroutes. The traceroutes show that the ping is usually around 70 until around hop 9 and 10 which usually time out. That will look something like this to the closest overwatch server.
Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 12 ms 9 ms host-69-145-214-41.chy-wy.client.bresnan.net [69.145.214.41]
4 9 ms 9 ms 9 ms 69.145.247.51
5 67 ms 64 ms 58 ms host-69-145-214-209.chy-wy.client.bresnan.net [69.145.214.209]
6 66 ms 63 ms 58 ms host-72-175-110-146.static.bresnan.net [72.175.110.146]
7 60 ms 57 ms 57 ms host-69-146-192-2.chy-wy.client.bresnan.net [69.146.192.2]
8 76 ms * 15 ms host-72-175-110-219.static.bresnan.net [72.175.110.219]
9 * * * Request timed out.
10 201 ms 181 ms 171 ms ae-7-0.ear3.Dallas1.Level3.net [4.69.210.149]
11 193 ms 190 ms 204 ms BLIZZARD-EN.ear3.Dallas1.Level3.net [4.15.45.54]
12 191 ms 193 ms 187 ms ae1-br01-eqda6.blizzardonline.net [137.221.74.33]
13 194 ms 184 ms 177 ms hu-0-0-0-0-pe02-swlv10.blizzardonline.net [137.221.65.67]
14 192 ms 168 ms 180 ms be3-pe01-swlv10.blizzardonline.net [137.221.83.74]
15 201 ms 183 ms 178 ms et-0-0-13-br01-eqla1.blizzardonline.net [137.221.65.68]
16 208 ms 190 ms 182 ms be1-pe01-eqla1.blizzardonline.net [137.221.68.67]
17 189 ms 197 ms 205 ms lax-eqla1-ia-bons-02.blizzardonline.net [137.221.66.3]
18 191 ms 187 ms 191 ms 24.105.30.129

Trace complete.
I've called the isp at least 8 times already and have had 3 technicians visit my house. all 3 of them said that nothing was wrong.

 

[haroon453]

probably this has to do with internet congestion during peak hours. share traceroute results of same IP with you ISP from morning and when you start facing latency spikes. The problem you are facing is probably due to bad routing during peak hours.

 

[Flipback012]

probably this has to do with internet congestion during peak hours. share traceroute results of same IP with you ISP from morning and when you start facing latency spikes. The problem you are facing is probably due to bad routing during peak hours.

All right. I'll set a reminder to do a trace route at a high speed time

 

[bill001g]

This problem maybe hard to get fixed. There appears to be a issue between your ISP...which is owned by charter and level3 which is now owned by centurylink

Your traffic also appears to go via dallas which is strange but in itself does not cause the issue. Unfortunately the link that is likely causing the problem is the one that times out. It is hard to say whose router that is.

If there is a capacity issue that far into the connection you tend to not get that fixed. The ISP likely already know about it and choose to not fix it.

What is strange is charter and level3 have multiple interconnects in many cites not sure why it would use the one it is.

You likely will not get this fixed but you might get lucky and it somehow be related to only blizzards internet ip block.

The solution that "might" work is to use a VPN. You are hoping that the ISP the VPN service uses does not travel the same path. Try running the tests to some of the data centers on this link
https://www.privateinternetaccess.com/pages/network/

You may want to run tracert to some of these vpn data centers to see the path.

You would hope that blizzard has good connectivity to one or more of these data centers hopefully circumventing the bottleneck.

This is just one example of a VPN service. There are many more. This one just has a easy to use tool to test throughput.

 

[Flipback012]

So i ran another traceroute to the same server during the day, when the speeds are fine, that looks like this
Tracing route to 24.105.30.129 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 11 ms host-69-145-214-41.chy-wy.client.bresnan.net [69.145.214.41]
4 11 ms 11 ms 12 ms 69.145.247.51
5 33 ms 15 ms 11 ms host-69-145-214-209.chy-wy.client.bresnan.net [69.145.214.209]
6 15 ms 17 ms 17 ms chywy001cr5-XE-3-0-0-U0.int.bresnan.net [69.145.214.166]
7 18 ms 17 ms 17 ms host-69-146-192-2.chy-wy.client.bresnan.net [69.146.192.2]
8 17 ms 17 ms 17 ms host-72-175-110-219.static.bresnan.net [72.175.110.219]
9 43 ms 43 ms 43 ms xe-8-0-2.bar2.boston1.Level3.net [4.68.127.189]
10 * * * Request timed out.
11 69 ms 70 ms 68 ms BLIZZARD-EN.ear3.Dallas1.Level3.net [4.15.45.54]
12 70 ms 71 ms 71 ms ae1-br01-eqda6.blizzardonline.net [137.221.74.33]
13 67 ms 67 ms 67 ms hu-0-0-0-0-pe02-swlv10.blizzardonline.net [137.221.65.67]
14 66 ms 64 ms 64 ms be3-pe01-swlv10.blizzardonline.net [137.221.83.74]
15 74 ms 68 ms 68 ms et-0-0-13-br01-eqla1.blizzardonline.net [137.221.65.68]
16 67 ms 74 ms 67 ms be1-pe01-eqla1.blizzardonline.net [137.221.68.67]
17 70 ms 71 ms 70 ms lax-eqla1-ia-bons-02.blizzardonline.net [137.221.66.3]
18 69 ms 69 ms 67 ms 24.105.30.129

Trace complete.
Also last night i looked into killping. It seemed to drop my ping from around 200 to about 80 but that only worked for the first couple minutes, then rose again to the normal non-proxy ping. I also ran a couple of pings through my vpn ipvanish. the ping was only a bit higher but there were a couple less hops.

 

[bill001g]

So it looks like there are 2 places you have issues.

The first is after hop4. You get about 50 extra MS at that point. You also get a extra 30-40 at hop 10.

Hop5 you might get your ISP to fix since that is all within their network. The main problem will be getting a level 1 tech that knows how to read tracert. Most just know "did you power cycle your modem,router,computer?". Even if they did the level 1 guys generally have no access to the core routers they tend to only have access to the devices that connect to end users houses.

This is one of those times it would be nice to have a different ISP as a option.

 

[Flipback012]

So it looks like there are 2 places you have issues.

The first is after hop4. You get about 50 extra MS at that point. You also get a extra 30-40 at hop 10.

Hop5 you might get your ISP to fix since that is all within their network. The main problem will be getting a level 1 tech that knows how to read tracert. Most just know "did you power cycle your modem,router,computer?". Even if they did the level 1 guys generally have no access to the core routers they tend to only have access to the devices that connect to end users houses.

This is one of those times it would be nice to have a different ISP as a option.

Unfortunately there is no other high speed Internet company in town, or at least one with comparable speeds. Another thing that might make this situation more difficult is that the speeds that they see when they test my modem from the call center are above the speeds that I'm supposed to be getting and they said last night that they don't really care about ping because "there are too many factors in play" I've thought about calling up another one of the ISPs that seem to be causing trouble hops but I really doubt that it would be any different than calling my own isp

 

[bill001g]

I suspect you will see speedtest difference if you were to choose a server in another city. Testing to only your ISP server or a server connected very close to you just means the line between your house and the ISP works. They likely don't want to admit they have a issue with how they have their network connected.

Calling another ISP is a complete waste of time. You have no contract for service with them so they will not talk to you. Even if you found the support line (the nice one that you call on a corporate account) they will ask you with for your account number or the circuit number. When you do not have that information they will figure you are try to hack the network by scamming the techs into doing stuff for you.

Had issue like this on one of our corporate connections and the only way I got to talk to someone was because I worked with someone in the past that now worked for the ISP. I called him and had him conference call the techs that where responsible for that part of the network.

 

[Flipback012]

I suspect you will see speedtest difference if you were to choose a server in another city. Testing to only your ISP server or a server connected very close to you just means the line between your house and the ISP works. They likely don't want to admit they have a issue with how they have their network connected.

Calling another ISP is a complete waste of time. You have no contract for service with them so they will not talk to you. Even if you found the support line (the nice one that you call on a corporate account) they will ask you with for your account number or the circuit number. When you do not have that information they will figure you are try to hack the network by scamming the techs into doing stuff for you.

Had issue like this on one of our corporate connections and the only way I got to talk to someone was because I worked with someone in the past that now worked for the ISP. I called him and had him conference call the techs that where responsible for that part of the network.

Yeah now that you mentioned speed tests mine are a bit weird. All three of them are in my town less than 3 miles away but one of them gives me around 100ms every time and the other gives me 180ms every time. The isp server for ookla gives me 8ms without fail. All from ookla btw