That sounds good, you might be right about consistency though. I reran the pathping and this time on that same problem one as last time I got this
7 46ms 12/ 100 = 12% 0/ 100 = 0% .google-ic-373139.ip.twelve99-cust.net [62.115.145.225]
So a 12% packet loss…but around the same MS.
Just to clarify a point here.
Getting higher than 2% packet loss is an issue for things like communication and gaming.
Getting 12 is really bad in that same vein.
Something like video streaming, not really a problem though.
Do this.
Run the command prompt.
Put in Ping (server) -t
Let that run for 10 minutes.
Then check your packet loss.
For (server) put in a website like google or the IP of the bnet server, try a few different ones at the same time actually. Like microsoft google, yahoo, battlenet, etc
You can also review this thread I made last year with some links and tools:
-For everyone having connection issues of various types: UPDATE 8-7-23
Yea and I came across this post on reddit from April 23rd of this year
From what someone said in the comments they called their ISP and apparently those twelve99 had a cut cable in the ocean.
I don’t know what ISP he has, but when I was a customer service rep for comcast it was company policy to make a customer happy (within reason) but that could mean lowering his bill by $30 for 6 months, upgrade to a better package for the cost of current plan. In a civil & advanced society you would not have a billion dollar company milking its customers. I used to shell out all kinds of free stuff for people. Good times.
Ahhh I tried putting in the IP of the Central D4 server and was getting Request Timed out. It wasn’t sending anything back on the ping it seems. I’ll try the bnet server.
just saying - absolutely no expert here - but i had similar issues with league of legends ages ago, only this game.
after some people helped me they figured out there was indeed something wrong with my connection on the way to the lol servers. after many annoying calls with my isp it got finally fixed.
I have some detailed instructions for running the ping test in the post at that link above. But will put it here too:
-For everyone having connection issues of various types: UPDATE 8-7-23
Try to run a standard ping test to battle.net or any other common website. To do this:
[quote=“DTMAce-1687, post:79, topic:51386”]
Try a simple ping test tobattle.net. To do that, hit the Windows key + R. Type CMD in the run box and enter.
In the black CMD screen, put inping battle.net -t. The -t allows the test to continue till canceled.I’m using this just to see what your ping is. Run the test and time it for say 5 minutes. After 5 minutes hit CTRL+C. Then view the results. It will show number of packets sent, received, and amount lost. And will show the latency minimum, maximum and average.
Please note, we are testing this using a server that will respond to the ping request. The Diablo IV game server IPs will not work. This is to get us a gauge on how your latency is to a connection.
Similarly, you can run this test to
google.comor any other place to test as well. If you run this test and every place you test shows a lot of latency, then you have issues, potentially at the router/modem.
Ok just finished the test on battle.net for the ping. Here are the results.
Ping statistics for 137.221.106.104:
Packets: Sent = 434, Received = 434, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 82ms, Average = 80ms
That doesn’t show anything no.
Try running some to other places as well.
What you should do is start it, then have it run in the background while playing.
Then after playing for say 15-30 minutes, ctrl-c and see what results you have then.
Alright I’ll try that. I’ll also try that WinMTR as well while playing.
Ok here are the results after playing D4 while running WinMTR as well as pinging battle.net
Ping statistics for 137.221.106.104:
Packets: Sent = 952, Received = 952, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 92ms, Average = 80ms
WinMTR:
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|-------------------------------------------- |---------|--------|------|------|------|------|
| [Omitted] - 0 | 1019 | 1019 | 0 | 1 | 23 | 1 |
| [Omitted] - 1 | 1015 | 1014 | 0 | 3 | 14 | 4 |
| 209.170.69.52 - 1 | 1015 | 1014 | 0 | 4 | 14 | 5 |
| .ash-b3-link.ip.twelve99.net - 0 | 1019 | 1019 | 17 | 19 | 44 | 20 |
| .rest-bb1-link.ip.twelve99.net - 1 | 1015 | 1014 | 0 | 20 | 30 | 21 |
| .ash-b2-link.ip.twelve99.net - 1 | 1015 | 1014 | 0 | 20 | 54 | 21 |
|.google-ic-373139.ip.twelve99-cust.net - 3 | 920 | 894 | 0 | 34 | 86 | 24 |
You can also make a self-calling batch file by just opening Notepad and inserting the following:
@echo off
:loop
echo Tracing Route to 34.170.230.40, 8 hops max starting time: %date% %time%
tracert -h 8 34.170.230.40
timeout /t 10 /nobreak
goto loop
Save the file as ’ continous_ping.bat ', or whatever name you want really as long as it’s saved as a .bat file. Put it somewhere safe, or on your desktop it won’t hurt anything.
When you start to get lag spikes, run this as admin, it will automatically pop up a cmd prompt on the screen and start to run the Tracert by itself. I’ll explain the lines just so you understand.
The @Echo off just means it won’t display the command prompts itself, so it won’t show the actual ‘tracert IP address’ in the beginning.
The :loop is just a starting point for the loop itself, i.e. this is the start of the loop, repeat everything below this line essentially.
echo - literally just displays the text after it in that format in the CMD prompt itself. So everytime it starts a new loop it’ll show you “Tracing route to bla bla, 8 hops max, starting at date/time” You can leave this out if you want, up to you, I just find it helps to pintpoint when the tracert was sent.
tracert - h 8 IP address - is just running the tracert to a max of 8 hops (you only took 7 hops to get to the server so I typically add 1 more just in case)
timeout /t 10 /nobreak - just means it will continue this loop after its run every 10 seconds until you either close the CMD prompt itself, or hit Ctrl C to quit when it pops up on the prompt itself, which it will do for every 10 seconds after it runs.
goto loop - just repeats the process all over again
Just popping in to say OP is far from the only person having this issue. There are plenty, but a lot of them just don’t care enough to say anything about it.
Haha thank you, I actually write a bunch of .bat for my job regularly (although I never have used tracert in batch or any networking tool). Typically I’m writing batch to invoke some Java or execute python scripts etc lol.
I’ll try this out though, what’s crazy is right now my MS seems to have stabilized. it’s floating around 60-70 MS in a town. I did change some network settings since I had some power saving settings directly set on my ethernet adapter. I also changed a setting to shutdown battle.net launcher when I launch D4 as well. I’ll run this command tomorrow though during the times it usually spikes my connection to see if I can pick up the times when I get massive latency spikes.
Oh you should know exactly what each line does then lol, I’m sorry I typically explain as if the person on the other end doesn’t know anything. Makes it so much easier talking to some one who actually knows what batch files are, and that what I put in won’t hurt their computer.
You probably already know then you could technically have it save to a txt file too for the log instead of just leaving it up and sifting through the cmd prompt. Up to you of course, we all have our preferences. Depending on what I’m doing I’ll sometimes just have it log it for me instead, and I’ll come back 20 minutes later to read through it.
Game performance has significantly decreased after the latest patch. I get massive lag spikes and sometimes complete freezes for like 30 seconds, leaving and reentering the game often fixes the lag spikes. Inventory/shop/seasonpass menus often refuse to load or give various errors.
Idk wth happened but I hope it gets fixed soon.
I get the same issue. Can play fine with 80-200ms then start getting 2000-3000ms. I’ll zone to one zone or dungeon and have normal latency then zone somewhere else and I get 2-3000ms and it’s unplayable.
It is 100% Blizzard fault.
Stop blaming ISP and take the issue seriously Blizzard. Tons of people experience they just stop playing instead of reporting it.
I play from Thailand Bangkok on optic fiber connection.
No one here has asked the OP if he has an active VPN running while he plays. This can make his connection seem bi-polar at times. I’ve ran into this more times than i care to remember with our customers calling in to complain about internet speed and connection issues. I show up and run multiple test with my equipment and speeds are always fine with no packetloss. Then we go to the PC and its always a VPN or some crap firewall or internet security they are running throttling their connection.
maybe pay for your internet instead of stealing it from the neighbor, or get a different isp, ever stop think actually use more than 2 brain cells and think maybe the isp is dog water after a certain time? mine is, guess what I don’t do though? I don’t come here crying about it.