Hey all… I’ve tried searching for this issue but I cant seem to find anyone with it. When I play during the day, Overwatch is great… I usually get around 50 ping. However, after around 9-10 PM, I get terrible lag and around 170 latency showing in game and it’s very noticeable. I have a wired connection and have tried resetting the router, updating my Win10 computer, and repairing Overwatch, all to no avail. Any help would be greatly appreciated.
This is the sign of a network that is oversaturated. Perhaps more people in your neighborhood are online during that time (makes sense). Unfortunately, only the ISP would be able to alleviate the traffic load, so you’d have to consult them about your connection being worse at nighttime.
I could see that, though it always being only at night around the same times seems weird to me. I did check to see if other computers have the same issue and they do, so its probably not me or my setup. Could it be a routing issue? I don’t know why it would route to Overwatch servers differently at night, though.
My brother actually works for our local ISP, and we actually have fiber to the home in the whole area (its a small area though, they probably have 1500-2000 customers total [lucky to have that around here I think]). He’s a bit perplexed too. He’s sort of new there, but he’s supposed to look into it more. Can ISPs even do anything to alleviate the traffic load?
Hey Hyozans,
It’s possible that there’s a routing change happening around that time every night. Easiest way to tell would be to run two traceroutes, one during the day when you have low latency and one at night when the latency is high. Make sure to use the same IP address each time, so for the West coast server it would be: 24.105.30.129
If you want to reply back with those results we can help take a look. Otherwise I’d see if you can get this escalated up through your ISP so their network guys can get in touch with Blizzard’s network team to investigate further.
1 Like
Sorry I took so long to reply! Got busy. So I did the tests, I guess I should just post them here? Is that not advisable security wise?
I will say the tracert during the day it was good ping throughout, and at night, it actually got bad at the 3rd ping, which does belong to the ISP I am at. I have told my brother who works there and he’s going to look into it too.
I would love other eyes on them though, is it okay to post the day tracert and one of the night tracerts?
Yeah, post those tests here.
Okie Dokie.
DAYTIME around 3:30 PM:
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms router.home [192.168.1.1]
2 1 ms <1 ms <1 ms scio-198-15-0-129.static.smt-net. com [198.15.0.129]
3 1 ms 1 ms <1 ms scio-gw-edge-pc3.smt-net. com [198.15.0.252]
4 2 ms 1 ms 1 ms smt-net-border.leb-core-r1.peak. org [69.59.218.101]
5 2 ms 3 ms 2 ms cvo-core-r1.peak. org [69.59.210.169]
6 2 ms 2 ms 2 ms cvo-br1.peak. org [69.59.210.218]
7 3 ms 2 ms 2 ms xe-2-0-0-4000-sur04.corvallis.or.bverton.comcast. net [50.200.51.237]
8 3 ms 3 ms 6 ms ae-11-rur02.corvallis.or.bverton.comcast. net [96.108.80.21]
9 7 ms 6 ms 6 ms ae-50-ar01.troutdale.or.bverton.comcast. net [68.87.222.133]
10 11 ms 12 ms 12 ms be-33490-cr01.seattle.wa.ibone.comcast. net [68.86.92.217]
11 10 ms 10 ms 10 ms be-10846-pe01.seattle.wa.ibone.comcast. net [68.86.86.90]
12 11 ms 9 ms 9 ms 66.208.229.226
13 75 ms 30 ms 30 ms ae1-br01-eqse2.as57976. net [137.221.73.33]
14 30 ms 30 ms 30 ms xe-0-0-0-1-br01-eqsv5.as57976. net [137.221.65.40]
15 30 ms 30 ms 30 ms et-0-0-29-br02-eqsv5.as57976. net [137.221.65.117]
16 30 ms 30 ms 30 ms xe-0-0-1-1-br02-eqla1.as57976. net [137.221.65.6]
17 30 ms 30 ms 30 ms be3-pe02-eqla3.as57976. net [137.221.68.85]
18 31 ms 30 ms 30 ms 24.105.30.129Trace complete.
NIGHTTIME around 9:30 PM:
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms router.home [192.168.1.1]
2 2 ms 3 ms 3 ms scio-198-15-0-129.static.smt-net. com [198.15.0.129]
3 125 ms 119 ms 99 ms scio-gw-edge-pc3.smt-net. com [198.15.0.252]
4 120 ms 101 ms 102 ms smt-net-border.leb-core-r1.peak. org [69.59.218.101]
5 112 ms 109 ms 109 ms cvo-core-r1.peak. org [69.59.210.169]
6 136 ms 113 ms 122 ms cvo-br1.peak. org [69.59.210.218]
7 121 ms 112 ms 103 ms xe-2-0-0-4000-sur04.corvallis.or.bverton.comcast. net [50.200.51.237]
8 136 ms 127 ms 124 ms ae-11-rur02.corvallis.or.bverton.comcast. net [96.108.80.21]
9 164 ms 158 ms 144 ms ae-50-ar01.troutdale.or.bverton.comcast. net [68.87.222.133]
10 140 ms 145 ms 142 ms be-33490-cr01.seattle.wa.ibone.comcast. net [68.86.92.217]
11 140 ms 154 ms 145 ms be-10846-pe01.seattle.wa.ibone.comcast. net [68.86.86.90]
12 176 ms 119 ms 130 ms 66.208.229.226
13 131 ms 128 ms 124 ms ae1-br01-eqse2.as57976. net [137.221.73.33]
14 136 ms 142 ms 144 ms xe-0-0-0-1-br01-eqsv5.as57976. net [137.221.65.40]
15 155 ms 129 ms 137 ms et-0-0-29-br02-eqsv5.as57976. net [137.221.65.117]
16 192 ms 168 ms 171 ms xe-0-0-1-1-br02-eqla1.as57976. net [137.221.65.6]
17 143 ms 217 ms 175 ms be3-pe02-eqla3.as57976. net [137.221.68.85]
18 145 ms 138 ms 145 ms 24.105.30.129Trace complete.
I had to put a space before each com, net, org, etc. because it said I cant have links. For the Night one, like I said I did several but they were all very similar to this one. Occasionally there would be some better pings sprinkled in. It clearly starts with the 3rd one down.
vs
Looks like it’s the oversaturation/high traffic issue I mentioned. During the day the node/hub I quoted has a 1ms ping and at night it has a 99-125ms ping. It’s probably city a neighborhood or city level node/hub, the ISP would know more. The rest of the nodes also appear to be slower, too.
These tests, along with the time of day you ran them, will help demonstrate the issue for the ISP and hopefully make it easy to track down/repair.
I apologize for coming back to this so late, though the issue was only fixed a couple months ago. My phone and Internet company was switching over to a new system that apparently took months and was the reason for the spotty internet at night. It was related to the over-saturation times and the switching over I guess, kind of confusing but I could find out more if anyone cares haha. They are finally finished and I now no longer have issues. Thanks to everyone who helped me with this. Sorry for reviving an old thread.
2 Likes
Hey! Thanks for confirming my suspicions 
1 Like