devtrackers.gg
I am experiencing 500-700 ping in game and in the practice mode. Att is my current service provider, before patch .49 I had around 50 stable ping. Is anyone else having these problems?
External link →I am experiencing 500-700 ping in game and in the practice mode. Att is my current service provider, before patch .49 I had around 50 stable ping. Is anyone else having these problems?
External link →That's nasty. Can you DM me your IP address if you don't mind? (google what is my IP address or hit www.whatismyip.com ) -- I don't have flair on this sub setup yet so another Rioter will vouch for me shortly.
I vouch for Korensky, this guy knows internet
Here is my recent tracert. I’ve been being hopped to both Russia/Sweden with no help from AT&T. Also, it’s not just a problem when connecting to your servers, it’s connecting anywhere.
traceroute to 185.224.132.24 (185.224.132.24), 30 hops max, 38 byte packets 1 104-15-116-1.lightspeed.miamfl.sbcglobal.net (104.15.116.1) 1.379 ms 1.197 ms 1.045 ms 2 ----99.167.39.58 (99.167.39.58) 2.115 ms 2.353 ms 2.017 ms 3 ----99.167.141.216 (99.167.141.216) 2.504 ms 2.323 ms 2.393 ms 4 ----12.83.70.77 (12.83.70.77) 16.382 ms 12.83.70.73 (12.83.70.73) 7.251 ms 26.706 ms 5 ----fldfl401igs.ip.att.net (12.122.155.169) 11.058 ms 9.283 ms 15.256 ms 6 ---- mai-b1-link.telia.net (62.115.11.1) 4.731 ms 4.856 ms 4.585 ms 7 ----ash-bb2-link.telia.net (62.115.120.176) 48.938 ms 49.787 ms 52.686 ms 8 ----prs-bb3-link.telia.net (62.115.112.243) 192.276 ms 198.509 ms 195.440 ms 9 ----adm-bb3-link.telia.net (62.115.121.154) 130.221 ms ----adm-bb3-link.telia.net (213.155.136.20) 141.729 ms ----adm-bb3-link.telia.net (62.115.121.154) 139.027 ms 10 ----adm-b6-link.telia.net (62.115.116.125) 136.632 ms 150.326 ms 140.326 ms 11 ----novoserve-svc069390-ic354347.c.telia.net (62.115.188.167) 131.551 ms 137.359 ms 141.548 ms 12 ----Vlanif711.zar-dcd.cust.novoserve.com (89.105.192.233) 141.323 ms 145.288 ms 131.631 ms 13 ----zomro8.server.com (185.224.132.24) 135.940 ms 137.867 ms 130.193 ms
I don't know what you are tracing to - it's not our IP.
Went from 50ms when on west coast to 100+ and from 20ms on east coast to 50. Was all fine up until around the ranked patch. I mostly play with west coast friends and can’t play under 100ms and without lag anymore. Going a little crazy trying to identify and fix the issue. Was on the phone with Comcast for five hours two days ago convinced they were throttling me.
Can you please perform a traceroute to 192.207.0.1 and let me know what city you're in.
Dont know if you are still responding to this thread but, after this new update I have a constant 80-85 ping. Usually have 20-40 depending on the server. I ran a traceroute to your IP and it returns
1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 1 ms 1 ms 1 ms lime-wan01.bloombb.net [160.32.96.1]
3 21 ms 21 ms 21 ms lag-34-1900-99.ear3.Atlanta2.Level3.net [4.28.178.221]
4 46 ms 46 ms 46 ms 4.14.27.102
5 59 ms 58 ms 58 ms 104.160.135.35
6 59 ms 59 ms 59 ms ae99.er02.atl01.riotdirect.net [104.160.143.242]
7 * * * Request timed out.
After 7 everything else times out.
Your ISP indicates they're based in Michigan (Manifold Services?) but they send this traffic to us in Atlanta. They appear to be connected to CTS Telecoms as well as Level3/Centurylink. If they routed to us there, they would have much better performance as you would land in Chicago. Can you open a helpdesk ticket with them to see what they can do on their side?
I should have mentioned, I am Northern Alabama. I made a lengthy call with my ISP and they said that they couldnt find an issue with the routing on their end. They suggested the usual port forwarding solutions. What is frustrating is before this new patch I had such good ping 20-40ish then after this patch I have consistent 80. Thank you for the support but any other ideas?
Can you DM me your IP address and the name of your ISP in-case the data I have is resolving in correctly to MI.
After upgrading my internet speed to 1gb down, trying a vpn, and dealing with my isp for a week, I am at a loss for what to do to get the latency that I was getting before the ranked patch.
More bandwidth wont improve your latency in most circumstances. In case I've missed it - which ISP are you with and what city are you in? If you want you can DM me your IP address as well and I will see if there's something that we can do.
Same here. Lakeland, Florida, Spectrum internet. Constant 70-90 ping with network error and high average ping every game.
Tracing route to 192.207.0.1 over a maximum of 30 hops
1 4 ms 4 ms 3 ms 192.168.0.1
2 17 ms 28 ms 14 ms 072-031-129-005.res.spectrum.com [72.31.129.5]
3 17 ms 24 ms 18 ms 071-046-027-061.res.spectrum.com [71.46.27.61]
4 31 ms 136 ms 40 ms bundle-ether28.tamp27-car1.bhn.net [72.31.208.77]
5 27 ms 43 ms 30 ms 072-031-006-000.res.spectrum.com [72.31.6.0]
6 51 ms 166 ms 60 ms hun0-0-0-5-tamp20-cbr1.bhn.net [72.31.3.51]
7 74 ms 49 ms 61 ms bu-ether19.chctilwc00w-bcr00.tbone.rr.com [66.109.6.42]
8 81 ms 49 ms 67 ms bu-ether17.hstqtx0209w-bcr00.tbone.rr.com [66.109.1.70]
9 61 ms 78 ms 69 ms ge-3-1-0.cr1.sea20.tbone.rr.com [66.109.6.90]
10 44 ms 99 ms 47 ms 66.109.5.121
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
1 4 ms 4 ms 3 ms 192.168.0.1
2 17 ms 28 ms 14 ms 072-031-129-005.res.spectrum.com [72.31.129.5]
3 17 ms 24 ms 18 ms 071-046-027-061.res.spectrum.com [71.46.27.61]
4 31 ms 136 ms 40 ms bundle-ether28.tamp27-car1.bhn.net [72.31.208.77]
5 27 ms 43 ms 30 ms 072-031-006-000.res.spectrum.com [72.31.6.0]
6 51 ms 166 ms 60 ms hun0-0-0-5-tamp20-cbr1.bhn.net [72.31.3.51]
7 74 ms 49 ms 61 ms bu-ether19.chctilwc00w-bcr00.tbone.rr.com [66.109.6.42]
8 81 ms 49 ms 67 ms bu-ether17.hstqtx0209w-bcr00.tbone.rr.com [66.109.1.70]
9 61 ms 78 ms 69 ms ge-3-1-0.cr1.sea20.tbone.rr.com [66.109.6.90]
10 44 ms 99 ms 47 ms 66.109.5.121
11 * * * Request timed out.
Hop 4 shows some huge issues before you're even out of the local area. Can you log a fault with Spectrum about this. This is either localized congestion that they'll have to address with capacity changes or you might have some other more local problems with your service. If you don't log faults with your provider, it can be difficult to get attention on these types of issues.
Spectrum in Florida, packet loss has been a lot better, very minimal. I am getting either 65-70 ping to what I believe is the Chicago servers, and I get about 75-80 ping to the NY servers. I have been in touch with support though I have not heard back since I replied to my ticket with all the logs and trace routes they asked for.
It's just frustrating having a poor connection to the servers in a competitive FPS. I feel at a huge disadvantage. Last resort is finding a VPN I guess. I just don't understand why this is a Valorant issue. I've always had good connection for at least a decade to various online multiplayer games. I do understand that data is routed differently. Really appreciate you responding to this thread still and I know many of these issues are out of your hands.
Tracing route to 192.207.0.1 over a maximum of 30 hops
1 5 ms 3 ms 4 ms 192.168.0.1
2 17 ms 21 ms 10 ms 072-031-128-165.res.spectrum.com [72.31.128.165]
3 22 ms 11 ms 11 ms 071-046-024-157.res.spectrum.com [71.46.24.157]
4 22 ms 19 ms 19 ms bundle-ether33.tamp20-car1.bhn.net [71.44.2.195]
5 16 ms 13 ms 17 ms hun0-0-0-5-tamp20-cbr1.bhn.net [72.31.3.51]
6 19 ms 33 ms 59 ms bu-ether19.chctilwc00w-bcr00.tbone.rr.com [66.109.6.42]
7 40 ms 48 ms 44 ms bu-ether17.hstqtx0209w-bcr00.tbone.rr.com [66.109.1.70]
8 45 ms 38 ms 38 ms bu-ether12.dllstx976iw-bcr00.tbone.rr.com [66.109.6.39]
9 38 ms * 36 ms 66.109.5.121
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
6 19 ms 33 ms 59 ms bu-ether19.chctilwc00w-bcr00.tbone.rr.com [66.109.6.42]
This hop is sick. You can run longer type traces with pingplotter etc. They may try and blame CPU on the device or schedulers for a slower response but the honest truth is you can see 16ms is possible to this location yet you have variance up to 59ms. This could be for a lot of different reasons but more commonly, some interface is running hot and your packets are waiting in buffers.
Where VPNs may help is that they tend to have unicast addresses and your can route 'around' these spots. Unfortunately if everybody starts jumping on those same routes, they'd just end up overloaded too.
Like I suggested above, logging these issues with Spectrum does help. Their own data will show spikes in complaints about poor performance. from pockets of their user base and it may help them prioritize upgrading vs all the other engineering opportunities their teams might have. We also have raised the general concern of this FL area with our contacts there and are trying to work on some strategies to address this with them.
u/RiotKorensky I received a reply from support. They had me use this tool but gave me different IP's to use. Here's a sample using the WinMTR tool with your IP.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 426 | 426 | 1 | 5 | 119 | 1 |
| 072-031-128-165.res.spectrum.com - 0 | 426 | 426 | 10 | 20 | 157 | 13 |
| 071-046-024-157.res.spectrum.com - 0 | 426 | 426 | 11 | 20 | 163 | 16 |
| bundle-ether33.tamp20-car1.bhn.net - 0 | 426 | 426 | 12 | 22 | 135 | 17 |
| hun0-0-0-5-tamp20-cbr1.bhn.net - 0 | 426 | 426 | 13 | 23 | 164 | 20 |
|bu-ether19.chctilwc00w-bcr00.tbone.rr.com - 0 | 426 | 426 | 15 | 28 | 142 | 23 |
|bu-ether17.hstqtx0209w-bcr00.tbone.rr.com - 0 | 426 | 426 | 38 | 50 | 175 | 49 |
|bu-ether12.dllstx976iw-bcr00.tbone.rr.com - 0 | 426 | 426 | 36 | 48 | 162 | 50 |
| 66.109.5.121 - 67 | 117 | 39 | 0 | 51 | 101 | 61 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 86 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
| 192.168.0.1 - 0 | 426 | 426 | 1 | 5 | 119 | 1 |
Hop 1 has a worst ping of 119 - please make sure you're wired to your router and if so, maybe try replacing your cable etc. Something in your home shouldn't be responding that slowly.
u/RiotKorensky My recent response from support....
Hey again!
Thanks for the update. Looking through this, the following steps should resolve your issue.1) I'd like you to make sure you've installed the latest Windows Updates. VALORANT is optimized to work best when on the latest version of Windows and updating can resolve a number of issues.
2) I know this might sound weird, but if you get high FPS try capping your FPS to 128 or lower in the in-game video settings. This will decrease the network load due to the way VALORANT works. More context on this can be found here:
https://twitter.com/arkem/status/12479225170978693143) It could be that other programs are interfering with VALORANT. To eliminate the possibility of that happening, let's turn off your unnecessary start up processes. This has the added benefit of making your PC boot up faster :)
* Press [Windows Key] + R
* Type msconfig into the text bar at the bottom of the menu
* Click on the Services tab
* Check Hide all Microsoft services <--- Super important! Protects you from accidentally disabling a key process!
* Click the Disable All button
* Find vgc and re-check that one. This is required for VALORANT
* Click on the Startup tab (Note: Windows 10 has you go to a Task Manager Tab, which has no disable all button. Disable the ones you see there manually)
* Click on the Disable All button
* Click on the Apply button
* Click on the OK button
* Restart your computer4) Make sure to configure your firewall/antivirus so that it's not blocking VALORANT traffic. We're going to borrow our League of Legends resource to walk you through it here:
- https://support-leagueoflegends.riotgames.com/hc/en-us/articles/201752664-Troubleshooting-Connection-Issues#firewall-troubleshooting-0-4And here's another tracert. Still being routed back to Texas and the trail ends.....
Tracing route to 192.207.0.1 over a maximum of 30 hops
1 5 ms 2 ms 6 ms 192.168.0.1
2 11 ms 11 ms 29 ms 072-031-128-165.res.spectrum.com [72.31.128.165]
3 13 ms 18 ms 11 ms 071-046-024-157.res.spectrum.com [71.46.24.157]
4 27 ms 23 ms 29 ms bundle-ether33.tamp20-car1.bhn.net [71.44.2.195]
5 20 ms 16 ms 16 ms hun0-0-0-5-tamp20-cbr1.bhn.net [72.31.3.51]
6 24 ms 21 ms 26 ms bu-ether19.chctilwc00w-bcr00.tbone.rr.com [66.109.6.42]
7 39 ms 38 ms 39 ms bu-ether17.hstqtx0209w-bcr00.tbone.rr.com [66.109.1.70]
8 45 ms 48 ms 43 ms bu-ether12.dllstx976iw-bcr00.tbone.rr.com [66.109.6.39]
9 * * * Request timed out.
10 * * * Request timed out.
I've had some discussions with the engineering team at Charter/Spectrum and they do balance the exit points for Florida between Atlanta or Dallas depending on their own core capacity. You shouldn't be seeing the packet loss issues that were present weeks ago but unfortunately It's still taking 50ms to get you to our point of presence in Dallas. You can see that fluctuation in the 2nd hop between 11ms and 29ms which is the reality of being on a large cable access network. Your first hop is unusually high. Are you on wired ethernet and how old if your router?
Any news sir?
Tracing route to 192.207.0.1 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 10 ms 9 ms 072-031-128-165.res.spectrum.com [72.31.128.165]
3 9 ms 7 ms 8 ms 071-046-026-159.res.spectrum.com [71.46.26.159]
4 13 ms 12 ms 12 ms bundle-ether33.tamp20-car2.bhn.net [71.44.2.205]
5 12 ms 16 ms 13 ms hun0-1-0-5-tamp20-cbr1.bhn.net [72.31.3.97]
6 16 ms 15 ms 16 ms 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com [66.109.6.96]
7 41 ms 39 ms 47 ms bu-ether17.hstqtx0209w-bcr00.tbone.rr.com [66.109.1.70]
8 37 ms 35 ms 35 ms 107.14.19.49
9 34 ms 35 ms 35 ms 66.109.5.121
10 * * * Request timed out.
11 * * * Request timed out.
I cant do anything to make the jump from your house -> Tampa - > Houston - >Dallas any faster unfortunately. We're investigating options around closer server locations as a potential mitigation for this but I can't promise anything yet.