Is there a reason that I’m getting 20% packet loss in about a third of my games? It last the whole match and in those matches my teammates say they’re getting it too.
If you're on Optus - yes. We just found something on our interconnect with them and we'll have it fixed today, even if we turn it off for a while and your ping goes up slightly.
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.
I see. Riot Support told me VPNs are absolutely fine to use so I hope I'm good. Although it does result in shots being registered late
No issues I am aware of with using VPNs. If they work for you then use one. They do not improve things for everyone and they do add a large amount of overhead so you will use more bandwidth per game while on one.
It is a VPN
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.
/u/RiotKorensky might be able to provide the IP for Texas.
Side note: this problem is more solveable than the commonly upvoted ranked circlejerk complaints we see here
Please send a trace to 192.207.0.1 (This IP is generally used for all of North America) and DM me your ISP name and IP address. Thanks.
u/RiotKorensky Could you possibly provide an IP address for the Sydney server so that I could run a cmd prompt ping test for a few minutes prior to starting up a comp game?
We don't unfortunately as there are layers of proxy equipment you need to traverse before your traffic goes to a game container. The best way to check your ping if you get variance at peak would be to jump into a practice range. I'm on Telstra in NSW and have pretty high reliability 24/7 on an NBN service. If you are seeing differing performance throughout the day, we have metrics from league of legends at www.lagreport.com that you can use to see if it's similar for your ISP and location. These are normalized to remove variance from things like local wireless issues and are a good indicator of your ISP performance to Riot.
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.
would this be for telstra users only or all perth users? thanks for taking your time to respond to so many people
Initially just Telstra so that we can prove the concept but the intention will be to capture as many players from WA as we can at this point. Every step of this will require the cooperation of ISPs since it'll be new interconnects and we're building in a location where they all have common presence to try and avoid any air gaps.
Does this mean there will be a server in Perth?
No there wont be a server in Perth. There will be network equipment to try and capture your traffic locally and send it over to our other equipment in Sydney on the shortest path we can find.
If you can get these stats (need to enable them in the menu) from a practice/custom game on Sydney-1 it'll help
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.
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
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.
It's not horrible per se, but when I'm trying to compete with the east coast players who average 25 ping, anything is better. I'm with Telstra, and I play in Perth, if that helps.
Telstra solution is in the works but is realistically probably going to take us a few weeks to get implemented (we will have some paperwork to sign once the details are ironed out, people will need to do some work on both sides, equipment will need to arrive in Perth from the COVID capital of Australia etc).
i just did tracert and i get 52 ping, and in game its 66 ping, is it visual glitch ? might be in stats not working properly
1 <1 ms <1 ms <1 ms 192.168.2.1
2 1 ms 1 ms <1 ms 192.168.1.1
3 38 ms 7 ms 5 ms Loopback1.bng01-sbb-1william-per.au.superloop.com [203.132.88.1]
4 6 ms 6 ms 6 ms bundle-ether13-100.bdr01-ipt-1william-per.au.superloop.net.co [27.122.123.71]
5 51 ms 52 ms 51 ms hundredgige0-0-1-3.bdr01-ipt-4millros-per.au.superloop.net.co [103.200.13.135]
6 52 ms 52 ms 52 ms hundredgige0-0-1-2-126.bdr01-ipt-4edenpar-syd.au.superloop.net.co [103.200.13.152]
7 52 ms 52 ms 52 ms as6507.sydney.megaport.com [103.26.69.85]
8 * * * Request timed out.
Superloop use Indigo Central (the submarine one) to get from Perth to Sydney and the network round-trip there is about 46.8ms for that segment.
The in-game ping will be adding the client render-time to the number so it's always going to be higher than the network number. I need to chat with some of the folks on the development side who are a little more in the weeds on the specifics here but the article here talks a bit about it: https://technology.riotgames.com/news/peeking-valorants-netcode -- a higher framerate will help bring this number down in-game but the network ping you see when you're running thos...
Read morei live in western Australia.... (sydney 2) i got 51 ping in game, and (sydney 1) 67 ping in game please explain how the servers are in the same location,then why such a huge ping difference.
i have fibre to premise 250 down 40 up.
what a piss weak response ....... ''If it isn’t then we can take a look at your ISP and how they’re routing to us''
there is only 1 way to route, 1 under sea cable from sydney to perth, on the valorant competitive reddit there is plenty of people complaining if its this wide spread how is it our ISP's
for a game was marketed as having no peakers advantage.... no ping advantage this is a joke. playing on 67 ping vs 0 to 40 ping players in eastern states its unplayable there is no hit reg
There are three major terrestrial routes from Perth to Sydney and one undersea cable. The submarine one is not the fastest. There are also many more than one ways to route packets over the Internet, even inside Australia.
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.
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..
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 :(
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...
devtrackers.gg