Frequent lag spikes since the 6/4 maint in US

Technical Support
Below is my post from the bug report forum on 6/7. I'm reposting because it was suggested that the issue may be a technical one and not a bug.
06/06/2019 06:56 PMPosted by BossDogg
I've done the following:
- run updates on my PC
- reboot my PC
- reboot my router
- reboot my cable modem
- run speed tests on speedtest.net

Despite the above actions I've been encountering frequent lag and disconnects. The speed test resulted in 4ms ping, 202.29 Mbps DOWN, 35.12 Mbps UP. In game the latency bar goes from 41ms to the 120's, to the 140's. Suddenly the latency bar jumps into the 1100's. The latency results in disconnects and random half second pauses. All of the lag and disconnects were in solo games on T-13.

06/10/2019 04:04 AMPosted by BossDogg
The authentication issue the IT folks @ Blizz were working on should be resolved at this point. However, last night between 8p and 11:30p EST I encountered frequent lag spikes. Again this morning between 6am and 7am EST high ping rates (200 - 440ms) and lag spikes.


As of 1:05pm today I ran a speed test @ speedtest.net with the following results:
- 7ms Ping
- 214.08 Mbps Down
- 36.09 Mbps Up

I'm in NYC on Optimum.
Update:
The WinMTR was run from 7:12pm to 7:24pm EST today. The tracert was run right as after the WinMTR. In game between 7:12pm and 7:30pm my ping on the US server, in a solo game, was 122-167. This is while standing still in Act 5 town.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 959 | 959 | 0 | 0 | 14 | 0 |
| 10.240.166.117 - 0 | 959 | 959 | 6 | 9 | 31 | 8 |
| 67.59.225.48 - 0 | 959 | 959 | 6 | 10 | 33 | 8 |
| ool-4353e11c.dyn.optonline.net - 0 | 959 | 959 | 8 | 12 | 40 | 10 |
| 64.15.8.172 - 0 | 959 | 959 | 8 | 12 | 38 | 10 |
| 64.15.2.78 - 0 | 959 | 959 | 10 | 14 | 39 | 12 |
| be3033.rcr21.ewr02.atlas.cogentco.com - 0 | 959 | 959 | 31 | 35 | 62 | 33 |
| be2600.rcr23.jfk01.atlas.cogentco.com - 0 | 959 | 959 | 32 | 36 | 56 | 39 |
| be2896.ccr41.jfk02.atlas.cogentco.com - 1 | 955 | 954 | 31 | 34 | 101 | 32 |
| be3362.ccr31.jfk04.atlas.cogentco.com - 0 | 959 | 959 | 33 | 37 | 56 | 37 |
|be2556.rcr11.b001587-1.jfk04.atlas.cogentco.com - 0 | 959 | 959 | 33 | 37 | 57 | 35 |
| 38.88.194.29 - 0 | 959 | 959 | 33 | 41 | 239 | 36 |
| ae1-br01-eqny8.as57976.net - 0 | 959 | 959 | 82 | 88 | 174 | 87 |
| et-0-0-2-br02-eqch2.as57976.net - 0 | 959 | 959 | 82 | 89 | 210 | 84 |
| et-0-0-29-br01-eqch2.as57976.net - 1 | 940 | 935 | 81 | 88 | 202 | 83 |
| 137.221.65.132 - 1 | 955 | 954 | 81 | 87 | 253 | 85 |
| et-0-0-2-br01-eqla1.as57976.net - 1 | 928 | 922 | 81 | 103 | 4619 | 83 |
| be1-pe01-eqla1.as57976.net - 0 | 959 | 959 | 83 | 87 | 112 | 87 |
| 24.105.30.129 - 0 | 959 | 959 | 83 | 87 | 109 | 88 |
|________________________________________________|______|______|______|______|______|______|

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.5.200]
2 18 ms 7 ms 8 ms 10.240.166.117
3 9 ms 7 ms 10 ms 67.59.225.48
4 10 ms 9 ms 9 ms ool-4353e11c.dyn.optonline.net [67.83.225.28]
5 10 ms 9 ms 10 ms 64.15.8.172
6 12 ms 13 ms 12 ms 64.15.2.78
7 34 ms 32 ms 33 ms be3033.rcr21.ewr02.atlas.cogentco.com [154.54.11.77]
8 35 ms 34 ms 39 ms be2600.rcr23.jfk01.atlas.cogentco.com [154.54.40.29]
9 33 ms 39 ms 44 ms be2896.ccr41.jfk02.atlas.cogentco.com [154.54.84.201]
10 34 ms 35 ms 36 ms be3362.ccr31.jfk04.atlas.cogentco.com [154.54.3.10]
11 36 ms 41 ms 43 ms be2556.rcr11.b001587-1.jfk04.atlas.cogentco.com [66.28.4.94]
12 50 ms 35 ms 38 ms 38.88.194.29
13 107 ms 88 ms 83 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
14 83 ms 90 ms 84 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
15 83 ms 85 ms 84 ms et-0-0-29-br01-eqch2.as57976.net [137.221.65.2]
16 84 ms 96 ms 85 ms 137.221.65.132
17 85 ms 83 ms 86 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
18 84 ms 91 ms 85 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
19 85 ms 91 ms 85 ms 24.105.30.129


It looks like the traffic is going from NYC (zip code 10013), to Denver, out to the Netherlands (137.221.x.x addresses) and then back into Blizzard in the US.
06/10/2019 04:54 PMPosted by BossDogg
It looks like the traffic is going from NYC (zip code 10013), to Denver, out to the Netherlands (137.221.x.x addresses) and then back into Blizzard in the US.
Blizzard is using (perhaps "recycling" is a better word) some IP addresses they had originally registered for Europe... that's ok.

Were you playing while the WinMTR was running ?
Did you get the lag spikes you are normally getting ?

The WinMTR looks fairly clean to me...
In game, in town, standing still. High latency and random bumps. I did not have the spikes where the latency meter turns orange or red this evening. However, in my original thread in the bug report forum I did document that experience.

I don't see the benefit of sending traffic over seas to the Netherlands only to return it back to the US. The experience I'm currently getting in the US realm, is the common if I play in the EU or Asia realms.

Update:
Also, having trouble loading list of heroes when attempting to swap between characters in-game.
Update:
Error code 1016 and disconnect while attempting to bring up the leaderboard with season Wizard list filtered by my friends.

While the WinMTR may look fairly clean to you. I disagree since my latency sometimes hovers 120-170ms and sometimes worse at 200-500ms. This is unacceptable since I'm paying more $$ to have higher internet bandwidth. Its not like my ISP is controlling this pathing. If Blizzard is a customer of Congentco in Denver, then they can get them to stop routing traffic out of the US to the Netherlands.
The IP couldn't be in Europe, otherwise the ping must be over 100, but it was ~85 in your log.

As Boubou said, Blizzard recycled the ISP addresses. Those 137.* was registered in Europe is re-used for NA server. A support had explained before in this thread (read the last paragraph): https://us.battle.net/forums/en/d3/topic/20765028176#post-7

I found that the in-game ping in town is higher than in rift. Also, when freshly loaded into a game, the ping is higher than normal probably because the game is still busy in loading assets behind the scene. I'd only take log while running a rift.

I also don't find any problem in your log too. Make sure running WinMTR for 10 minutes while you a experiencing high latency. Restart WinMTR if not.
06/10/2019 07:03 PMPosted by BossDogg
Update:
Error code 1016 and disconnect while attempting to bring up the leaderboard with season Wizard list filtered by my friends.

While the WinMTR may look fairly clean to you. I disagree since my latency sometimes hovers 120-170ms and sometimes worse at 200-500ms. This is unacceptable since I'm paying more $$ to have higher internet bandwidth. Its not like my ISP is controlling this pathing. If Blizzard is a customer of Congentco in Denver, then they can get them to stop routing traffic out of the US to the Netherlands.
would you grep a new WinMTR log that cover a dc?

Edit:
- higher bandwidth isn't the same as lower latency. They are two different measures, like width and height of a rectangle.
- I don't think Blizzard is a customer of Congentco. NA server is in LA.
@Maskraider:
I didn't have WinMTR running when the disconnect occurred.

06/10/2019 07:21 PMPosted by Maskraider
higher bandwidth isn't the same as lower latency.

Come on dude... really?? You must think I just fell off the banana boat and stumbled onto the shore.

High bandwidth does not guarantee lower latency, but having higher bandwidth is there to allow for better through put performance which would lead to low/lower latency. Switching to the higher bandwidth had an immediate improvement in latency since Feb. of this year for me. Only after the recent 6/4 maintenance did I have the high latency, disconnects, and lag spike issues. If recycling those EU IP addresses is causing the problem then they need to revisit those changes. Truly, what ever the changes were, they need to revisit those changes. The latency issue isn't limited to just me. Just because there aren't 1000 threads in the general forum about lag/latency doesn't mean many others aren't experiencing lag/latency.

Seriously, playing in the US realm is like playing in the Asia realm right now. The lag spikes lead to delays in spells firing off, and leads to delays and rubber banding when attempting to teleport. I expect this kind of experience when playing on the Asia realm, not on the US realm. I expect lag spikes and relatively high latency when playing on the EU realm but certainly not nearly as choppy as playing on the Asia realm and not nearly as smooth as playing on the US realm.

06/10/2019 07:19 PMPosted by Maskraider
I found that the in-game ping in town is higher than in rift. Also, when freshly loaded into a game, the ping is higher than normal probably because the game is still busy in loading assets behind the scene. I'd only take log while running a rift.

I also don't find any problem in your log too. Make sure running WinMTR for 10 minutes while you a experiencing high latency. Restart WinMTR if not.


I don't see how in town ping would be higher in a solo game than in a solo rift where there are so many more entities and calculations going on. Especially if one is standing still for more than 3 mins in town. If my latency meter, in town, goes green > orange > red > red over 2000ms > red over 3000ms and sits there for more then 15 seconds, there is no point to entering a rift/GR to play the game unless it is purely for diagnostic purposes. In most cases players are not going to rush to the forums and complain if its a once or twice occurrence and performance returns to normal. Which leads to why I'm posting. Performance isn't returning to normal and the lag spikes in town, in rifts/GRs and while running bounties in sanctuary are frequent/recurring. No, I don't play the game with WinMTR running in the background all the time waiting for a problem to occur because I've had a mostly steady experience with very few latency/lag spike/disconnect problems.

The whole point of posting the diagnostic info. is because there is a problem. The high values in the log are indicating that there is a problem. Back in January 2019, my latency in a solo game, in town, in the US realm would be in the 90's (green). I doubled my down load speed with my ISP in Feb. and immediately the solo in-game, in town latency went down to 40's to 60's range (green). Almost half the latency was immediately experienced. I don't understand how you come to the conclusion that the 80+ms values are a "nothing wrong" scenario.

The thread you linked to shows dates of Jun 13. What year?
Bandwidth is like the number of lanes of a highway. Latency is the time required to travel from one end to the other end. Bandwidth won't affect the latency. It does affect the throughput as more cars can travel in parallel, but each car still take the same among of time to travel.

If you didn't run the test while you were getting laggy/dc, the result is meaningless.

I play on all three regions. I know what their normal latency, 50, 200, 300 respectively. Even with 300ms, the game can still play smoothly. But if latency jumps up and down, that's a problem.

You can mouse over the date of the post to see the year.
I'd also monitor the CPU, hard disk, and network loading on the Task Manager and/or Resource Monitoring tool.
D3 isn't a demanding game. These loadings shouldn't be very high.
If you find them abnormally high. Try tracing which process causes the loading.
3 solo GR runs plus time in town on the US realm (approx 38-41 mins):
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 1617 | 1617 | 0 | 0 | 29 | 0 |
| 10.240.166.117 - 1 | 1613 | 1612 | 4 | 17 | 111 | 9 |
| 67.59.225.48 - 1 | 1606 | 1603 | 4 | 17 | 84 | 5 |
| ool-4353e11c.dyn.optonline.net - 1 | 1602 | 1598 | 5 | 18 | 91 | 39 |
| 64.15.8.172 - 1 | 1613 | 1612 | 5 | 19 | 83 | 9 |
| 64.15.2.78 - 1 | 1613 | 1612 | 8 | 21 | 80 | 11 |
| be3033.rcr21.ewr02.atlas.cogentco.com - 1 | 1602 | 1598 | 28 | 42 | 116 | 34 |
| be2600.rcr23.jfk01.atlas.cogentco.com - 1 | 1613 | 1612 | 28 | 43 | 105 | 34 |
| be2896.ccr41.jfk02.atlas.cogentco.com - 1 | 1609 | 1607 | 27 | 41 | 99 | 37 |
| be3362.ccr31.jfk04.atlas.cogentco.com - 1 | 1605 | 1602 | 31 | 44 | 123 | 33 |
|be2556.rcr11.b001587-1.jfk04.atlas.cogentco.com - 1 | 1606 | 1603 | 30 | 44 | 135 | 37 |
| 38.88.194.29 - 1 | 1606 | 1603 | 31 | 48 | 211 | 35 |
| ae1-br01-eqny8.as57976.net - 1 | 1613 | 1612 | 80 | 95 | 469 | 84 |
| et-0-0-2-br02-eqch2.as57976.net - 1 | 1566 | 1558 | 79 | 120 | 4700 | 86 |
| et-0-0-29-br01-eqch2.as57976.net - 1 | 1600 | 1596 | 78 | 110 | 1975 | 85 |
| 137.221.65.132 - 1 | 1594 | 1591 | 78 | 111 | 4687 | 88 |
| et-0-0-2-br01-eqla1.as57976.net - 1 | 1594 | 1589 | 77 | 105 | 2503 | 85 |
| be1-pe01-eqla1.as57976.net - 1 | 1606 | 1603 | 80 | 93 | 175 | 88 |
| 24.105.30.129 - 1 | 1613 | 1612 | 80 | 94 | 160 | 85 |
|________________________________________________|______|______|______|______|______|______|

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 2 ms 1 ms 5 ms router.asus.com [192.168.5.200]
2 9 ms 8 ms 10 ms 10.240.166.117
3 10 ms 26 ms 19 ms 67.59.225.48
4 13 ms 11 ms 13 ms ool-4353e11c.dyn.optonline.net [67.83.225.28]
5 60 ms 66 ms 72 ms 64.15.8.172
6 17 ms 10 ms 14 ms 64.15.2.78
7 68 ms 79 ms 74 ms be3033.rcr21.ewr02.atlas.cogentco.com [154.54.11.77]
8 42 ms 33 ms 37 ms be2600.rcr23.jfk01.atlas.cogentco.com [154.54.40.29]
9 38 ms 32 ms 30 ms be2896.ccr41.jfk02.atlas.cogentco.com [154.54.84.201]
10 35 ms 35 ms 36 ms be3362.ccr31.jfk04.atlas.cogentco.com [154.54.3.10]
11 37 ms 35 ms 36 ms be2556.rcr11.b001587-1.jfk04.atlas.cogentco.com [66.28.4.94]
12 41 ms 36 ms 35 ms 38.88.194.29
13 106 ms 96 ms 105 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
14 89 ms 84 ms 84 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
15 84 ms 82 ms 83 ms et-0-0-29-br01-eqch2.as57976.net [137.221.65.2]
16 82 ms 92 ms 82 ms 137.221.65.132
17 84 ms 82 ms 80 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
18 95 ms 92 ms 87 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
19 90 ms 93 ms 84 ms 24.105.30.129


Mostly green latency bar. There were brief periods where the latency bar went green > orange > green (no more than 2 secs on orange). There were several times where my Wizard was rubber-banding when teleporting around rapidly in Archon mode (green latency bar). There were several occurrences where Archon mode ended and I attempted to teleport away and the delay was long enough for the monsters to land a multiple hits (green latency bar). This is kind of behavior is what I would experience on the Asia realm, but much more frequently rubber-banding and delays in spells firing off. On the Asia server there would also be noticeable UI delays such as the Archon stack count being out of sync and behind what is happening in game.

Again I expect this on the Asia realm, but not on the US realm. If its happening on the US realm that indicates a problem. As previously stated I rebooted my PC, cable modem, and router. Let me be clear so that there is no room for confusion. I shut down all 3 devices. I powered up the cable modem and waited 4 minutes. I then powered up the router and waited another 4 minutes. I then booted my PC and went about my business as usual. None the above has positively impacted performance in D3.
06/10/2019 10:47 PMPosted by Maskraider
I'd also monitor the CPU, hard disk, and network loading on the Task Manager and/or Resource Monitoring tool.
D3 isn't a demanding game. These loadings shouldn't be very high.
If you find them abnormally high. Try tracing which process causes the loading.

To be clear, when I said that in February the doubling of my download speed provided an immediate improvement in performance, I was able to maintain a 40's to 60's latency bar status in game with:
- my wife on an active VPN connection to her employer's network
- I'm on an active VPN connecton on a second PC to my employer's network
- my son watching a video on youtube while playing StarCraft 2
- 3 smart phones connected over wifi to the web/social media

Yesterday evening it was only me in D3, my wife watching a movie on Amazon, my son watching netflix, the 3 smart phones, and all 3 of us with a few web pages open (mostly static pages and we all run ad-block).

This entire time that I've been posting since yesterday, my in-game latency bar shows 120+ms regardless of my in-game activies. From 40 to 120 is a noticeable jump in latency.
06/10/2019 11:11 PMPosted by BossDogg
Yesterday evening it was only me in D3, my wife watching a movie on Amazon, my son watching netflix,
^^^ this . . . @.@
If you don't get laggy when others don't use internet, then . . .
After the bump in bandwidth in Feb. my connection and gaming experience has been smooth like sliding on corn oil. After the 6/4 maint. that is no longer the case.
Update:
6:08am EST shutdown PC, router, and cable modem
6:14am EST power up cable modem
6:21am EST power up router
Verify internet access via smart phone:
- load www.foxnews.com
- load www.nbcnews.com
- load www.youtube.com
- load www.amazon.com
- load www.yahoo.com
- load www.msnbc.com
- load www.facebook.com (login and immediately log out after page fully loads so as not to trigger full body convulsions and spasms from social media allergies)

6:28am EST power up PC
- Login and open Task Manager (14.1 GB RAM available, 2% CPU utilization @ 3.4Ghz)
- Launch Firefox, VLC (music), EVGA NV-Z GPU monitoring tool, Battle.net Launcher, EVGA Precision XOC (EVGA GTX 1060 6GB running @ factory default clock speeds with adaptive fan configuration)

6:33am EST Fire off a trace route to 24.105.30.129
Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.5.200]
2 7 ms 7 ms 7 ms 10.240.166.117
3 7 ms 7 ms 9 ms 67.59.225.48
4 11 ms 12 ms 9 ms ool-4353e11c.dyn.optonline.net [67.83.225.28]
5 18 ms 10 ms 8 ms 64.15.8.172
6 13 ms 11 ms 12 ms 64.15.2.78
7 33 ms 33 ms 34 ms be3033.rcr21.ewr02.atlas.cogentco.com [154.54.11.77]
8 33 ms 34 ms 33 ms be2600.rcr23.jfk01.atlas.cogentco.com [154.54.40.29]
9 32 ms 31 ms 31 ms be2896.ccr41.jfk02.atlas.cogentco.com [154.54.84.201]
10 36 ms 37 ms 34 ms be3362.ccr31.jfk04.atlas.cogentco.com [154.54.3.10]
11 35 ms 35 ms 34 ms be2556.rcr11.b001587-1.jfk04.atlas.cogentco.com [66.28.4.94]
12 42 ms 50 ms 35 ms 38.88.194.29
13 84 ms 107 ms 107 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
14 84 ms 157 ms 84 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
15 81 ms 81 ms 86 ms et-0-0-29-br01-eqch2.as57976.net [137.221.65.2]
16 82 ms 83 ms 82 ms 137.221.65.132
17 84 ms 82 ms 81 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
18 98 ms 85 ms 86 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
19 84 ms 86 ms 85 ms 24.105.30.129


Notice from hops 1 to 6 the ms values are below 15. I don't have D3 or any other game loaded yet. The web pages in Firefox are mostly static. The only devices on my internal network are my PC, 3 smart phones, a tablet, and my VOIP device. Notice all of the 137.221.x.x address have ms values above 80. These are Blizzard/Battle.net IP's as you've stated. This shows an issue on Blizzard's side of things.

Please don't give me any of this "I don't see anything wrong crap". I'll run and post WinMTR data as soon as I can to follow up.
If not 80ms, what number you are expecting?

Before go to the conclusion who is responsible, lets trace the message.
At the start, CSC Holdings (67.59.*) is located in central (according to IP registration).
Then it routed to Cogent (154.54.*) still in central.
Hop 11, 66.28.* still belongs to Cogent (Washington according to IP registration).
Hop 12, 38.88.* still belongs to Cogent (New York according to IP registration).
Hop 13 is blizzard net located in LA (west coast).

It spent half of the time (42ms) from hop 1 to 12 (still within CSC and Cogent). If the IP registration is collect, it is still in central or east coast.
It took 42ms from hop 12 to 13. It is reasonable? I don't know. If hop 12 is really in NY, then it took 42ms from east coast to west coast could be normal, IMO.

You may ask why the data went to east coast first? May be the IP registration is incorrect (like 137.221.* are not in Europe) or some problem in routing. In the latter case, you may ask your ISP for confirmation. (Blizzard isn't an ISP.)

(As I said, Blizzard's ISP isn't Cogent. And my WinMTR trace doesn't go thru Cogent at all.)
After making a few calls I was able to get through to a tech at Cogent. We are getting less than accurate info. in WinMTR and trace route. Their network is setup to de-prioritize ICMP traffic.
Ok, so I played D3 without problems most of the day and after a break for dinner out, the rest of the evening (past midnight CST). I've been having no problems for a few weeks now, since May's batch of error 1016's. There was nothing I needed to do to resolve that, fortunately...it self-corrected after updating windows 10.

I got up today, logged in, and was immediately booted... error code 1016.
I tried again-booted immediately, same error. I updated Windows 10 with the new update and tried logging in again...same error.

Now it just so happens there was a Blizzard update this morning...is there a connection to one or more of the "fixes" they applied?

I have updated all update-able programs (drivers, windows 10, scan-checked D3, went thru blizzard, discord and steam apps to verify/turn off streaming and overlays, and made sure all other non-essential programs were stopped via the task manager. I also set D3 to be started in 32-bit mode and set the Battle.net app to close when D3 starts. My latency did go down, from average of 180 msec to 70 msec, and the bit of lag I had is now gone. My computer/vid card is old, but is still on the Blizz list of compatible vid cards.

I have an Arris Surfboard SB141 modem and a Linksys EA6350 router. My computer is direct-connected to the router. My wifi is only for my kindle. There are no other people using my internet access.

Edit: I also have been having to try several times to log in because of authentication problems. This is a totally new thing for me.

Ideas, anyone...?
@Maskraider:
Some additional info:
Hops 7-11 are bundled ethernet (notice the BE at the beginning of the host name). Hop 7 is in New Jersey (most likely Edgewater). The tech. said that the hop 7 router is connected to Cablevision/Altice. Its a 100 gigabit connection and there was only 30 gigabits worth of traffic (yesterday afternoon/evening) so its definitely not flooded/congested. The 33ms ping is because their system places ICMP traffic at a lower transmission priority. The true ping if the priority was removed would be much lower. The tech looked at the other routers in the trace route path and said none of them were congested and none were near their capacity. The almost uniform ping values reflects de-prioritization.

He also stated that Cogent had an issue with one of their routers in Dallas Fort Worth, Texas (DFW) a few days ago but the issue was quickly resolved (a minutes to a few hours time frame). However, the DFW router that was fixed is not in the trace route list. Any spill-over traffic would have had a barely noticeable impact on other routers given their high transmission capacity. None of the Cogent routers in the list had issues.
@Gandra:
There is probably other threads in the tech support forum that are discussing the authentication issue(s). I was able to get into the game yesterday evening and did not encounter authentication problems. I set the game to hard difficulty and attempted to complete some set dungeons. There are far fewer ppl on level 70 hard difficulty doing set dungeons. While doing the set dungeons I did encounter lag spikes and the latency hovered above 130ms in-game. I'll have to run WinMTR and trace routes later on today.

Join the Conversation

Return to Forum