RiotKorensky

RiotKorensky



03 Nov

Comment

Originally posted by blueberriesenjoyer

ty, a bit of a tangent, but usually my European friends have a better ping to South Africa than me, of course they usually have better internet in general, but is that in part due to the network topology thing, that even our connection to SA runs through a European POP to get to SA, with the same happening to Europeans too but just because for us the point is in the opposite direction of SA, we get higher pings, or is it just our poorer infra-structure?
Also any plans for a north African Server XD?

Probably no plans for North Africa. We only just got Capetown done this year.

The reason they have a better ping from Europe is most of South Africa’s connectivity runs via submarine cable and will land direct into a hub like Marseille or London. For North Africa you’re probably going via Europe to reach sub Saharan Africa.

Comment

Originally posted by RiotKorensky

This should improve sometime in the next week. We are aiming to try and get Paris, London and Madrid back down however because of our network topology, it might be a few ms higher than before as we run Cairo into Milan first for redundancy reasons.

EU from Egypt should be a lot better now

Comment

Originally posted by blueberriesenjoyer

I'm from Egypt, getting 58 on Dubai,68 Frankfurt, 114 Bahrain, 164 Paris, 165 London, 172 Madrid, & the rest are higher, before the introduction of Dubai servers, Paris/london/frank were within a few ms of each other, between 55 to 75, followed by Madrid/Warsaw/Stockholm from 80:90, & so on.

"if you’re located between two of our network points of presence then unfortunately one of them is going to be your entry point" if I'm not misunderstanding, this would mean that previously Paris or somewhere close to Paris was the POP being used as entry mostly for me (since it used to have the lowest ping), but now you've a new one closer to UAE through which I'm connecting to others? but also if so why is the Frankfurt server's ping still the same? right now the game is basically unplayable on most servers for North Africans, traceroute:

1 <1 ms <1 ms <1 ms [192.168.1.1]

2 5 ms 6 ms 5 ms 10.45.5.2

3 5 ms 5 ms 5 ms 10.36.22....

Read more

This should improve sometime in the next week. We are aiming to try and get Paris, London and Madrid back down however because of our network topology, it might be a few ms higher than before as we run Cairo into Milan first for redundancy reasons.


02 Nov

Comment

Originally posted by KrCharter

I live in a Levant country and Dubai/Bahrain servers are at 48-50ms so mission accomplished I guess. However, 98% of my playtime was spent on London due to most my friends being European and now I'm afraid I won't be able to anymore. I'll try the VPN thing later today but I doubt any free services are good enough to provide a stable enough connection and idk about paying for a VPN provider just to play on a server I've already been playing on for years.

50ms seems high. For reference - we go from Cairo to Dubai in 45ms, via Riyadh. If you can paste a traceroute to 162.249.72.1 or DM it to me I will see if we can further optimize. Unfortunately a lot of these issues only become visible to us once infrastructure has gone live as it is difficult to predict how every ISP will route towards us. We are still going through a lot of the data we have gathered in the last day and working out what our next moves are. It might take us a few weeks to finish tuning the region.

Comment

Originally posted by DueRepresentative912

verizon in both

Mobile? Please provide a traceroute to 192.207.0.1 if you can. It would also be worth complaining to Verizon about this so they reach out to us. They’re not super responsive.

Comment

Which ISP are you using in California?

Comment

Which ISP please and location? Can you post a traceroute to 162.249.72.1? Thanks

Comment

Where are you located in the Middle East? If you use a VPN to Central or Western Europe this will give you a better result when trying to play on servers that are further away.

Routing is optimized to get players the best result to the closest server location with the aim of trying to get as many people under our 35ms and 50ms targets as possible. VPNs are a way to override or go around that. We will work to try and provide good access to all of our locations but if you’re located between two of our network points of presence then unfortunately one of them is going to be your entry point.


24 Aug

Comment

Originally posted by radiatione

Are you sure you are not playing on the Tokyo server from the European client? Because that one is mainly a server for east Russia. You'll need to play on the Japanese client to have more japanese people.

This is correct. There are some “Europe” servers in Tokyo for eastern Russia. If you have moved there are details here on moving your account: https://support-valorant.riotgames.com/hc/en-us/articles/4413502362259-Account-Transfer-FAQ


18 Aug

Comment

Originally posted by tm458

Doubt you remember our conversation from more than a year ago but thanks for the help u/RiotKorensky

It’s a team effort for these type of projects and like I said originally, I’m not going to be the one to announce anything when it is on the roadmap because it’s not my news to share. Just make sure to tell all your friends to give it a shot now that we are (soon to be) local and pings are where they should be to experience the game the way it was designed.


12 Jun

Comment

I still lurk looking for fixable infrastructure issues…


30 Apr

Comment

Originally posted by Reunision

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.


21 Apr

Comment

Originally posted by SpiderTechnitian

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.

Comment

Originally posted by ConsiderationNo1550

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.

Comment

Originally posted by Stryker3414

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?

Comment

Originally posted by ConsiderationNo1550

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?

Comment

Originally posted by G33ke3

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?


07 Apr

Comment

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...

Read more

16 Mar

Comment

Originally posted by mhoja1234

In 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.


13 Mar

Comment

Originally posted by Mysterious_Drop_92

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.