Valorant

Valorant Dev Tracker




31 Aug

Comment

Originally posted by tqstin

Yeah I live in sydney and before it was removed I average around 5 ping, now its around 30 which doesnt sound bad but from 5 to 30 is huge and its very annoying

See above. Traceroute please.

Comment

Originally posted by rpkarma

Yeah it was also on Sydney 2 — and yeah that makes sense. I’m no network engineer, just a software one haha, I’m still convinced what you people do is black magic.

So, consistently, at around 4pm onward to about 10pm, my average ping begins to rather wildly fluctuate.

When the two “servers” (I saw in your comments they’re actually the same server with different networks?) existed, Sydney 1 appeared to have better routing, and was 5-10ms lower on average. But once those near peak times hit, the ping on either server would fluctuate wildly, up to 80-100ms for seconds, sometimes tens of seconds. This is consistent too, basically every evening.

The reported initial ping even ignoring those fluctuations also increased by 5-10ms at those peak time’s too, for what it’s worth.

I play a number of other online games which don’t (appear to!) experience this. Of course it’s possible that they do, and it’s masked somehow, but this phenomenon is so common that ...

Read more

I live in Australia so I'm pretty familiar with the Internet landscape here. Both the networks for Sydney-1 and Sydney-2 don't have a presence in Brisbane. Can you DM me your IP address and I'll make sure our return path is optimized but I suspect the congestion point will either be CVC related or congestion between Brisbane and Sydney which is unlikely given that Vocus own their own transmission there.

Comment

Originally posted by rpkarma

Mate NBN (Brisbane 4059)

``` Tracing route to 43.229.65.1 over a maximum of 30 hops

1 1 ms <1 ms <1 ms RT-AX86U-ED58 [192.168.50.1] 2 12 ms 14 ms 11 ms lo40.lns03.brisngn.qld.vocus.network [203.134.103.92] 3 11 ms 14 ms 16 ms ae2-14.per01.brisngn.qld.vocus.network [203.134.98.130] 4 15 ms 12 ms 25 ms ae6.per03.brisngn.qld.vocus.network [203.134.12.160] 5 12 ms 13 ms 17 ms be106-99.bdr01.bne08.qld.vocus.network [114.31.195.82] 6 30 ms 29 ms 29 ms be202.lsr01.bris.qld.vocus.network [103.1.77.192] 7 29 ms 30 ms 29 ms be801.lsr01.brdg.nsw.vocus.network [103.1.76.137] 8 29 ms 30 ms 34 ms be221.cor02.syd04.nsw.vocus.network [103.1.77.9] 9 29 ms 29 ms 34 ms be100.bdr04.syd03.nsw.vocus.network [114.31.192.45] 10 29 ms 29 ms 28 ms 218.100.53.59 11 * * * Request timed out. 12 * * * Request timed out. 13 * ...

Read more

If you're running this on an idle line, then I'd expect more consistency on hop 3-5. Hop 6 is where this enters their core network so runs the full roundtrip of 28ms. You should be seeing <35ms in-game on this.

Comment

Originally posted by rpkarma

I’ll do that in a second. Question for you, the biggest problem is the congestion at (near) peak times forcing higher and far more unstable pings. Can anything even be done about that (short of horizontal scaling with more servers) — as in, I don’t experience it anywhere near as badly with other online games, which leads me to believe it’s partially on your servers end, but that’s an educated guess on my end obviously.

Can you give any details on the congestion? Was it also on Sydney-2? These are the same servers in the same location with some differences in routing. There is no network congestion anywhere on the network however you are going to be at the mercy of some annoying equal-cost multi-pathing that some of the providers are using to get between states on paths that are very very different in length.

Comment

Originally posted by Ponzu_Lord

hey! i play from NA to play with my friends on OCE and i used to play on sydney too because 150 ping was much more bareable then 250 on sydney 1, if the servers are in the same location why are the ping differences so drastic?

i use AT&T Fiber with 1000 up and down

I'd suggest using a VPN for this. It's a use case we are not optimizing for at the moment sorry. If you post a traceroute to 43.229.65.1 I'll see if we have any potentially easy wins.

Comment

Any of you who are seeing poorer performance now - please reply with your ISP, location and a traceroute to 43.229.65.1. Thanks.

September 1 edit: We're aware of the Telstra WA ping increases and are talking with them about what can be done. There are multiple paths across the country and unfortunately they're choosing to use one of the longest ones right now. The Bigpond game optimizer add-on for your service will also not address this issue in case you were thinking of trying it. If you need a short term fix, I can suggest trying some of the VPN providers that have presence in both Perth and Sydney as they actively try to shortcut some of these problems.


30 Aug

Comment

Originally posted by Android_Addict

here you(also my home network is configured in a double NAT environment ):

Tracing route to 43.229.65.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RT-AX55-1B90 [192.168.50.1]

2 <1 ms <1 ms <1 ms 192.168.1.1

3 12 ms 12 ms 12 ms 172.18.216.104

4 13 ms 14 ms 12 ms 172.18.73.173

5 12 ms 14 ms 13 ms bundle-ether4.pie-edge902.perth.telstra.net [203.50.112.52]

6 16 ms 15 ms 15 ms bundle-ether10.pie-core10.perth.telstra.net [203.50.6.188]

7 42 ms 41 ms 41 ms bundle-ether3.way-core10.adelaide.telstra.net [203.50.6.234]

8 55 ms 55 ms 53 ms bundle-ether16.exi-core10.melbourne.telstra.net [203.50.6.231]

9 67 ms 67 ms 67 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]

10 66 ms 66 ms 66 ms bundle-ether1.chw-edge903.sydney.telstra.net [203.50.11.177]

11 66 ms 66 ms 66 ms rio3...

Read more

Yeah this is not the… optimal path across the country. See how it’s detouring via Melbourne instead of just cutting straight across from Adelaide? I will talk to our contacts at Telstra to see if we can do anything about their traffic engineering here to try and improve this. A VPN may help this since most VPN providers would likely have a node in Perth and use a better transport path across to Sydney. Just to warn you, this discussion with Telstra will take time and they may flat out refuse our request for “policy” reasons.

Comment

Originally posted by TheZedMan610

I play on west coast in Aus, Syd 2 is consistently 5~10 ping lower than Syd 1.

I don’t think that hits the bar for horrible — which ISP are you with? The issue here is there are multiple different transmission paths across the country and some are shorter in length so they’re faster. Depending on the provider we may be able to do something to get that performance on par.

Comment

Originally posted by Android_Addict

Telstra ADSL2+ from Western Australia average speeds of 15mbps down and 0.5mbps up

Can you run a traceroute (tracert if you used windows command prompt) to 43.229.65.1 and paste it here? You'll be hitting Perth then over to Sydney so that's a minimum 45ms or so we wont be able to do anything about but 50ms for your ADSL 2+ connection seems high. It's possible you're on an interleaved profile or similar if you're at the end of a copper loop and it's what is needed to make your service stable but I'll be able to comment more once I see a trace.

Comment

Originally posted by 4dzilla

I’m on Vodafone and playing from NZ.

I’d never had ping issues before until Sydney 2 disappeared, then it was instantly 120-180 ping for 95% of the games.

In saying that I didn’t have any issues yesterday (a small update was done, possibly just coincidence?), ping was usual 50-60, so hopefully whatever was going on is sorted!

I do remember an issue the first evening Sydney 2 was shutdown that was resolved the following morning. It was causing some folks to be placed on Tokyo or Singapore during peak time.

Comment

Originally posted by HanimeAddict768

Is sydney 2 permanently removed? I personally get perfectly fine ping, but it would be good to know for others. I have a mate who lives in NZ and he usually gets 70ping on syd 2 and 30 on syd 1 but now its just random (could be confirmation bias though im just passing on info)

They’re the exact same servers in the same location with different network configurations. Sydney 1 should provide the same responses consistently. If it isn’t then we can take a look at your ISP and how they’re routing to us.

Comment

Originally posted by Cosmohnaut

It's been MIA since last week, no certainty on the reasoning.

Pretty frustrating as more often then not, I'll get put in games with 4x the ping, which wasn't as frequent when Sydney 2 was online.

Hope riot let's us know so we can understand if or when it's coming back.

You should in theory have much less chance of a game with 4x ping as the players you can match with wont be split across both Sydney locations, giving a greater pool of players with Sydney 1 as their best performing location.

Comment

This is way outside of our targets - which ISP are you on and where are you playing from?

Comment

Originally posted by 4dzilla

Yeh it disappeared about a week or so ago and then most games I played on Sydney 1 had 150-180 ping which is not even worth playing on.

It did a quick update a day or so ago and my ping has been usual 50 since then, not sure what’s going on but appreciate the normal ping!

Couldn’t find anything online about it either

Which ISP are you using and where are you playing from?

Comment

Originally posted by Frozoken

don't think there's any statement on it yet. could be to increase players on one server for the end of the season when less people are playing. could be down for good. could just be having maintenance done in it as valorant sydney has had a shit ton of problems recently. hopefully it's temporary as sydney 1 is horrible and I'm guessing it is due to the lack of any statement from riot.

Please provide details on what you mean by horrible.


27 Aug