• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Can Someone Explain A Networking/Lag Issue to Me?

C

CK011885

Joined
Jan 30, 2013
Messages
70 (0.02/day)
System Specs
Processor i5-6600k (4.2 GHz)
Motherboard Asus Z170-P D3
Memory Crucial 16GB DDR3L 1600MHz
Video Card(s) GTX 970
Storage Samsung 850 Pro
Display(s) Philips 272G5DYEB + Samsung LED HDTV
Case Cooler Master HAF 912
Power Supply Corsair 700W
Software Windows 8.1 64 Bit
So here's the situation. I play the game League of Legends and for the last week during peak time, people with Verizon and Telus ISP's are experiencing high ping and some packet loss. The majority of players are fine, it's only those with these two ISP who are experiencing issues. So the weird part comes when performing a trace route to their servers, 104.160.131.1 and 104.160.131.3 we were given to us to test.

http://imgur.com/ioMluAe

http://imgur.com/JqFWb74

As you can see, the high ping and packet loss does not occur until the packets actually reach Riot's servers, which would seem to indicate that the problem is on their end. But, like I mentioned, only people with Verizon and Telus are lagging. There are thousands of other players with other ISP's playing without any issues right now. Contacting Verizon support is not helpful, they claim it's not their problem, and Riot doesn't give any information. Can anyone put forth a suggestion as to what might be going on here?
 
Last edited:
likely a peering/interconnection problem \
that last hop looks like a inter-connect node between riot and the rest of the backbone likely verizon's peering link isn't fast enough
 
Must be a zone problem Im on Verizon in the south and I dont have an issue

Code: 
tracert 104.160.131.1

Tracing route to 104.160.131.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Chronos.TDE [192.168.1.1]
  2     5 ms     3 ms     3 ms  lo0-100.TAMPFL-VFTTP-307.verizon-gni.net [96.254.182.1]
  3     7 ms     5 ms     5 ms  T0-2-0-6.TAMPFL-LCR-22.verizon-gni.net [130.81.32.38]
  4     *        *        *     Request timed out.
  5    12 ms    11 ms    10 ms  0.ae4.BR1.MIA19.ALTER.NET [140.222.225.113]
  6    10 ms     9 ms     8 ms  204.255.168.238
  7    11 ms    10 ms    19 ms  ae2.mpr1.mia1.us.zip.zayo.com [64.125.30.193]
  8    35 ms    32 ms    33 ms  ae10.cr1.dca2.us.zip.zayo.com [64.125.20.193]
  9    36 ms    36 ms    37 ms  v11.ae29.cr1.lga5.us.zip.zayo.com [64.125.31.205]
 10     *       37 ms    38 ms  ae10.mpr3.lga7.us.zip.zayo.com [64.125.20.77]
 11    38 ms    36 ms    38 ms  128.177.169.158.IPYX-089814-970-ZYO.zip.zayo.com [128.177.169.158]
 12    37 ms    38 ms    35 ms  104.160.132.35
 13    42 ms    43 ms    42 ms  ae31-br01.chi01.riotdirect.net [104.160.159.14] 
 14    42 ms    42 ms    41 ms  104.160.131.1

Trace complete.
 
Solaris17 said:
Must be a zone problem Im on Verizon in the south and I dont have an issue

Code: 
tracert 104.160.131.1

Tracing route to 104.160.131.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Chronos.TDE [192.168.1.1]
  2     5 ms     3 ms     3 ms  lo0-100.TAMPFL-VFTTP-307.verizon-gni.net [96.254.182.1]
  3     7 ms     5 ms     5 ms  T0-2-0-6.TAMPFL-LCR-22.verizon-gni.net [130.81.32.38]
  4     *        *        *     Request timed out.
  5    12 ms    11 ms    10 ms  0.ae4.BR1.MIA19.ALTER.NET [140.222.225.113]
  6    10 ms     9 ms     8 ms  204.255.168.238
  7    11 ms    10 ms    19 ms  ae2.mpr1.mia1.us.zip.zayo.com [64.125.30.193]
  8    35 ms    32 ms    33 ms  ae10.cr1.dca2.us.zip.zayo.com [64.125.20.193]
  9    36 ms    36 ms    37 ms  v11.ae29.cr1.lga5.us.zip.zayo.com [64.125.31.205]
10     *       37 ms    38 ms  ae10.mpr3.lga7.us.zip.zayo.com [64.125.20.77]
11    38 ms    36 ms    38 ms  128.177.169.158.IPYX-089814-970-ZYO.zip.zayo.com [128.177.169.158]
12    37 ms    38 ms    35 ms  104.160.132.35
13    42 ms    43 ms    42 ms  ae31-br01.chi01.riotdirect.net [104.160.159.14]
14    42 ms    42 ms    41 ms  104.160.131.1

Trace complete.
Click to expand...

The issue is not on-going right this moment, I'm running a trace route right now and ping is fine. It's usually 6 or 7 PM EDT till anywhere from 8-11 PM EDT. It also comes and goes. It seemed fine about 40 minutes ago, then 10 minutes after that came back, and right now it's fine again.
 
CK011885 said:
The issue is not on-going right this moment, I'm running a trace route right now and ping is fine. It's usually 6 or 7 PM EDT till anywhere from 8-11 PM EDT. It also comes and goes. It seemed fine about 40 minutes ago, then 10 minutes after that came back, and right now it's fine again.
Click to expand...

Either way iv never experienced a connection problem. I wouldnt say its wholly a verizon or Telus issue.
 
Pingplotter is showing consistent 100% packet loss at a Level3 router in Chicago for me on both targets.. I didn't see this topic until after the timeframe you mentioned, but I'll keep it running and see if losses show up anywhere else.

EUBWohv.png
 
Last edited:
You must log in or register to reply here.
Back
Top