makes no sense that the same issue is happening to random people in different cities and or countries. gotta be a bliz issue
We troubleshoot one connection at a time, until the information indicates there is a regional or ISP specific issue.
This data indicates his issues starts at his network, so that’s where we start.
Assuming that multiple people that have latency or disconnections, which are standard internet connectivity issues, are entirely Blizzard’s fault is just ignorant.
lol calling customers ignorant huh?
It’s your ISP
every city in this world is our ISP … hahahaha
Joke bro , i’m tired of this, same problem every year, same excuses from Blizz !
2 Likes
If you can’t tell that I’m a customer like you, then you’re ignorant.
Blue text for blizzard employees.
wow, delusional much? and i quote…
Keep playing tech support, buddy.
hahahhaha exactly
Welcome to the Technical Support forum for World of Warcraft. This forum exists to provide World of Warcraft customers with a place to discuss technical issues with each other and Blizzard Tech Support staff members. While Blizzard Tech Support staff regularly monitors and replies to this forum (between 7am-8pm Pacific, 7 days a week), it is not meant as a place to resolve complex issues, because of the nature of forums. If you cannot resolve your issue through the forum, we recommend checking our Knowledge Center for resolutions and workarounds for common issues.
Hey brownout,
We were having some DDoS issues earlier today, but they don’t match up with when you put in your ticket. The DDoS issues should be resolved now. To keep the other thread from being further derailed by unrelated issues, I moved your reports to your own thread.
Also, please keep in mind that Zungar is volunteering his time to help you. While I can understand that this is a frustrating issue, we’re here to troubleshoot with eachother and figure out what’s going on, not fight. Let’s try to keep it civil, please. If you want help figuring out why you’re disconnecting, we’re happy to give it a look, but let’s try to work together okay?
It’d help to figure your issue out if we can catch a disconnection with winMTR. We were seeing some Canadian issues which cleared up a week or so ago, but they may be back now.
If you’re still having this problem, please create a WinMTR test which catches a disconnection. You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this.
If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.
~~~~
WinMTR goes here
~~~~
2 Likes
i disconnected during this one…
and again
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 1 | 1160 | 1158 | 2 | 13 | 116 | 9 |
| 174.4.64.1 - 1 | 1160 | 1158 | 9 | 14 | 95 | 16 |
| rd3ht-be100-1.ok.shawcable. net - 1 | 1164 | 1163 | 10 | 15 | 89 | 14 |
| rc3no-be12.cg.shawcable. net - 1 | 1160 | 1158 | 16 | 21 | 121 | 20 |
| rc2wt-be100.wa.shawcable. net - 1 | 1160 | 1158 | 26 | 30 | 120 | 31 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Both show packet loss from the first hop. The second has significantly higher latency on the first hop. Normally, anything over 10 on the first hop is bad. It’s not unusual for that to be 1-2.
Wired or wireless?
If wireless, 2.4 or 5 Ghz?
Router firmware and network drivers are up to date?
dont talk to me
Brownout,
Zungar is correct, regardless of your earlier disagreement. Zungar, appreciate the attempt to help but I’d recommend letting us take it from here to prevent this disagreement from escalating any further.
The packet loss at the beginning of the test and the latency stability issue is the best explanation for the problem. Based on that, your best bets are:
- Restart your PC and power cycle your connection
- Use an ethernet cable if you’re on wifi. If that works, get closer to the router or get it replaced if it just started having issues.
- If you have a separate modem and router, try bypassing the router and wire directly into the modem via etherenet. If that works, the router’s on the fritz - you’ll want to hit up your ISP to replace it.
If none of it works, let’s snag a new WinMTR and let us know how each of the tests above worked - if anything changed, etc. We’ll use those to look for more options.