Keyru (NA)
: [Resolved] 4/28 Server Issues - Ranked Disabled/Reconnect Spikes
Hey guys, I used to do Incident Management for Chase Bank. I would be more than happy to help get something similar to what they have set up as far as managing incidents and releasing communications.
: Hey Mowens, Because your issue is a little different from the issue that everyone else is experiencing, I'd recommend you [submit a support ticket](https://support.riotgames.com/hc/en-us/requests/new) so our techs can further investigate this issue.
Sorry if I wasn't clear before - I was seeingthe same symptoms as everyone else. It has been resolved since yesterday. I came back to the board to point out what I thought was another symptom, but everything appears to be great.
: Hey All, Wide Open West made a change that may have resolved this issue. Please let me know if you're experiencing this issue tonight so we can verify that the issue has been resolved! Thanks!
Will do. Also, I was going to point out on this board that I get some packet loss at all times of day, regardless of if the latency issue is a problem. I have confirmed that it is still occurring. Below, is the results of a pathping right now, while the issue normally doesnt exist for me. Tracing route to 104.160.131.1 over a maximum of 30 hops 0 DNA1 [192.168.1.104] 1 192.168.1.1 2 192.168.0.1 3 d28-23-1-198.dim.wideopenwest.com [23.28.198.1] 4 76-73-166-101.knology.net [76.73.166.101] 5 76-73-167-218.knology.net [76.73.167.218] 6 76-73-167-89.knology.net [76.73.167.89] 7 76-73-166-126.knology.net [76.73.166.126] 8 76-73-166-125.knology.net [76.73.166.125] 9 static-69-73-0-139.knology.net [69.73.0.139] 10 dynamic-75-76-35-10.knology.net [75.76.35.10] 11 dynamic-75-76-35-6.knology.net [75.76.35.6] 12 104.160.131.1 Computing statistics for 300 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 DNA1 [192.168.1.104] 0/ 100 = 0% | 1 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 5ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1 0/ 100 = 0% | 3 14ms 0/ 100 = 0% 0/ 100 = 0% d28-23-1-198.dim.wideopenwest.com [23.28.198.1] 0/ 100 = 0% | 4 15ms 0/ 100 = 0% 0/ 100 = 0% 76-73-166-101.knology.net [76.73.166.101] 0/ 100 = 0% | 5 15ms 0/ 100 = 0% 0/ 100 = 0% 76-73-167-218.knology.net [76.73.167.218] 0/ 100 = 0% | 6 15ms 0/ 100 = 0% 0/ 100 = 0% 76-73-167-89.knology.net [76.73.167.89] 0/ 100 = 0% | 7 16ms 0/ 100 = 0% 0/ 100 = 0% 76-73-166-126.knology.net [76.73.166.126] 0/ 100 = 0% | 8 16ms 0/ 100 = 0% 0/ 100 = 0% 76-73-166-125.knology.net [76.73.166.125] 0/ 100 = 0% | 9 23ms 0/ 100 = 0% 0/ 100 = 0% static-69-73-0-139.knology.net [69.73.0.139] 0/ 100 = 0% | 10 25ms 0/ 100 = 0% 0/ 100 = 0% dynamic-75-76-35-10.knology.net [75.76.35.10] 0/ 100 = 0% | 11 26ms 0/ 100 = 0% 0/ 100 = 0% dynamic-75-76-35-6.knology.net [75.76.35.6] 9/ 100 = 9% | 12 24ms 9/ 100 = 9% 0/ 100 = 0% 104.160.131.1 Trace complete.
: 220MS+ ping issues on WOW! Internet
Same exact issue. Usually clears up around 11:30 PM EST. Located in Columbus, Ohio. Traceroute: Tracing route to 104.160.131.1 over a maximum of 30 hops 1 1 ms 2 ms 2 ms 192.168.1.1 2 5 ms 11 ms 7 ms 192.168.0.1 3 22 ms 17 ms 16 ms d28-23-1-198.dim.wideopenwest.com [23.28.198.1] 4 25 ms 19 ms 20 ms 76-73-166-101.knology.net [76.73.166.101] 5 26 ms 24 ms 33 ms 76-73-167-218.knology.net [76.73.167.218] 6 33 ms 18 ms 16 ms 76-73-167-89.knology.net [76.73.167.89] 7 26 ms 29 ms 17 ms 76-73-166-126.knology.net [76.73.166.126] 8 23 ms 21 ms 18 ms 76-73-166-125.knology.net [76.73.166.125] 9 42 ms 38 ms 31 ms static-69-73-0-139.knology.net [69.73.0.139] 10 22 ms 32 ms 35 ms dynamic-75-76-35-10.knology.net [75.76.35.10] 11 33 ms 23 ms 34 ms dynamic-75-76-35-6.knology.net [75.76.35.6] 12 221 ms 229 ms 239 ms 104.160.131.1

Mowens

Level 149 (NA)
Lifetime Upvotes
Create a Discussion