The game has been lagging for the last 2 days, since March 18th around 8pm EST. There is a slight delay, about every 8 seconds, on doing things like talking to NPCs, looting corpses or chests. Even the mobile mission table app is receiving this lag, with a slight stutter on completing a mission every 8 seconds or so. This is happening across multiple realms (other people I’ve talked to) and it’s been happening to me and others across multiple computers, internet connections, etc.
My ping is the same as always (74ms home and world) but the lag is still present without it affecting the in game ping reporter. This isn’t a personal internet issue, so please don’t suggest I fix my internet - this is affecting multiple people.
You guys could all be using similar internet backbones, that could be suffering from buffer-bloat/packet loss. So yes, it’s still going to be recommended you run an MTR on your connection to rule out bad connection hops.
This forum is for community based troubleshooting for localized issues involving the system, client, network and connection. Any troubleshooting you receive will be focused on that. Troubleshooting assistance of this nature also requires information on the system and connection to be provided.
As for the idea that this is a service issue because multiple people are seeing issues, keep in mind there are hundreds of thousands of players at any given moment and each server has hundreds or thousands of players at any given moment. Knowing other people with issues doesn’t allow for the assumption that it is a service issue. Just that the issue isn’t unique. (Which with millions of monthly players around the globe, it likely wouldn’t be)
That doesn’t mean there can’t be a service side issue. It does happen, it may even be the case here, but based on the number of reports so far, there is no evidence of such. So until a service issue is confirmed, you would need to perform localized troubleshooting as mentioned previously.
To better help with that, you should also provide system and connection information as instructed here.
If you are not comfortable doing community based troubleshooting for this issue you could also put in a direct support ticket (Click the support button at the top right of the page, then click contact support. Be sure to include the requested system files)
Ive been having the exact same problem and im 99% sure its not on my end. I wasnt gonna report it cuz I know Blizzard wont do or say anything to help. Im just hoping the tech guys that monitor servers will fix it on Monday or maybe the Tuesday maintenance will fix it.
If its still happening after that, Im going to be quite annoyed because its making me not even want to play the game.
Well, as a long time PAYING CUSTOMER who is going through and has GONE THROUGH the VERY SAME ISSUE during various EXPANSION updates FOR YEARS, I do not know you, know your internet status, computer status, or even cognitive abilities, but I am about 91% sure the issue is not on your end either.
The standard response from the Buzzard (inc) the various ‘blood sworn’ sycophants, “customer support” and other lackeys will always be as it always has been (eg. ‘It’s NOT Blizzard’s fault, despite the fact that you have changed absolutely nothing in settings, software, hardware, or server status, etc. and though we are working on releasing a new expansion with infinite changes that affect the existing game, it certainly shouldn’t even be considered as a possibility that it is in any way shape or form our fault… unless you can prove it’) and you should never expect more than that.
Yeah, the fact that everything was running FINE for numerous people up until the most recent update and that immediately after that update numerous people started all having the very same issue, should probably just be likened to “conspiracy theory” and of course never ever attributed to Blizzard messing up the game (again) DESPITE the fact that EVERY OTHER SITE YOU USE STILL FUNCTIONS normally.
While it is possible an update changed how the game works together with something that you and some other people have in common, it doesn’t mean the company developed a bad product no one can use. Plus, lagging every few seconds can have so many causes that it’s impossible for support staff or the community to dissect every possibility with you. Here are just a few examples:
| Potential causes:| |
|-|-|-|
| • Corrupt UI data | • Corrupt game install
| • Poor connection or routing | • Defunct addons
|• Poorly coded addons | • Slow hard drive
|• Poor performance from GPU | • Corrupted GPU drivers
|• Worn out components |• Overheating components
|• Software incompatibility |• Power management issues
|• Pending Windows updates |• System permissions
|• Corrupt network software |• Antivirus identifying non-issues
|• Modem updates from ISP | • Router updates from ISP
|• Home network conflicts
We could be here all year. Because of the myriad of reasons, the community and support staff start with the basics.
Paying for a game subscription doesn’t include PC technician services. Since Blizzard offers tech support as a courtesy, and the community is here volunteering their time, you may run into an issue that can’t be resolved to your satisfaction and requires professional assistance. You won’t find that the situation is much different with other gaming companies.
In your case, the second hop in the network is showing a high ping, which continues throughout the test. This node is either your building or neighborhood, but your ISP would have more info about it. I recommend contacting them because you can’t resolve this in your home.
Im more concerned with this hop below, but after researching it, it seems like there isnt much I can do until the server host recoginizes it and fixes it.
Notice how that 1290 isn’t appearing on the hop after it? That means it’s just the node ignoring your ping. It’s a protection mechanism to prevent DDoS attacks from affecting the server. A DDoS uses ICMP requests, which is also what WinMTR uses on a much, much smaller scale.
To find a problem in a WinMTR, you look to where the lag first appears. That would be in your ISP’s network.
Never implied “no one” can use it. However, if it a bug in the updated program of the game it is a product that is not functioning properly for some people and thus impeding functionality.
I do notice, as should everyone else, that in your list of “potential causes” not a single one could be attributable to the company (Blizzard) or the game itself.
Very convenient for those doing their best to once again dissuade any/all culpability of problems that have REGULARY occurred after expansion releases and pre releases from being attributed to the company that has coded and recoded and programmed the game.
Again, implying that it is a problem caused on the user’s end and NOT by Blizzard’s technical staff.
Good work though, all the same. I’m sure your brownie badge will be updated to platinum for your efforts.
Weird take on what I had to say. Most problems are local to the machine, the peripherals, Windows, etc. When the problem is the game client, the forum is flooded with complaints, as is the ticket system—that isn’t the case here. I don’t think that Blizzard is free of all responsibility, but the issue described does not match with behavior in the past or other current topics regarding the software itself. If you only think “Blizzard bad, customer always right,” this forum probably can’t help since troubleshooting requires effort on your part. Best of luck resolving your issue.
Did another WinMTR today and it still shows the same hop causing the problem. No early hops are bad now. From what Ive found is that ‘eqla1’ stands for Equinix LA, so its their problem, I just dont know how to fix it. Maybe Blizzard techs can report it to them or something?
That test doesn’t show any issues. Your worst ping to the server is 26ms if you look at the last line, which is the server itself. Again, that Blizzard hop is designed to ignore your test. I’m not having any issues and it shows a response time for 3200ms for me. If it was really 3200ms, I wouldn’t be able to login.
The test was only run for 1min 41sec, so it’s not a big data grab to look over either.