It is perfectly normal for some nodes that have 100% packet loss, mtr check for ICMP ping for every node in between our PC and the target server, and not all server is configured to reply for ICMP ping requests, so if it has 100% loss but the next hop is 0% loss, then it is fine, the traffic went through the node without packet loss. It just the node don’t answer to ICMP ping requests.
It become problem when the destination server (last hop) have packet loss, then it is definetely have loss somewhere too (check all previous host to identify possible suspect)
I am from South East Asia, I don’t know what actual server D4 is using, it was fine during launch at 2 June 6AM GMT+7 just until yesterday (4 June around noon GMT+7) the Server was terrible got upwards of 500ms, previously it was ~90-100ms
Confirmed. I was able to reproduce the 100% packet loss in Blizzard’s own network, starting at ae1-br02-eqda6.as57976 net. (This was after it left Comast).
I discovered that the IP route at the hop of :ae1-br02-eqda6.as57976 net and et-0-0-2-br02-swlv10.as57976 net is actually going to The Netherlands, even though I am in NA - no wonder there is latency.
IP Details For: 137.221.74.35
Decimal:2312981027
Hostname:ae1-br02-eqda6.as57976 net
ASN:57976
ISP:Blizzard
Services:Datacenter
Assignment:[Likely Static IP](https:// whatismyipaddress com/dynamic-static)
Country:Netherlands
State/Region:Noord-Holland
City:Amsterdam
IP Details For: 137.221.65.67
Decimal:2312978755
Hostname:et-0-0-2-br02-swlv10.as57976 net
ASN:57976
ISP:Blizzard
Services:Datacenter
Assignment:[Likely Static IP](https:// whatismyipaddress com/dynamic-static)
Country:Netherlands
State/Region:Noord-Holland
City:Amsterdam
Redacted below. First line is Comcast, the rest Blizzard, staring with going to Blizzard’s servers in The Netherlands. So the IP route leaves Comcast at 66.208.216.198 and the travels to these two hops and 137.221.68.77 - in The Netherlands - and then times out. After that it finishes the last hop in Irvine at 24.105.30.129.
I’d put up another thread with these results. I’m betting that this thread has been buried. Blizzard likely isn’t going to test this thing out themselves.
It is a live test, testing all nodes along a path at the same time. If there is an issue at any node, every node after will show similar or worse results. You won’t have a bad node and then everything after it look normal.
The easiest thing to do is look the first hop which is your PC to your network device. If everything looks good there, look at the final visible hop. If there is no data loss there and the latency looks about how it should, then the test can show anything on the nodes in between and it won’t matter because your data made it to the end point as it was supposed to.
Some nodes ignore test requests, some deprioritize such request and some mask the data giving fake results. What we are looking for over individual node numbers are patterns.
If you start losing data at say hop 2 and every node after that shows similar or worse data loss? that is something to look at. If latency jumps up really high a say hop 4 and then continues to increase … that is something to look at.
The other thing to keep in mind is that the test only measures what your connection is doing at that moment it is running. And connection issues have a bad habit of being intermittent. Enough to mess up a game over time but not gonna affect much else in a very noticeable way. So always run the test for a consistent length (10 minutes is what I recommend) while replicating the issue. If you cant replicate in 10 minutes, stop and restart the test every 10 minutes and keep going until the issue happens. Those are the results you want to analyze.
Enough people have done this and posted their results over the last two days for it to be pretty clear where the problem lies - even if you are not particularly fond of the results given here.
I think the problem is clearly on their end, since my PC/network works totally fine with everything else - except Live D4. WoW, Overwatch (and all other games, including the D4 Open Beta) work fine on the exact same setup.
This thread was from 3 days ago and was not about the game specifically. If you read the first post in the thread, they were asking if it was on their end.
Most of the thread is talking about AT&T fiber, and also folks in DFW Texas. Lots of people with similar setups from a similar area having an issue.
They wanted to compare pathways to the servers so were shown how to run a WinMTR. So they could analyze their own data pathway.
The Blue is helping them learn to read the data along the path to the servers. This particular thread was not about the rubber banding or in-game issues specifically.
Yeah, this is still happening today. Anytime I transition zones, it’s like rolling the dice if I will start rubber banding and/or lag until I DC. I’m happy to provide any troubleshooting data requested.
Can we get the specific IP address for American Diablo 4 servers so we can run a proper MTR? Right now, we’re just guessing by running it to D3 at 24.105.30.129.
For anyone else having problems running the game with AT&T in the DFW area, using a VPN made it work for me last night but I’d rather that be a temporary workaround.
Proton, it’s some freebie that I’m sure is collecting usage data. I just wanted to try something to see if it would work.
edit: I connected through one of its US servers. Not sure exactly where in the US it’s located but it seems to have done the trick. My latency is ~100ms which isn’t the best but FAR better than 2.5k right before disconnect.
I have tried Proton VPN before, it worked for me for a bit but the lag spikes bounced back after 30 minutes of gameplay. When will Blizzard respond to this? It is NOT the only thread about this issue.
I’m testing from StarLink so expect some packet loss and latency, but no other online game I’m playing is having the latency issues that I’m seeing with D4 (as reported in-game with CTRL+R as well as these tests below). I did not have these latency issues with either of the prior Beta test runs.
I loaded both addresses in a browser first to make sure my DNS cache was current and to lessen lookup delays.
Here, a concurrent run (two instances of WinMTR):
Me to Battle.net (not sure what IP I’m using for the D4 server I’m connecting to, but it shows issues within your network):
The above shows that somewhere around et-0-0-29-br01-eqla1.as57976.net (as57976.net is a Blizzard domain hosting things like World of Warcraft and living in Google’s cloud) for me there’s a huge delay being added, if MTR is to be trusted.
What other metrics/information would help Blizzard narrow down this issue if MTR is not helping?
DxDiag if it helps: https://www.dropbox.com/s/tnnfftkmpxss3f5/24182%20Lolmer%20DxDiag.txt?dl=0
I grabbed the IP from the FenrisDebug.txt that it suggests I had connected to and and this while teleporting to Kyovashad and entering the chapel. As often happens, I DC’d after transitioning into the chapel. Here’s the WinMTR from that…
I 2023.06.06 13:15:04.430787 [Game] ---------------- UIModalNotificationManager::ShowModal 2: Travel to Kyovashad?
I 2023.06.06 13:15:08.705870 [WarpManager] Intro portal to exterior Subzone 'Frac_Kyovashad'
I 2023.06.06 13:15:08.754506 [WarpManager] Starting intro effect default_warp_effect_intro (239914)
I 2023.06.06 13:15:09.695589 [WarpManager] Setup complete
I 2023.06.06 13:15:09.695597 [WarpManager] Waiting for limbo warp...
I 2023.06.06 13:15:09.771527 [Game] Local player long distance snap (-427.25, -83.34, 23.01 vs 0.00, 0.00, 0.00)
I 2023.06.06 13:15:09.805264 [Game] [Prism] 14996: Purged 223 entries from the render and compute pipeline caches in 0.341ms
I 2023.06.06 13:15:09.811096 [Game] Disposing UI for World
I 2023.06.06 13:15:09.978082 [Game] Client entered world | world: Limbo | CWorldID: 524288
I 2023.06.06 13:15:09.979172 [WarpManager] Warped into limbo
I 2023.06.06 13:15:10.299095 [WarpManager] Waiting for fast loading time (1.00s)...
I 2023.06.06 13:15:10.304980 [Game] ClientConnect | ip_address: 34.121.204.51:6114 | connection_id: 17
I 2023.06.06 13:15:10.368565 [Game] Computed solution to server puzzle | bits: 7 | solution: 196 | time_elapsed_us: 32
I 2023.06.06 13:15:10.541589 [Game] Initializing client world Limbo...
I 2023.06.06 13:15:10.690418 [WarpManager] Transfer prefetch begin (loop)
I 2023.06.06 13:15:11.322800 [WarpManager] Starting loop for loading screen
I 2023.06.06 13:15:15.224974 [WarpManager] Starting loop outro effect default_warp_effect_intro (239914)
I 2023.06.06 13:15:16.226283 [WarpManager] Waiting for destination warp...
I 2023.06.06 13:15:16.232512 [WarpManager] Prefetch complete
W 2023.06.06 13:15:16.572654 [Game] 'ClientReceiveHeartbeat' received out-of-order tick | cur_tick: 844483 | msg_tick: 844477
I 2023.06.06 13:15:16.573569 [Game] Initializing client world Sanctuary_Eastern_Continent...
I 2023.06.06 13:15:16.573777 [Game] Local player long distance snap (0.00, 0.00, 0.00 vs -1402.30, 154.29, 100.92)
I 2023.06.06 13:15:16.812797 [Game] [Prism] 14996: Purged 31 entries from the render and compute pipeline caches in 0.299ms
I 2023.06.06 13:15:16.812824 [Game] Disposing UI for World
I 2023.06.06 13:15:16.904887 [Game] Adjusting world Sanctuary_Eastern_Continent (69068) subzone from Kehj_Ridge (531775) to Frac_Kyovashad (445430)
I 2023.06.06 13:15:16.973796 [Game] Client entered world | world: Sanctuary_Eastern_Continent | CWorldID: 524289
I 2023.06.06 13:15:17.419671 [WarpManager] Warped into destination
I 2023.06.06 13:15:17.763518 [WarpManager] Starting outro effect default_warp_effect_outro (239915)
I 2023.06.06 13:15:17.825598 [Game] Client: sHandleDisconnect | connection_id: 16
I 2023.06.06 13:15:17.825762 [Game] ClientDisconnect | connection_id: 16 | reason: 8 | connections_remaining: 1
I 2023.06.06 13:15:17.825768 [Game] ConnectionBase::Disconnect | connection_id: 16 | reason: 8 | connectiontype: 4
I 2023.06.06 13:15:18.961178 [WarpManager] Portal completed
I 2023.06.06 13:15:48.522245 [Game] ClientConnect | ip_address: 35.224.189.134:6113 | connection_id: 18
I 2023.06.06 13:15:48.584290 [Game] Computed solution to server puzzle | bits: 7 | solution: 191 | time_elapsed_us: 26
I 2023.06.06 13:15:48.726249 [Game] Initializing client world Sanctuary_Eastern_Continent...
I 2023.06.06 13:15:48.726484 [Game] Server Transition prefetch/preload starting on frame 54623
W 2023.06.06 13:15:55.827989 [Game] 'ClientReceiveHeartbeat' received out-of-order tick | cur_tick: 447 | msg_tick: 444
I 2023.06.06 13:15:58.872031 [Game] Server Transition prefetch/preload starting on frame 55938
I 2023.06.06 13:16:05.025458 [Game] Client: sHandleDisconnect | connection_id: 17
I 2023.06.06 13:16:05.025969 [Game] ClientDisconnect | connection_id: 17 | reason: 8 | connections_remaining: 1
I 2023.06.06 13:16:05.025975 [Game] ConnectionBase::Disconnect | connection_id: 17 | reason: 8 | connectiontype: 4
I 2023.06.06 13:16:05.026552 [Game] Client Disposed world 524288.
I 2023.06.06 13:16:09.670766 [Game] Received pong with old sequence!
I 2023.06.06 13:17:02.684946 [Game] Application Deactivated. Active: 0 Minimized: 0
I 2023.06.06 13:17:08.943531 [Game] Client: sHandleDisconnect | connection_id: 18
I 2023.06.06 13:17:08.947198 [Game] [Prism] 14996: Purged 212 entries from the render and compute pipeline caches in 0.282ms
I 2023.06.06 13:17:08.953949 [Game] Disposing UI for World
I 2023.06.06 13:17:09.055145 [Game] Client Disposed world 524289.
I 2023.06.06 13:17:09.057063 [Game] UICommon::OnGameDisconnected msg=The game connection has been lost: your client has been disconnected from the server.
I 2023.06.06 13:17:09.057073 [Game] ---------------- UIModalNotificationManager::ShowModal 0: The game connection has been lost: your client has been disconnected from the server.
It sure looks like something is being fumbled when transitioning between zones/servers.
I had exactly the same issues with a, also on a 2 Gig fiber line (not ATT) in the Dallas area as some others in this post. No issues with other games, and tried all kinds of tricks that others have suggested.
As some people were saying their partners had been OK at the same time they were having issues on the same connection, I figured at least some people must have issues not related to their connection. So I went ahead and installed the game on my gaming laptop which has lower specs than my gamin rig, but still enough with and RTX 2060 to play the game just fine. It’s also on a WiFi connection instead of hardwired so was expecting things to get worse.
However, NOW it works perfectly, no issues whatsoever with latency when I play D4 on the laptop. It only happens on the desktop.
I am on AT&T fiber as well as in the DFW area and the game has been, barely playable with the lag spikes, disconnects and rubberbanding that ensues.
I port forwarded to no avail, even went so far as to shut off my avast shielding, which, strangely enough, alleviated the issue slightly where I could get longer playable times. Yet when the server decides that it’s had enough nothing really stops it, even reconnecting after a dc INTO a dc.