RiotKorensky

RiotKorensky



28 Jan

Comment

Originally posted by Fatblard

I have an ongoing case with Verizon Executive relations about problems with ping spikes/jitter for about 2 weeks now and the same issues as described in this post. https://imgur.com/a/FZzT4rG https://imgur.com/a/4pAtZXd These are logs for 6 and 24 hours a week and a half ago. This sort of jitter is abnormal correct RiotKorensky? It seems alter.net and Verizon-gni.net are both owned by Verizon

Yes - hop 1 there is bad. You will probably hear them tell stories about how ICMP is de-prioritized but this looks like congestion or over-subscription on your access segment / last mile, assuming that the first hop you are seeing here is the PON ONU. They should be inspecting counters on your OLT for errors as part of triage here to make sure there's nothing specific to your drop that may be the cause.


27 Jan

Comment

Originally posted by tnmw

YUP!

Can confirm the stats for Verizon were not good but this was not the same problem. Looks like it was possibly an outage of some sort as the packet loss went through the roof. Going to be keeping an eye on it through evening peak again tonight to see what we can do. I'll try and wrangle some contacts at Verizon as well to see if we can find a better long term solution to this as well.


26 Jan

Comment

Originally posted by Mmrysignal

I pinged the ip you provided and it is timed out. This game is unplayable any more due to this serve lag. Other games are all normal to me. Only lol is lagging. It started one or two months ago and was improved for certain days but now is completely unplayable. The characters are hoping on the map now.

This is not the Verizon problem this thread is about. Please log a player support ticket at http://support.riotgames.com


24 Jan

Comment

Originally posted by worthlesston

I'm not sure about other east coasters, but it is fairly unpredictable on a game by game basis. Will you (or someone else on the team) check this thread tomorrow when we get another surge of lag? I just finished an ARAM where I was fine but my wife (same room, nearly identical hardware, same software, same internet) was sitting at 150 ping with occasional spikes of well over 1k. Running the traceroute just after the game shows 3 hops, each <5 ms. I will DM the full thing to you though.

I forgot Verizon don't want their customers being able to run traces so they effectively block them on their network edge.

I've been through some stats across multiple games and can see it's only impacting League and looks to be one of the two carriers we send traffic for Verizon to in Chicago. It might be trial and error on our part to see which of these two it is and making sweeping route policy changes late on a Sunday evening is not the best idea. We'll do some more digging and make some path adjustments tomorrow before peak. If it runs fine through peak, we've likely found the culprit. If it gets worse than we know to revert and go the other way.

Comment

EDIT 3: Update 25/1: Routing changes have proven effective and Verizon performance has looked stable for the past couple of nights now. If you are still experiencing any issues please log a player support ticket so they can get the right log data needed to triage this properly. If you're not a Verizon user, this is not the problem impacting you. Please log a player support ticket. There's kind of a recurring theme here. Logging player support tickets will help us help you when it comes to chronic network conditions, if it is something within our power to fix or work around. We also have a resource at www.lagreport.com that you can use to see if other people on your ISP have similar performance problems during different times of the day in different locations.

EDIT 2: Changes were made to routing this mo...

Read more

13 Jan

Comment

Originally posted by maverickk44

can you guys help the person out? u/EvrMoar u/RiotKorensky

I see it. I can’t say anything about what the outcome will be yet. I am having conversations with the right folks internally to see what we can do. I can’t promise, announce or commit to anything but I can tell you that I’ve seen this and will advocate for a solution.


04 Jan

Comment

Originally posted by kokkelzz

Hey man. My issue has returned. Exactly the same problem like last time. Tracert results:

https://ibb.co/wBJVKWZ

ISP: Elisa

Location: Finland

Hello - can you take a look now? Thanks


11 Dec

Comment

Originally posted by fellowcheapgamer

Hey, i live in singapore itself. Singapore 1 gives me less than 10 ping and singapore 2 gives around 15-ish but singapore 2 is much more stable and consistent than Singapore 1.

This doesn't help unless you mention which ISP you're using.

Comment

Originally posted by muthgh

The client often selects the worse route, where I live, my two lowest options were p1 path ~60ms, and then f1, 67ms, p2 path has always been 78ms, now that the selection is up to the client when I select paris only, it literally cost me so many matches, by connecting me through p2 on 78 (and often 2 to 10% packet loss) ping instead of p1 with 60, I don't understand, why not just let the user select a path in another place in settings or something!

Which ISP in France? This doesn't really make a lot of sense as latency is the key metric on deciding which network path the client will use.


10 Dec

Comment

Originally posted by aAnonymX06

Isp: Telekom Unifi City: Perai, Penang

Ok - unfortunately they don't seem like a huge data source for us so you can either DM me your IP address ( google "what is my ip address") with the last digit replaced with XXX or you can raise a player support ticket.

Comment

The servers have multiple network options that get tested during match making. These spikes might be indicating an intermittent problem the test window misses. They are the same servers as they’ve always been and in the same locations - the client just tries to find the best path to them. Which ISP are you using and which city are you playing from? I’ll get the team to take a look.


05 Nov

Comment

Originally posted by QuiteLife

Melbourne, Telstra

Tracing route to 43.229.65.1 over a maximum of 30 hops

  • 1 1 ms 2 ms 1 ms mymodem.modem [192.168.0.1]
  • 2 6 ms 6 ms 6 ms 172.18.211.15
  • 3 5 ms 6 ms 5 ms 172.18.67.141
  • 4 5 ms 5 ms 6 ms bundle-ether4.win-edge902.melbourne.telstra.net [203.50.76.8]
  • 5 7 ms 5 ms 7 ms bundle-ether12.win-core10.melbourne.telstra.net [203.50.11.111]
  • 6 236 ms 149 ms 18 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
  • 7 18 ms 18 ms 18 ms bundle-ether1.ken-edge903.sydney.telstra.net [203.50.11.173]
  • 8 18 ms 18 ms 18 ms bundle-ether2.chw-edge903.sydney.telstra.net [203.50.11.175]
  • 9 18 ms 17 ms 18 ms rio3430665.lnk.telstra.net [203.54.189.30]

Tracing route to 43.229.65.1 over a maximum of 30 hops

  • 1 9 ms 3 ms 1 ms mymodem.modem [192.168.0.1]
  • ...
Read more

Hop 3 and 4. Sorry but this is inside Telstra.


01 Oct

Comment

Originally posted by kokkelzz

Oh, ok. That explains a lot. Thanks a bunch my friend :) Have a good weekend.

This should be fixed up as of about 6-7 hours ago.

Comment

Originally posted by RiotKorensky

Thanks. They're sending this to RETN in Warsaw towards us. I'll see what we can do.

I spoke with some engineers at RETN and they've got an equipment failure between Stockholm and Helsinki causing some traffic to be routed on another path. They're going to see what they can do for this specific case while they are waiting on replacement parts for the larger issue. I'm also reaching out to Elisa to see if they can carry this over to Stockholm on their own capacity as we connect there with their parent company and we send the traffic back to them on this path which is why you're seeing such a high ping value at the moment.

Comment

Originally posted by kokkelzz

Hey. Still cant dm you "User doesn't accept direct messages. Try sending a chat request instead."

Cant open chat either since the account is new. I'll just post the info here then.

ISP: Elisa

Location: Finland

Traceroute results https://ibb.co/Jqwm0D3

Thanks. They're sending this to RETN in Warsaw towards us. I'll see what we can do.


30 Sep

Comment

Originally posted by Kam192

If you want more detailed answers or troubleshooting feel free to reach out to me. I can do some cmd pings or tracerts or give you other details if you want. This is a common experience for me in valorant specifically it seems. Years of CS and other FPS- none of which have had as many issues like this.

Thanks - I'll just take a poke around the stats and make sure we're not missing something that we can fix.


29 Sep

Comment

Which region are you in and what server location were you playing on? Thanks

Comment

Originally posted by kokkelzz

Your dm's are closed. I have the exact same issue as OP.

Messages are open - chat requests are not for accounts <30 days age. Try to message me if you're on a new account or post the data here without your IP address.

Comment

If it’s still this way please DM me your ISP, location and IP address (Google what is my ip) along with a traceroute (tracert 162.249.72.1 from the command prompt). Thanks.


24 Sep

Comment

Originally posted by RiotKorensky

Can’t help you if you don’t let me know which ISP and location.

We did some digging and think we have corrected a problem that would have been kicking in towards Optus mainly around peak time. I need to stress if you're having issues like this, player support tickets help and if you're not getting satisfaction there, sending me a ticket number will help me chase it up from our side. Monitoring the entire Internet is not an exact science and while work on systems to get better at it constantly, having the support queues used to grab our attention to specific issues can help shine a light on things we are missing.