devtrackers.gg → Valorant

[2021] Riot removed the only well-functioning Australian server


Original Post — Direct link

I hope this gets some visibility, first OPL is gone and now riot further slaps the face of Australian players.

Before, Australia had Sydney 1 and Sydney 2 servers. Now Sydney 2 is gone, and the game has become unplayable for anyone living outside the east coasy. Sydney 2 had somewhere between 55-65 ping consistently for anyone on the west side of Aus, and now I can't get below 80, with many people regularly geting 90+. Noone is talking about this, and it's a pathetic slap in the face to Aus players. Even people who live near the server hub are getting worse ping, and not to mention the fact that Sydney 1 is generally more unstable and drops out regularly.

Awful decision.

External link →
about 3 years ago - /u/RiotKorensky - Direct link

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.

about 3 years ago - /u/RiotKorensky - Direct link

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.

about 3 years ago - /u/RiotKorensky - Direct link

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 * * * Request timed out. ```

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.

about 3 years ago - /u/RiotKorensky - Direct link

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 it’s remarked upon by my non technical Valorant friends here in Aus too.

Welcome to our shitty internet haha

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.

about 3 years ago - /u/RiotKorensky - Direct link

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.

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by Equivalent_Ad505

so im not the only one? the ping flunctuation is also insanely fast, when i watch my netword rtt it fluctuates atleast 2-3 times a second between 65-115 ping over and over again.

Any chance you can capture a video of this or what the network stats are like in the practice range? Which ISP are you using? Can you capture a traceroute as well (instructions somewhere in the thread). This data will help us get the places that were not at parity performance wise with Sydney-1. We have a good idea what the problems are but need to reach out to our contacts in the ISP community for assistance in correcting it.

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by Frozoken

iinet(NBN), perth

2 1 ms 1 ms 1 ms 203-219-198-201.tpgi.com.au [203.219.198.201]

3 49 ms 48 ms 49 ms 203.29.134-193.tpgi.com.au [203.29.134.193]

4 50 ms 54 ms 54 ms syd-tpg-wat-crt2-ge-3-1.static.tpgi.com.au [203.26.22.125]

5 49 ms 49 ms 49 ms 203.29.134-18.tpgi.com.au [203.29.134.18]

6 50 ms 50 ms 50 ms 203-219-106-254.tpgi.com.au [203.219.106.254]

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

This looks pretty good - you should be on the same sort of performance that you had before...

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by rpkarma

Okay me again, so my in-game ping right now is 57ms and my traceroute shows this:

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

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

Hop 3 shows inconsistent response times (and 4) so congestion likely starting before that. Can you download something like ping plotter or similar and run a longer trace over time during peak to try and get a better sampling window? I suspect it'll give a stronger indicator. These issues would also have been present on Sydney-2 since they're close to the access end of the route so we're dealing with a lot of cognitive bias :(

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by Daisy_1

Aussie Broadband - Canberra

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

2 88 ms 87 ms 84 ms 100.96.128.1

3 * * * Request timed out.

4 75 ms 79 ms 87 ms 180.150.0.235

5 87 ms 73 ms 74 ms be10-3999.core1.nextdc-s1.syd.aussiebb.net [180.150.2.96]

6 88 ms 88 ms 79 ms be1.core2.nextdc-s1.syd.aussiebb.net [180.150.1.117]

7 87 ms 77 ms 70 ms as6507.syd.edgeix.net.au [202.77.88.10]

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.Trace complete.

88ms to hop 2 - you should really call your ISP and talk to them about this..

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by tqstin

yeah playing on anything higher thab like 30 ping is aids for le

Still can't help you if you don't run a traceroute and post the results.

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by meme_poacher

Anything on the bahrain server, or adding african servers?

What's your issue with Bahrain sorry? It should be up and working as normal to my knowledge.

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by Equivalent_Ad505

I’ll try and do it tonight. What settings do you want me to record besides ping?

If you can get these stats (need to enable them in the menu) from a practice/custom game on Sydney-1 it'll help

https://imgur.com/a/OErOSKM

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by RiotKorensky

If you can get these stats (need to enable them in the menu) from a practice/custom game on Sydney-1 it'll help

https://imgur.com/a/OErOSKM

Disclaimer: i do not work day to day on the Valorant client side of things and have very little knowledge of some of the other trace/debug/log options that may exist in it. I will make some time to talk with folks on that team to see if we have a better way of extracting this data also for specific cases.

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by meme_poacher

The ping used to be 70ms to Kenya now its 240ms, it's literally the only server the whole of africa can play on

I just got word today that there is an outage on the direct path between Kenya and Bahrain that started around August 23. Our partner in the region is waiting on repair details but it sounds like a submarine cable fault so may take a few weeks to repair.

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by Petaurus_australis

Hey, do you happen to know if the Sydney 1 servers are having problems today / tonight? Had three matches where multiple people were getting ping spikes and packetloss spikes to a decent severity, but tracert's, discord, ping plotter, etc all coming back clean. I'm with iinet and it seems the tracerts time out at the 8th hop for me.

No server issues. If you can screenshot the ingame stats and check if it’s network related (ploss/jitter) that helps. We are working through issues with some ISPs that like to congest their intercapital links at peak times but if you post your ISP and city it helps us to validate it against our own telemetry from the game clients and log faults with our commercial contacts so that we can get this resolved.

about 3 years ago - /u/RiotKorensky - Direct link

Originally posted by KofskiMayte

Ever since the server merge my ping is consistently below 10ms but my packet loss is pretty much 50-50 depending on the match, somewhere between 10-20% or flat 0%. Not sure why this is happening, doesnt occur in other online services/games.

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

about 3 years ago - /u/RiotKorensky - Direct link

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.

about 3 years ago - /u/RiotKorensky - Direct link

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]
  • 2 6 ms 8 ms 19 ms 172.18.211.15
  • 3 54 ms 81 ms 7 ms 172.18.67.141
  • 4 212 ms 47 ms 5 ms bundle-ether4.win-edge902.melbourne.telstra.net [203.50.76.8]
  • 5 6 ms 7 ms 7 ms bundle-ether12.win-core10.melbourne.telstra.net [203.50.11.111]
  • 6 17 ms 18 ms 20 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
  • 7 20 ms 19 ms 17 ms bundle-ether1.ken-edge903.sydney.telstra.net [203.50.11.173]
  • 8 85 ms 44 ms 22 ms bundle-ether2.chw-edge903.sydney.telstra.net [203.50.11.175]
  • 9 20 ms 21 ms 20 ms rio3430665.lnk.telstra.net [203.54.189.30]

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

over 2 years ago - /u/RiotKorensky - Direct link

Originally posted by Weak_Branch720

1 31 ms 21 ms 29 ms h268a [192.168.20.1]

2 159 ms 282 ms 447 ms 69.1.233.220.static.exetel.com.au [220.233.1.69]

3 150 ms 88 ms 27 ms 10.1.81.133 [10.1.81.133]

4 292 ms 460 ms 180 ms tengige0-0-0-35.bdr01-ipt-4millros-per.au.superloop.net.co [27.122.123.126]

5 200 ms 193 ms 258 ms bundle-ether34-126.bdr02-ipt-4edenpar-syd.au.superloop.net.co [103.200.13.152]

6 163 ms 75 ms 76 ms as6507.nsw.ix.asn.au [218.100.53.59]

7 * *

You have an ISP problem. Hop 2 is huge.

over 2 years ago - /u/RiotKorensky - Direct link

Originally posted by MicolasFoley

hey, i'm not from Australia, but i thought i'd give this a try anyway

Michigan - wideopenwest

I've linked a few pingplotter traces, and for example on the 192.207.0.1, it's supposed to route me to the 'best' riot server in NA, but it's routing me to Georgia when it should be Chicago as seen in the other two images. When i try to get to Dallas or Chicago it first sends me to Georgia. My ping to VALORANT chicago was normally 15-20ms, now it's sitting at a steady 60-70ms

This only started happening around april 16th.

https://i.imgur.com/XK5Jror.png

https://i.imgur.com/6aelwUe.png

https://i.imgur.com/DXLpiAk.png

You need to reach out to WOW. I will reach out to their peering team and see if they can correct it on their side but it helps to have customer complaints.

over 2 years ago - /u/RiotKorensky - Direct link

Originally posted by NexYT

Did this get addressed yet? WA Telstra user curious. Also can any Perth VALORANT players recommend a VPN for Perth-Syd?

We're probably about a week away from getting this in-place for non-Telstra users. Telstra are installing some additional infrastructure before they can connect to us in WA at the same location.

over 2 years ago - /u/RiotKorensky - Direct link

Originally posted by Weak_Branch720

Thanks, is there any recommendations for better wifi in Perth? I really cannot play valorant with the ping I have currently, just played a comp with over 500 ping.

Look into Pentanet. They are actively pumping their game performance too.

over 2 years ago - /u/RiotKorensky - Direct link

Originally posted by No_Light_6013

When I have stable ping

Tracing route to 43.229.65.1 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 6 ms 6 ms 10.15.0.1 3 * * * Request timed out. 4 12 ms 11 ms 13 ms 203.30.1.145 5 7 ms 7 ms 7 ms ip-65.208.103.123.VOCUS.net.au [123.103.208.65] 6 27 ms 28 ms 28 ms be200.lsr01.adel.sa.vocus.network [103.1.77.128] 7 28 ms 28 ms 28 ms be801.lsr01.melb.vic.vocus.network [103.1.76.154] 8 30 ms 30 ms 30 ms be802.lsr01.brdg.nsw.vocus.network [103.1.76.142] 9 28 ms 27 ms 27 ms be221.cor02.syd04.nsw.vocus.network [103.1.77.9] 10 30 ms 29 ms 29 ms be100.bdr04.syd03.nsw.vocus.network [114.31.192.45] 11 30 ms 30 ms 29 ms as6507.nsw.ix.asn.au [218.100.53.59] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out.

Im new to this so im not quite sure why it changes

You need to report this to your ISP. It looks like they are balancing load but might be a mistake. Send them both traces please. I will be meeting with engineers from there late next week on other business and will also ask about this routing then.

over 1 year ago - /u/RiotKorensky - Direct link

Originally posted by MicolasFoley

Hey, sorry to bother you again - my ISP (WOW) is having another issue with Riot servers in Chicago/Dallas again. This has been ongoing for about 2 months now with no resolution from WOW.

I'm not sure what they changed, but this issue was resolved after i contacted you the last time.

https://i.imgur.com/HACygTG.png

I would churn from them if you can. We used to have direct peering with them but they have been retracting their footprint the last couple of years. I’m not sure what their strategy is but they don’t seem to value quality of experience. I’ll reach out to them again but I’m not hopeful. What ping are you expecting to see here?

over 1 year ago - /u/RiotKorensky - Direct link

Originally posted by MicolasFoley

Hey, sorry to bother you again - my ISP (WOW) is having another issue with Riot servers in Chicago/Dallas again. This has been ongoing for about 2 months now with no resolution from WOW.

I'm not sure what they changed, but this issue was resolved after i contacted you the last time.

https://i.imgur.com/HACygTG.png

Which location are you playing from as well?

We will need a traceroute to 192.207.0.1 to diagnose Valorant routing in NA.

← More from Valorant





Recent Valorant Posts

Everything you need to know about the new map rotation system in 2025.

2 days ago - VALORANT

stay crafty

3 days ago - VALORANT

The changes to Sunset's lighting were a very positive point for the game's design

3 days ago - /u/penguinVALORANT

VALORANT 9.10 Bug Megathread

4 days ago - /u/penguinVALORANT
Get Discord notifications