Again Massive Riot Direct ISSUE AS6507
All those who have experienced a sharp increase in ping at some point, please read and support if not indifferent https://www.reddit.com/r/riotgames/comments/1ig3vaj/again_massive_riot_direct_issue_as6507/
Reddit
From the riotgames community on Reddit: Again Massive Riot Direct I...
Explore this post and more from the riotgames community
24 Replies
@Riot Schmick
there's nothing i can do about this. i dont work in our networking area. those that do keep an eye out for these things
Just how to contact them, it's a problem that hasn't been solved for years and is getting worse (presumably) from the Riot Direct expansion
Contact riot support?
there is no way to directly contact anyone on Riot staff. if there were, we would be getting a constant influx of requests and would never be able to sort out the relevant ones, much less have time to do our jobs
I already sent everything in, but the employee said he didn't know if anyone would be doing it
and that's correct. all they can do is route it to the right folks. it's up to that owning team to decide if anything can be done and if so, if the effort involved can be prioritized over other efforts that are being worked on
but it's not even guaranteed that we have the power to fix it. a lot of the times we rely on ISPs or other providers to make changes on their end and they aren't always willing or able to
I understand how it works, but it seems that no one is interested in this problem and does not advertise it in any way, all the information I found is only how people complain en masse about the increase in ping from different regions 1-3 years ago specifically to Valorant, they just say, the problem of the provider of something else and all forget, to contact in any way can not, to get through too, support will just say ask to configure your ISPs Riot Direct, although just at the backbone provider RETN was configured Riot Direct and this is what comes out
Anyway, thanks for the reply
wait for the arrival of the holy Kenji-san :Prayge:
just because no one from the team is responding directly to you or on the posts doesn't mean no one is interested. we don't necessarily advertise our work for most parts of the company. i'm not promising that we are currently working on this. i'm just saying that something not being advertised doesn't mean anything.
but either way, there's nothing i can do to help here. if it's been reported then our team has likely been made aware. in addition, if it's been complained about for years, then they probably already knew, as we have people that monitor socials for sentiment and issues. i can't speak personally to what has been done/tried on our end or why it hasn't improved, except to say that it's not because no one cares. it's more likely because our hands our tied in some way.
Thanks for the reply, I'm just hoping someone from Riot NetOps has a more detailed answer, so I'm writing where I can
Hey @Tatara I am aware of the problem and this is not a very easy and quick fix, usually we take individual ISPs and optimize them, but we cant really tell them or force them to use transit of our choice, as unfortunately its out of our scope. I did a few tweaks to RETN events during 2024 major one was cutting advertisements in RETN PL towards APAC countries via BGP communities, but that wont stop all ISPs in CIS using different path/transit that results in preferring path via Poland. I can assure you we are reacting to this problem as we have plenty of metrics and ahead warnings when it happens. There are few more things I want to try this year as well that might improve or resolve it.
for now, you can create topic here which I actively sweep few times a week when you know about certain ISP that have a routing issue towards Stockholm and we can check it out if they are willing to cooperate with us and fix it
had a sweep through our cases and as example: we fixed one in December 2024, ASN 50498 were pathing via RETN PL, they were learning our prefixes as well in RETN St.Petersburg and instead of sending it via Stockholm it was flying via Poland. You can imagine latency nearly tripled for them. They were willing to cooperate with us and we resolved it within a day, some graphs for your vis.
Id say these shows up about every 3-4months, we react to it quickly enough
The problem is that most local providers and providers in Kazakhstan and Russia just connect to RETN. In Kazakhstan it is TTC and TNS, they provide Retn services to us and in Kazakhstan itself. I can only provide a few, in my country and others. AS41798, AS42837, AS5617, AS41750, AS35168
Retn makes Warsaw a base for the whole CIS and Russia
And the problem is that a lot of CIS providers have started connecting to RETN.
Specifically in my country, the routes have not changed for several years
I understand the frustration of this and dont want to brush this off, but you must understand that this is between those ISPs and RETN as a two individual companies, we cant be really telling them how to run their network. If I own an ISP and buy Tier 1 transit to connect me with a certain prefix I need to speak to my Tier 1 and tell them my issue. I pay money to Tier 1 they need to fix it. This is my logic to the problem. ISP can also utilize bgp communities towards RETN, I am sure you know how these works given you seem to understand routing.
if the return traffic would be the problem you bet I can fix that part as its our network and we control it
nevertheless, we can at least reach out to the individuals and ask them to look at it, that is what we are doing as part of the process . ill also have a look at those ISPs you mentioned throughout the week
I don't know much about routes, I've only started to learn about it this week. Thank you very much for your reply, that's the most you've done so far.
no probs man, feel free to ask or make topics in here when you have questions people around are very nice and knowledgeable
Have you tried working with Retn Russia AS57304 and RETN Kazakhstan 44877? Maybe they have more control over routing choices in CIS and can cooperate better with ISPs
:val_Heh:
UPD: AS8449 - it's a higher provider, for a few local ones. Including - AS42837. It uses a couple of transits including RETN.
@Tatara thanks Tatara, ill check them out when I get a chance. Meanwhile they should be talking to RETN themselves to get a reroute towards St.Petersburg or closer to Stockholm RETN
I tried to write to higher providers from Kazakhstan nobody answered me, I tried local providers, they said they can not do anything. Now I will try to write to AS8449