Hey I just wanna bump this - my friend with the same provider and same location said his ping is also like 15-20 higher.
Yes it is higher. The problem is you are in the middle between Chicago and Ashburn and routing appears to have changed. We will look at it next week and see if anything can be done to improve this. VPNs will override this routing if you can't wait.
my ping went from 50ms to 180ms after the update and hasnt gone back, i just need the ip address to reroute the connection from my isp
Which ISP are you using and which country
Thanks so much for the response. I just wanted to make sure it wasn't something on my end. Probably a dumb question... where would I actually set the VPN to?
Chicago. League servers for NA are in Chicago.
u/DelBringo is this related to the network changes you're rolling out as you mentioned here? if so, could you share more details about it? I'm curious, cause my ISP's routing (or Riot's?) can vary from game to game, causing me to have a stable 37ms ping in the worst case, and 26ms in the best.
Not related
EU East is based in Frankfurt, Germany. It'll still be a bit closer to be in NA servers.
I think the best way to test this would be to make a new account in EUNE and a new account in NA and see which is better ping.
Most of the ISPs in Alaska connect back to the US, not direct to Europe. You're probably best off on NA.
[deleted]
Does using a VPN to NA fix it? Try a trial one. If this does fix it, there is some sort of filtering between the server location and your ISP.
Hey I really don't know where to ask this, but has anyone else mentioned anything about having like 20-30 higher ping on NA since yesterday? I went from 30 to 55 ping and it's actually such a pain, everything else on my end seems fine so for whatever reason my connection to League is just strictly worse or something :(
Which isp and location?
I still lurk looking for fixable infrastructure issues…
Hello, I was wondering if there have been any updates or progress in resolving these issues since then? Will the target date be delayed at all or anything?? I've been waiting for the past 2 months to play League again, I really hope it will be resolved soon.
If you are a PLDT customer you should be asking them. May 19th is the latest date I have for repairs on the AAG system between HK and PH.
I am also on Ziply and still having the issue.
Ziply should be working now for anyone following along. If there are any other providers in Pacific NW that still have issues please let us know below. We're running extra checks in this region but want to be sure we don't miss anyone.
Might want to explain how to do that if you want the results
Those who knew sent them. I don't have a pre-written instructions for this to just paste and don't really want the liability of guiding folks around the CLI if they're unfamiliar but I understand what you mean.
Had the issue earlier at about 1:10 PST and am also on Ziply.
Can you please run a traceroute to 192.64.168.1 and paste output here or DM it to me?
I am also on Ziply and still having the issue.
Can you please run a traceroute to 192.64.168.1 and paste output here or DM it to me?
I question if this is fixed. At the time of posting (according to Reddit 12:48 PM PST), I had JUST been punished for not being able to connect to a game at 12:40. Not to say this is the Riot posters fault, they were probably told by QA/Production that the error had resolved. But I will not be playing ranked the rest of the day or maybe next few days if there isn't an update. Yes I had already submitted a ticket.
Also I don't BELIEVE my internet is AT&T. I use Ziply (Unless Ziply uses AT&T fiber cables and I'm unaware). So I don't think this was a ISP issue on my end.
Can you please run a traceroute to 192.64.168.1 and paste output here or DM it to me?
I can speak to the ping item. This was not just a decision made lightly. We had started building the Riot Direct network to try and deal with bad routing across the US already but it was clear we needed to find a more central location for the game servers to try and give everyone the best experience we could. There was a huge desire to not split the player population into east and west but to maintain a unified North America shard that had the best possible latency we could engineer to a single location. Chicago gave us the best compromise across Canada and the USA but was still not without its difficulties. Getting the interconnection setup and engineered to the major ISPs across NA, with the fairly constant change in ownership and engineering was challenging. You can get 45ms from LA on a good ISP to Chicago now. The averages before this when the servers were in Oregon were horrible. Our original goal was to get 80% of the players in NA under 80ms but we were able to move that to 80...
Read moreIn the meantime I have heard that some gaming vpns are having their ips blocked when connecting to sea servers (Exitlag and mudfish) was that intended? Because its the only way PLDT users like us to play at constant 20+ ping :(
Have them reach out to our team - [[email protected]](mailto:[email protected]) as we will need specific information to permit them due to all the malicious activity we've observed from anon VPNs and cloud based services.
idk if you guys knew about this bug, but during the day, whenever I play League, the ping would go to 80ms, then I would close the loading screen (after pick and bans) and the ping would go back to 29ms, but its only during the day, when I play 8pm onwards the ping would stay at 80ms. Basically, when the game loads (after pick and bans) just close the game and reconnect and the ping should be fixed.
This is caused by your ISP treating the route to HK over two paths out of the PH as equal cost when they have very different paths and latencies in reality. What you’re doing here is the right way to go about getting around it.
its still high, getting 80ms consistently
The servers for PH are still in HK. There are a few submarine cable cuts still impacting the direct path (AAG is the system I think) which should be resolved in early May. I’ll look into it again and see what we can carry for them on our own links but this looks like they might be balancing some traffic out via alternate paths that aren’t as short. The AAG cable segment between HK and PH has had 5 separate faults over the past 7-9 months which have been blowing the restoration time out.
this has been happening to me too ever since 13.3. riot support made me do port forwarding in my router settings just to fix it.
league is the only game to have lag issues for me as well.
This has nothing to do with 13.3 and probably nothing to do with your home router. If you don’t post your ISP and location then we can’t cross check your report vs the data we gather from all users of your ISP.
Can you post some details on your isp and location? This sounds like congestion in their network but we can take a look. We post ping data at www.lagreport.com as well