Forum Discussion
wow
- 5 years ago
lm8542 wrote:The top part of my post was omitted somehow without me being aware of it. Needless to say I have been using Hughesnet since 2011 and have been playing wow (world of warcraft) with the expected latency on both gen 4 and gen 5 after upgrade. The latency was playable and between 400ms-1200ms depending on the time of day. But last year I had to suspend playing this game because I thought it was the game as they released a new update. However, after contacting blizzard tech support and giving them my winMTR results I was told by the tech that it was a hughesnet problem and my first post is part of his reply to my request for help.
Level3 is a known problem. It's a serious bottleneck. Basically, anything owned by Qwest has been having trouble with WoW players. Lucky for me, almost everything goes through a Quest server on my route, so I experience monsterous latency. So WoW playing is nearly impossible.
The only solution is for HughesNet to route around the problem servers, though after talking with a very high up person, that is a major undertaking.
Qwest won't help unless you are their customer.
Could you post your original post in full? (You said some of it was cut off) That might help.
Yeah, so your lag time is bound to be a minimum of 500ms because you're going over satellite to a ground station on the west coast that's then connected to the internet. Click here for details on how to calculate what your minimum would be.
Yeah, neat tool it came out 502.38 when I entered the beam etc. But when it was last working like thas was early last year, spring 2019. The photo's I posted I can't even get to load but if anyone can see them they show the latency I get 628ms immediatly going up continuously like within 5 seconds 2100, 3500, 6800,12000, 16000 I don't remember it getting above 16000 ms but the photo I uploaded today was 14368ms. I don't think anyone else on Hughes.net is getting that kind of latency. Usually when it tops off at say 12000-16000ms it goes down to like 4000-8000ms. Those numbers don't allow for anything other than logging in and logging out. I am surprised I can even log in.
- lighthope15 years agoSenior
lm8542 wrote:Yeah, neat tool it came out 502.38 when I entered the beam etc. But when it was last working like thas was early last year, spring 2019. The photo's I posted I can't even get to load but if anyone can see them they show the latency I get 628ms immediatly going up continuously like within 5 seconds 2100, 3500, 6800,12000, 16000 I don't remember it getting above 16000 ms but the photo I uploaded today was 14368ms. I don't think anyone else on Hughes.net is getting that kind of latency. Usually when it tops off at say 12000-16000ms it goes down to like 4000-8000ms. Those numbers don't allow for anything other than logging in and logging out. I am surprised I can even log in.
I've gotten 44,000 latency.
It's better in the morning/afternoon. Evenings will kill you.
- lm85425 years agoSophomore
44,000ms is worse than anything I have ever gotten but I don't have the patience to click and wait 3 minutes and click etc. I have to stop paying for wow until we have a better connection.Thanks for your response. Wish you better luck than I .lol
- lighthope15 years agoSenior
For giggles, I did a traceroute to the servers for World of Warcraft (West), Final Fantasy XIV (Montreal), and Guild Wars 2.
WoW had two hops time out. Guild Wars 2 had three. And FF14 had one.
I don't know if that means anything. The servers at those particular hops may simply be rejecting test probes, though sometimes they will work.
I know GW2 can be a nightmare because you get very little time to move out of the way of a telegraphed attack.
WoW is more fogiving, but those high latency spikes make even that just hair-pulling.
Maybe FF14 is more workable. idk. They have a lot of fights with a lot of complicated things. On the plus side, it is heavily scripted, so if you learn the script, it is easier to anticipate and pre-move/pre-cast.
Related Content
- 10 years ago
- 7 years ago
- 6 months ago