As you can see from other posts alot of people from the southern states like texas, louisiana (this is where I live) and Mississippi are blocked from the client chat functions meaning: They can't see their friends list, they can't message anyone, they can't invite anyone, and probably more importantly they can't talk in pre game and post game lobbies.
Not a PC issue. this is a Riot related issue.
Resolve this quickly Riot, or the South will rise again!
Hey folks,
We want to understand this issue a bit better, could you please run tracerts to 192.64.174.69 and post here the results? It will help us towards investigation.
Instructions on how to perform tracerts can be found here https://support.riotgames.com/hc/en-us/articles/201752674-Network-System-and-League-of-Legends-Logs#wq2
Thanks!
I'm having the same problem here in Tennessee, and I doubt its the ISP because what are the odds we all have the same provider.
Can you advise if chat is connecting now? For those of you who still have problems - please provide the traceroute requested as it'll help us narrow down the cause.
Thanks
If it's isolated to a region, it's probably not a Riot issue, either. More likely ISP.
My chat actually disconnected last night around midnight and I couldn't reconnect to it. So it's been that way ever since.
I am having the same issue as well. I ran the tracerts and got this:
Tracing route to 104.160.131.1 over a maximum of 30 hops
1 63 ms 1 ms <1 ms homeportal [192.168.1.254] 2 24 ms 24 ms 22 ms 108-227-204-3.lightspeed.austtx.sbcglobal.net [108.227.204.3] 3 23 ms 22 ms 23 ms 75.8.128.122 4 24 ms 44 ms 23 ms 75.8.128.94 5 26 ms 24 ms 23 ms 12.83.68.145 6 29 ms 28 ms 28 ms 12.122.85.197 7 29 ms 28 ms 28 ms 206.121.120.30 8 51 ms 51 ms 51 ms 104.160.134.35 9 49 ms 48 ms 48 ms ae35-br02.chi01.riotdirect.net [104.160.159.24] 10 51 ms 50 ms 50 ms ae1-br01.chi01.riotdirect.net [104.160.159.8] 11 51 ms 51 ms 51 ms 104.160.131.1
Trace complete.
Hope this helps.
Edit: 1 minute after running this I was able to connect to chat.
Still not working. Location: Missouri.
Tracing route to 192.64.174.69 over a maximum of 30 hops
1 1 ms 3 ms 2 ms tjrh-c14d00-vrfresn-rtr.network.mst.edu [131.151.180.254] 2 <1 ms <1 ms <1 ms 172.16.128.74 3 <1 ms <1 ms <1 ms brdr-nccs-096-vrfresn-rtr.network.mst.edu [172.16.129.185] 4 1 ms <1 ms <1 ms core-nccs-010-vrfinet-rtr.network.mst.edu [172.16.97.186] 5 1 ms <1 ms <1 ms core-ncpk-010-vrfinet-rtr.network.mst.edu [131.151.254.18] 6 21 ms 2 ms 2 ms umicn-ro-tengige0-0-0-2-303.um.more.net [150.199.4.77] 7 12 ms 11 ms 12 ms umicn-kc-tengige0-0-0-1-100-1.um.more.net [150.199.4.46] 8 9 ms 9 ms 9 ms ks-96-xe-1-1-0-731.greatplains.net [164.113.254.237] 9 20 ms 19 ms 19 ms ae-4.493.rtr.dall3.net.internet2.edu [64.57.29.201] 10 19 ms 19 ms 19 ms 162.252.69.181 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.
Mine just connected.. Dunno if Riot fixed or what but, Amen!
Chat's back up and working! Thanks all the rioters that helped out!!! We love you!
Thx Riot!
I can confirm its fixed now.
Chat is working for me now! Thank you for your haste on this matter! Guys post your Traceroute so they can help you quickly! Well Right after I posted this I was Disconnected from chat again! What gives?!
Welp...I just got into champ select and I just disconnected again..
Same as Xeila :(
Just confirming: This worked for a period and has stopped working again?
Yes It worked and then it stopped...
I lost chat again.. Wont reconnect, omfg, this is getting annoying as F
Tracing route to 104.160.131.1 over a maximum of 30 hops
1 1 ms 1 ms 1 ms dsldevice.att.net [192.168.1.254] 2 12 ms 12 ms 15 ms 108-215-76-3.lightspeed.rcsntx.sbcglobal.net [108.215.76.3] 3 * * * Request timed out. 4 16 ms 15 ms 14 ms 12.83.80.193 5 15 ms 13 ms 13 ms 12.122.85.197 6 14 ms 21 ms 18 ms 206.121.120.30 7 37 ms 37 ms 37 ms 104.160.134.35 8 34 ms 34 ms 34 ms ae35-br02.chi01.riotdirect.net [104.160.159.24] 9 35 ms 35 ms 35 ms ae1-br01.chi01.riotdirect.net [104.160.159.8] 10 36 ms 36 ms 36 ms 104.160.131.1
Trace complete.
So it disconnected in champ select but now its working in game so idk......
Please let me know if this issue continues now. We've taken offline what looks to be the offending device to work on it.
I too am having this issue from TX... Tracing route to 192.64.174.69 over a maximum of 30 hops
1 7 ms 9 ms 4 ms 192.168.0.1 2 29 ms 30 ms 29 ms tx-71-51-104-1.dhcp.embarqhsd.net [71.51.104.1] 3 29 ms 29 ms 31 ms klln-agw1.inet.qwest.net [75.160.229.1] 4 37 ms 36 ms 37 ms dax-edge-03.inet.qwest.net [67.14.2.174] 5 36 ms 37 ms 37 ms 65.156.231.230 6 59 ms 55 ms 55 ms 104.160.134.52 7 * * * Request timed out. 8 * * * Request timed out. 9 79 ms 84 ms 77 ms 104.160.128.101 10 * * * Request timed out. 11 79 ms 81 ms 86 ms 192.64.174.69
Trace complete.
Tracing route to 104.160.131.1 over a maximum of 30 hops
Tracing route to 104.160.131.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1 2 8 ms 10 ms 8 ms 96.120.17.21 3 8 ms 19 ms 7 ms xe-3-0-3-sur03.egypt.tx.houston.comcast.net [68.85.253.153] 4 10 ms 9 ms 9 ms ae-41-ar01.bearcreek.tx.houston.comcast.net [68.85.244.97] 5 16 ms 17 ms 16 ms be-33662-cr02.dallas.tx.ibone.comcast.net [68.86.92.61] 6 14 ms 16 ms 14 ms 68.86.89.250 7 14 ms 14 ms 14 ms comcast-gw.la1.unitedlayer.com [75.149.228.202] 8 34 ms 32 ms 33 ms 104.160.134.35 9 33 ms 34 ms 32 ms ae35-br02.chi01.riotdirect.net [104.160.159.24] 10 34 ms 33 ms 33 ms ae1-br01.chi01.riotdirect.net [104.160.159.8] 11 41 ms 41 ms 45 ms 104.160.131.1
Trace complete.
This is all the data provided in the Txt file. Please help as this is clearly not an issue for one or two dozen people but several hundreds and possibly thousands of users.
Tracing route to 192.64.174.69 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1 2 10 ms 11 ms 11 ms 10.98.192.1 3 14 ms 16 ms 10 ms 192.168.22.105 4 26 ms 24 ms 25 ms ae1.er2.dfw2.us.zip.zayo.com [208.184.232.181] 5 * * 34 ms ae8.er1.dfw2.us.zip.zayo.com [64.125.29.121] 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 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.
Tracing route to 104.160.131.1 over a maximum of 30 hops
1 1 ms 3 ms 1 ms 100.65.1.1 2 1 ms 3 ms 1 ms 108.169.216.1 3 21 ms 20 ms 20 ms 12.247.201.9 4 21 ms 32 ms 25 ms cr2.dlstx.ip.att.net [12.122.138.202] 5 * * * Request timed out. 6 21 ms 22 ms 23 ms 12.122.85.197 7 21 ms 27 ms 21 ms 206.121.120.30 8 43 ms 56 ms 43 ms 104.160.134.35 9 45 ms 43 ms 43 ms ae35-br02.chi01.riotdirect.net [104.160.159.24] 10 47 ms 44 ms 47 ms ae1-br01.chi01.riotdirect.net [104.160.159.8] 11 44 ms 45 ms 44 ms 104.160.131.1
Trace complete.
mine is till not working Lubbock, Texas
