Players experiencing high ping

First Riot Post
Comment below rating threshold, click here to show it.

RiotJenny

Assistant NOC Manager

06-05-2013
1 of 111 Riot Posts

Hey there summoners,

We are aware that a lot of you are experiencing ping that is higher than normal. I'd really appreciate if you could provide the following information:

1) the Internet Service Provider that you use + where you live
2) Run the script attached to this post and post it to this thread

This information will help us in our on-going efforts to resolve this issue.

Thank you in advance for your assistance.

--

Update:

08/16/13 15:30 PDT - Hey there Summoners! In the past few months, we have worked with several providers in order to identify and fix the service impacting issues on their network. We do realize that there are always inefficiencies in routing, and we will continue to monitor and resolve these issues for you. We are closing this specific thread since we have identified and fixed the issues that we have been able to resolve with our providers, but if you continue to experience issues, please run the Diagnostic Test that we have attached in this post and send them through to Player Support - https://support.leagueoflegends.com/. Thank you all for your contribution in identifying the issues here, and your patience!

08/12/13 12:20 PDT Comcast players: I just heard from our Comcast engineer that they have corrected several service impacting issues on their network and they are certain that this will have a positive impact. They are looking to us to confirm. Are things looking better? If yes or no please post an updated log file so we can compare & continue to track the issue!

08/02/13 14:30 PDT We've moved a large block of players routing to alternate paths to attempt to route around the congestion. Please post new log files to help us determine if we are moving in the right direction. - RiotAntares

07/25/13 15:15 PDT Looks like we've fixed it for a few but made things worse for others. Not what we were hoping for to say the least. We've got one more chance to change things before the weekend so I'm going to make changes again with our provider in an hour or so. I've updated the batch script so it will give us more information and allow us to track our changes better so please keep running it. On that note, please stop using the old script and start using the new one that I've attached here. - RiotAntares

07/23/13 18:20 PDT - We have made changes to peering with our upstream providers to route traffic away from problematic junctions. Please give us feedback on whether your connection has improved, if you are still experiencing poor connections please keep providing us with requested logs.

07/22/13 10:00 PDT - We're continuing to track down the issues. We've spent the day parsing through lots of data and looking for correlation. Our current working theory has to do with a peering dispute between Verizon and a number of other Vendors. None of them directly associated with Riot. Please continue to post logs as soon as things happen. - Akov

07/17/13 19:30 PDT - We've been able to confirm that we solved the major issue for Comcast users from yesterday. We are still looking into other issues, so if you are getting severe lag please post the output from the script. Also, edited the instructions above to just the two bits of information that are the most important. - Akov

07/17/13 00:45 PDT - Was able to locate a pretty severe problem Between Verizon and Comcast and was able to route around it. Its a band-aid until we can get Verzion/Comcast to resolve the issue. What made this one difficult was that traffic was taking a different path in, then it was taking out. So it was only visible from ourside looking back to the players. The most severe problems with Comcast should be resolved, if you continue to have problems please run the script and post so we can dig further. - Akov

07/16/13 11:41 PDT - Verizon (Alternet) has responded and claims to have fixed their issue, if verizon users that were previously having a problem could comment on that it would be great. We are now chasing down the Comcast issue, but need data points from comcast users having the problem. Please play a 20 minute game, with out wireless, with the lag and then run the script. - Akov

07/09/13 13:20 PDT - Hey everyone! I see that our Network Engineers have been addressing your concerns over this thread. We are continuing to push the carriers to take action on the bottleneck in traffic that we've seen, and we are waiting for them to respond. We understand that it's been really frustrating for you guys - trust me, we feel the pain - and we're trying to do our best to communicate this pain to the carriers.

06/25/13 22:55 PDT - Hey everyone! Our Network Engineers have reached out to some carriers in order to address the issues that some of you are continuing to see. At this point, we're waiting to hear back from them regarding a potential bottleneck in traffic and we'll keep you updated as we hear from them. Thanks for your continued patience.

06/18/13 16:30 PDT - Hey Summoners! Sorry for the radio silence for the last 4 days, we've been waiting to hear back from the 2 major carriers that we escalated to. We have been notified that there were some changes performed to help alleviate the congestion. I have attached an awesome script that one of our Network Engineers created (thanks RiotAntares!) for people running Windows 7 (Mac users, a script is coming your way soon too) -> please run this script on your Windows 7. It basically compiles all the tracert/ping information, logs, and some system information that may be critical to our investigation into this issue. Run the script attached below, and attach the .txt file that it creates to your post, and it'll help us to figure out if this issue has been resolved or not.

06/14/13 16:00 PDT - Hey everyone! There was some routing work that was done 7 days ago which has greatly reduced the latency for those of you affected. In addition, we have escalated to the 2 major carriers involved. These companies have told us that there is an upgrade planned soon, and that we should know more next week. There are also additional connections coming online soon that should help more players avoid the bottleneck in question. Thank you for your continued patience and support.

06/11/13 21:15 PDT - Hey everyone, it appears that some of you are still having issues with high ping. We have been talking to our providers, and having them speak to individual ISPs, but since our provider isn't always a direct customer of particular ISPs, it's very difficult to get them to act on it. If you are still experiencing issues, if you could reach out to your ISP and ask to speak to a tier 2 technician and go through the traceroute where you're seeing super high latency, that'd be great.

06/08/13 21:10 PDT - Hey everyone, I hope you guys are having a good weekend. Our Network Engineers have been regularly checking this thread to go through the most recent traceroutes, so if you are still experiencing issues, please continue to post them. Our providers have also been reaching out to the ISPs. Rest assured that they know that this is causing poor game play for you guys, and they are pushing as hard as they can in order to ensure that the ISPs understand the need for a better level of service and connection. Thanks for your continued patience, and we really hope to be able to resolve this soon.

06/07/13 15:35 PDT - Hey Summoners, we are still working with our Network Engineering team and providers to resolve these issues. Unfortunately this can take a bit of time to fully implement the fix. This is still an issue we actively working to address.

06/07/13 00:30 PDT - Hey everyone, we are still working with our Network Engineering team, as well as our providers. We have also reached out to Comcast, who are investigating potential issues on their end. Please continue providing us with traceroutes because we are still actively looking through all of them - and every little helps. Also, if you guys are ever curious on how major ISPs are doing, take a look at http://www.internetpulse.net/ which always has up-to-date information. Thank you all for your continued patience.

06/06/13 15:10 PDT - Hey guys, I know that you are still experiencing high ping - and I do apologize about this. We have been speaking to our provider to get regular updates, and they have opened tickets with individual ISPs in order for them to drill down to the root cause of the issue. We are still actively looking through all your traceroutes, so please keep sending them in. Thanks everyone.

06/05/13 19:24 PDT - Hey guys, we have reached out to our provider and they have contacted Multiple ISPs to see what issues may be causing the latency. We are hoping to have updates for you guys soon.

Attached Files
File Type: zip NA_Network_Diagnostic_Test_v2.zip (1.1 KB, 16818 views)

Comment below rating threshold, click here to show it.

Kari Arisu

This user has referred a friend to League of Legends, click for more information

Senior Member

06-05-2013

Just had a game where most of the enemy team and our ADC d/ced or had high ping for the most of it. I was unaffected. Will the enemy team get loss prevented? I sure hope so.

I use Frontier FiOS and did not have issues.


Comment below rating threshold, click here to show it.

IAmPause

Recruiter

06-05-2013

1. Comcast

2. 100% loss (4/4 loss)

Quote:
C:\Users\iampause>ping 216.133.234.62

Pinging 216.133.234.62 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.133.234.62:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
3. Timed out after 17 hops. Still trying though.

Quote:
C:\Users\iampause>tracert 216.133.234.62

Tracing route to 216.133.234.62 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.1.1
2 38 ms 29 ms 29 ms c-98-215-48-1.hsd1.il.comcast.net [removed]
3 11 ms 16 ms 8 ms te-9-5-ur02.[removed].il.chicago.comcast.net [68.85.179.45]
4 10 ms 12 ms 11 ms te-0-0-0-7-sur01.[removed].il.chicago.comcast.net [68.87.233.9]
5 15 ms 19 ms 17 ms te-0-7-0-7-ar01.area4.il.chicago.comcast.net [69.139.200.197]
6 25 ms 23 ms 23 ms he-3-10-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.93.181]
7 16 ms 16 ms 16 ms pos-1-3-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.158]
8 66 ms 49 ms 52 ms te0-7-0-17.ccr21.ord03.atlas.cogentco.com [154.54.10.253]
9 56 ms 16 ms 16 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.73]
10 86 ms 83 ms 89 ms te0-0-0-3.mpd22.mci01.atlas.cogentco.com [154.54.25.77]
11 86 ms 82 ms 77 ms te0-4-0-5.ccr21.dfw01.atlas.cogentco.com [154.54.46.198]
12 129 ms 91 ms 86 ms te0-1-0-1.mpd21.iah01.atlas.cogentco.com [154.54.25.94]
13 75 ms 75 ms 76 ms te0-0-0-5.mpd22.lax01.atlas.cogentco.com [154.54.0.241]
14 77 ms 75 ms 78 ms te8-1.mag02.lax01.atlas.cogentco.com [154.54.47.170]
15 76 ms 77 ms 77 ms internap.com [38.104.82.234] 16 78 ms 76 ms 96 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.255.103]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


Comment below rating threshold, click here to show it.

TheEnigmaBlade

This user has referred a friend to League of Legends, click for more information

Senior Member

06-05-2013

1. Verizon FiOS (in Northern VA)

2.

Quote:
> ping 216.52.255.103

Pinging 216.52.255.103 with 32 bytes of data:
Reply from 216.52.255.103: bytes=32 time=162ms TTL=249
Reply from 216.52.255.103: bytes=32 time=164ms TTL=249
Reply from 216.52.255.103: bytes=32 time=159ms TTL=249
Reply from 216.52.255.103: bytes=32 time=198ms TTL=249

Ping statistics for 216.52.255.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 159ms, Maximum = 198ms, Average = 170ms

> ping 50.203.115.149

Pinging 50.203.115.149 with 32 bytes of data:
Reply from 50.203.115.149: bytes=32 time=102ms TTL=55
Reply from 50.203.115.149: bytes=32 time=101ms TTL=55
Reply from 50.203.115.149: bytes=32 time=93ms TTL=55
Reply from 50.203.115.149: bytes=32 time=138ms TTL=55

Ping statistics for 50.203.115.149:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 138ms, Average = 108ms

> ping 208.76.153.129

Pinging 208.76.153.129 with 32 bytes of data:
Reply from 208.76.153.129: bytes=32 time=116ms TTL=247
Reply from 208.76.153.129: bytes=32 time=89ms TTL=247
Reply from 208.76.153.129: bytes=32 time=91ms TTL=247
Reply from 208.76.153.129: bytes=32 time=90ms TTL=247

Ping statistics for 208.76.153.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 116ms, Average = 96ms
3.
Quote:
>tracert 216.52.255.103

Tracing route to border1.po2-20g-bbnet2.lax010.pnap.net [216.52.255.103]
over a maximum of 30 hops:

1 25 ms 1 ms 1 ms 192.168.1.1
2 18 ms 7 ms 11 ms L100.CLPPVA-VFTTP-11.verizon-gni.net [98.118.244.1]
3 12 ms 9 ms 12 ms G0-1-0-3.CLPPVA-LCR-22.verizon-gni.net [130.81.223.60]
4 46 ms 57 ms 40 ms xe-1-1-3-0.RES-BB-RTR1.verizon-gni.net [130.81.209.72]
5 80 ms 76 ms 77 ms 0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]
6 87 ms 84 ms 81 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
7 138 ms 131 ms 131 ms internapGIGE-gw.customer.alter.net [157.130.236.110]
8 151 ms 152 ms 133 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.255.103]

Trace complete.

>tracert 50.203.115.149

Tracing route to xe-10-2-0-32767-sur01.beaverton.or.bverton.comcast.net [50.203.115.149]
over a maximum of 30 hops:

1 1 ms 3 ms 1 ms 192.168.1.1
2 7 ms 9 ms 8 ms L100.CLPPVA-VFTTP-11.verizon-gni.net [98.118.244.1]
3 9 ms 24 ms 7 ms G0-1-0-3.CLPPVA-LCR-22.verizon-gni.net [130.81.223.60]
4 9 ms 8 ms 8 ms xe-1-1-3-0.RES-BB-RTR1.verizon-gni.net [130.81.209.72]
5 7 ms 10 ms 9 ms 0.xe-8-2-1.XL2.IAD8.ALTER.NET [152.63.8.13]
6 10 ms 10 ms 9 ms 0.xe-11-2-0.GW12.IAD8.ALTER.NET [152.63.35.130]
7 20 ms 16 ms 14 ms customer.alter.net.customer.alter.net [152.179.50.206]
8 15 ms 19 ms 26 ms he-2-4-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.83.65]
9 62 ms 61 ms 61 ms he-4-3-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.150]
10 46 ms 49 ms 47 ms pos-1-13-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.88.238]
11 65 ms 114 ms 72 ms pos-2-6-0-0-cr01.denver.co.ibone.comcast.net [68.86.89.109]
12 129 ms 126 ms 128 ms pos-0-7-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.87.66]
13 168 ms 133 ms 129 ms so-6-1-0-0-ar03.troutdale.or.bverton.comcast.net [68.86.90.214]
14 139 ms 135 ms 135 ms ae-0-0-ar03.beaverton.or.bverton.comcast.net [68.87.218.157]
15 138 ms 144 ms 142 ms xe-10-2-0-32767-sur01.beaverton.or.bverton.comcast.net [50.203.115.149]

Trace complete.

>tracert 208.76.153.129

Tracing route to cr1-fdcp-t4-2.bb.spectrumnet.us [208.76.153.129]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 11 ms L100.CLPPVA-VFTTP-11.verizon-gni.net [98.118.244.1]
3 8 ms 6 ms 7 ms G0-1-0-4.CLPPVA-LCR-22.verizon-gni.net [130.81.223.62]
4 19 ms 9 ms 7 ms xe-1-1-3-0.RES-BB-RTR1.verizon-gni.net [130.81.209.72]
5 9 ms 10 ms 9 ms 0.xe-10-1-0.BR3.IAD8.ALTER.NET [152.63.7.221]
6 28 ms 32 ms 29 ms 204.255.168.226
7 95 ms 93 ms 94 ms 207.88.14.162.ptr.us.xo.net [207.88.14.162]
8 86 ms 103 ms 102 ms te-3-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.9]
9 95 ms 91 ms 94 ms te-3-0-0.rar3.dallas-tx.us.xo.net [207.88.12.2]
10 88 ms 94 ms 86 ms te-3-2-0.rar3.denver-co.us.xo.net [207.88.12.42]
11 93 ms 88 ms 87 ms te-3-0-0.rar3.seattle-wa.us.xo.net [207.88.12.81]
12 87 ms 86 ms 88 ms ae0d0.cir1.seattle7-wa.us.xo.net [207.88.13.141]
13 313 ms 241 ms 225 ms 216.156.100.14.ptr.us.xo.net [216.156.100.14]
14 93 ms 91 ms 92 ms cr1-fdcp-t4-2.bb.spectrumnet.us [208.76.153.129]

Trace complete.
4-6: I'll get those when I can.


Comment below rating threshold, click here to show it.

CptBang

This user has referred a friend to League of Legends, click for more information

Junior Member

06-05-2013

Sorry, wasn't able to get a screenshot, but ping was around 300-400. Provider is Verizon FiOS

C:\Users\MOO>ping 216.133.234.62

Pinging 216.133.234.62 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.133.234.62:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)


C:\Users\MOO>tracert 216.133.234.62

Tracing route to 216.133.234.62 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 8 ms 9 ms L100.LSANCA-VFTTP-74.verizon-gni.net [72.67.85.1
]
3 14 ms 11 ms 18 ms G0-6-3-5.LSANCA-LCR-22.verizon-gni.net [130.81.1
05.8]
4 35 ms 61 ms 88 ms ae4-0.LAX01-BB-RTR2.verizon-gni.net [130.81.199.
114]
5 12 ms 8 ms 18 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.121]
6 14 ms 18 ms 9 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
7 26 ms 27 ms 27 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
8 25 ms 28 ms 28 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.103]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Comment below rating threshold, click here to show it.

CPaladino

Senior Member

06-05-2013

Timewarner in Aurora, Ohio.
Ping & Tracerout timed out.

---

Pinging 216.133.234.62 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.133.234.62:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
---


C:\Users\Chris>tracert 216.133.234.62

Tracing route to 216.133.234.62 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms 192.168.0.1
2 13 ms 8 ms 6 ms 10.5.64.1
3 7 ms 8 ms 10 ms tge3-7.mcdnoh1-swt401.neo.rr.com [24.164.111.20]

4 9 ms 6 ms 13 ms tge1-5.kentoh1-swt401.neo.rr.com [24.164.117.122
]
5 11 ms 15 ms 15 ms tge0-9-0-3.pltsohae-ccr03.midwest.rr.com [24.164
.112.128]
6 12 ms 15 ms 15 ms network-065-029-001-032.midwest.rr.com [65.29.1.
32]
7 22 ms 23 ms 23 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
8 20 ms 19 ms 19 ms ae-2-0.c1.nyc90.tbone.rr.com [66.109.1.49]
9 18 ms 17 ms 18 ms te0-7-0-11.mpd22.iad02.atlas.cogentco.com [154.5
4.10.209]
10 20 ms 20 ms 19 ms te0-4-0-5.mpd22.dca01.atlas.cogentco.com [154.54
.41.253]
11 38 ms 33 ms 41 ms te0-1-0-7.mpd22.atl01.atlas.cogentco.com [154.54
.28.14]
12 * * * Request timed out.
13 273 ms 271 ms * te0-0-0-5.mpd22.lax01.atlas.cogentco.com [154.54
.0.241]
14 * * 226 ms te8-1.mag02.lax01.atlas.cogentco.com [154.54.47.
170]
15 * 228 ms 227 ms internap.com [38.104.82.234]
16 227 ms 228 ms * border1.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.103]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 *

Attached Images
File Type: jpg Capture.JPG (49.6 KB, 1733 views)

Comment below rating threshold, click here to show it.

Faelara

This user has referred a friend to League of Legends, click for more information

Senior Member

06-05-2013

1. Comcast

2. ping 216.133.234.62

Pinging 216.133.234.62 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.133.234.62:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

3. tracert 216.133.234.62

Tracing route to 216.133.234.62 over a maximum of 30 hops

1 38 ms 4 ms 4 ms RT-N66U [192.168.1.1]
2 13 ms 11 ms 11 ms 96.120.15.9
3 13 ms 16 ms 12 ms te-8-4-ur01.southshrvprt.la.malt.comcast.net [68
.86.243.185]
4 17 ms 15 ms 14 ms te-9-1-ur01.mainshrvprt.la.malt.comcast.net [68.
86.240.193]
5 14 ms 13 ms 13 ms te-5-7-ur02.mainshrvprt.la.malt.comcast.net [68.
86.240.198]
6 32 ms 24 ms 22 ms te-0-15-0-6-ar02.dannythomas.tn.malt.comcast.net
[162.151.12.13]
7 30 ms 35 ms 32 ms pos-3-3-0-0-cr01.dallas.tx.ibone.comcast.net [68
.86.93.101]
8 32 ms 31 ms 35 ms pos-0-1-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.94]
9 69 ms 73 ms 67 ms as174.1950stemmons.tx.ibone.comcast.net [173.167
.56.166]
10 64 ms 68 ms 71 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
11 71 ms 72 ms 82 ms te0-2-0-2.mpd22.iah01.atlas.cogentco.com [154.54
.25.98]
12 68 ms 66 ms 67 ms te0-2-0-5.mpd22.lax01.atlas.cogentco.com [154.54
.0.249]
13 66 ms 74 ms 64 ms te8-1.mag02.lax01.atlas.cogentco.com [154.54.47.
170]
14 67 ms 68 ms 67 ms internap.com [38.104.82.234]
15 388 ms 385 ms 384 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.103]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

4. Can't seem to take a screenshot with print screen, just shows a black screen. Here's proof from my twitch.tv stream instead. http://www.twitch.tv/faelara/b/413079899?t=5m59s


Comment below rating threshold, click here to show it.

Azuchi

Junior Member

06-05-2013

ISP: Verizon Fios (I'm using my girlfriends internet)

Tracing route to border1.te9-3.riotgames-55.lax010.pnap.net [64.7.194.1]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms myrouter.home [192.168.1.1]
2 6 ms 6 ms 6 ms L100.LSANCA-VFTTP-114.verizon-gni.net [173.58.211.1]
3 22 ms 11 ms 11 ms G0-9-1-4.LSANCA-LCR-22.verizon-gni.net [130.81.185.70]
4 19 ms 12 ms 11 ms so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81199.40]
5 14 ms 14 ms 13 ms 0.xe-7-1-1.XL4.LAX15.ALTER.NET [152.63.6.69]
6 12 ms 11 ms 11 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
7 52 ms 53 ms 52 ms internapGIGE-gw.customer.alter.net [157.130.236.110]
8 54 ms 53 ms 50 ms border1.te9-3.riotgames-55.lax010.pnap.net [64.7194.1]

Pinging 216.133.234.62 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.133.234.62:

Here you go, may it help you solve this issue.

Attached Thumbnails
Click image for larger version

Name:	badping.png
Views:	5465
Size:	58.0 KB
ID:	699759   Click image for larger version

Name:	badpinggame.png
Views:	4204
Size:	61.9 KB
ID:	699760  

Comment below rating threshold, click here to show it.

Irojo

Junior Member

06-05-2013

I am running a mac. I used network utility and used the default send only 10 pings option. If I am doing this wrong if someone would let me know it'd be appreciated.

1) Verizon LLC
2)

Ping has started…

PING 216.133.234.62 (216.133.234.62): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

--- 216.133.234.62 ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss

3)
I used the traceroute tab of the "Network Utility" as I am running a Mac


Traceroute has started…

traceroute: hostname "216.133.234.62

PING 216.133.234..." is too long

4) I'm not in game, but it was VERY consistently the same ping 320-340 during the game although it was closer to 400 during loading screen. The ping is noticeable and I experienced absolutely no spikes just consistently the same high ping.


Comment below rating threshold, click here to show it.

raorbit

Junior Member

06-05-2013

1) the Internet Service Provider that you use: Verizon FiOS In The Washington Dc area
2) results of running /ping 216.133.234.62 in your Command Prompt: The request has timed out 4 times with a 100% packet loss
3) results of running /tracert 216.133.234.62 in your Command Prompt:C:\Users\Rahul>tracert 216.133.234.62

Tracing route to 216.133.234.62 over a maximum of 30 hops

1 2 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 9 ms 6 ms L100.WASHDC-VFTTP-85.verizon-gni.net [96.255.15.
1]
3 12 ms 15 ms 11 ms G0-6-3-5.WASHDC-LCR-22.verizon-gni.net [130.81.1
90.150]
4 20 ms 9 ms 12 ms ae5-0.RES-BB-RTR1.verizon-gni.net [130.81.209.22
2]
5 133 ms 81 ms 82 ms 0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]
6 79 ms 82 ms 81 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
7 93 ms 96 ms 95 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
8 95 ms 89 ms 87 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.103]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
4) a screenshot of your in-game ping when you see it as higher than normal: I dont have a screenshot but it went from 80 on average to 160 now.