Okay, thanks for the information. So this is mine, from Springfield, IL.
Tracing route to launcher.playneverwinter.com [208.95.184.201] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms homeportal [192.168.1.254] 2 24 ms 18 ms 18 ms 99-20-136-1.lightspeed.dctril.sbcglobal.net [99.20.136.1] 3 18 ms 19 ms 25 ms 99.4.195.13 4 * 20 ms 19 ms 99.136.7.32 5 25 ms 19 ms 19 ms 12.83.43.129 6 41 ms 43 ms 38 ms 12.122.117.97 7 42 ms 42 ms 41 ms 0.ae10.BR3.ATL4.ALTER.NET [204.255.168.253] 8 * * * Request timed out. 9 169 ms 169 ms 168 ms internap-gw.customer.alter.net [152.179.134.214] 10 166 ms 169 ms 166 ms border3.ae2-bbnet2.bsn.pnap.net [63.251.128.71] 11 166 ms 168 ms 167 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78] 12 167 ms 166 ms * 198.49.243.250 13 168 ms 166 ms 167 ms 198.49.243.253 14 170 ms 167 ms 171 ms launcher.playneverwinter.com [208.95.184.201]
Trace complete.
Pinging launcher.playneverwinter.com [208.95.184.201] with 32 bytes of data: Reply from 208.95.184.201: bytes=32 time=167ms TTL=47 Reply from 208.95.184.201: bytes=32 time=166ms TTL=47 Request timed out. Reply from 208.95.184.201: bytes=32 time=167ms TTL=47
Ping statistics for 208.95.184.201: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 166ms, Maximum = 167ms, Average = 166ms
Could be Alter.net. And, now I'm stuck at the Vellosk loading screen
Clearly that's the case for many people as it doesn't respond to the trace-route and then every hop after that has much higher pings by an order of magnitude.
This infuriating thing I have found with lagging in the last few months is that something during the spike knocks out my keyboard.. I think it could be related to USB keyboards... when it returns after hitting the esc repeatedly for a good minute the shift often is still lost and on certain classes like GWF the unstoppable will be bugged (fane being the worst offender).
This maybe inherent just to my system admittedly.. but it seemed possibly connected with a patch that changed the launcher? from 32 to 64 bit
I'm now being routed through a comcast server instead of a the verizon alter.net and getting much better pings.
Tracing route to launcher.playneverwinter.com [208.95.184.201] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Grassy-Knoll [192.168.1.1] 2 9 ms 7 ms 7 ms 10.104.192.1 3 8 ms 7 ms 11 ms 72-31-66-134.net.bhntampa.com [72.31.66.134] 4 10 ms 11 ms 12 ms ten0-15-0-9.orld71-car1.bhn.net [71.44.60.184] 5 9 ms 10 ms 28 ms 72-31-220-226.res.bhn.net [72.31.220.226] 6 16 ms 16 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98] 7 20 ms 16 ms 18 ms 0.ae1.pr0.mia00.tbone.rr.com [66.109.1.87] 8 16 ms 16 ms 16 ms be-201-pe03.nota.fl.ibone.comcast.net [173.167.57.117] 9 19 ms 16 ms 18 ms be-12297-cr02.miami.fl.ibone.comcast.net [68.86.82.69] 10 28 ms 26 ms 24 ms be-11422-cr02.56marietta.ga.ibone.comcast.net [68.86.84.153] 11 37 ms 37 ms 37 ms be-10114-cr02.ashburn.va.ibone.comcast.net [68.86.85.9] 12 42 ms 44 ms 42 ms be-10102-cr01.newark.nj.ibone.comcast.net [68.86.85.162] 13 42 ms 42 ms 53 ms be-10203-cr02.newyork.ny.ibone.comcast.net [68.86.85.186] 14 46 ms 54 ms 46 ms be-10373-pe02.onesummer.ma.ibone.comcast.net [68.86.86.158] 15 53 ms 46 ms 46 ms 96-87-8-114-static.hfc.comcastbusiness.net [96.87.8.114] 16 48 ms 49 ms 48 ms border3.ae1-bbnet1.bsn.pnap.net [63.251.128.7] 17 46 ms 47 ms 47 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78] 18 46 ms 55 ms 54 ms 198.49.243.250 19 49 ms 47 ms 47 ms 198.49.243.253 20 56 ms 50 ms 47 ms launcher.champions-online.com [208.95.184.201]
Common to all those traces above(except last): There is a huge jump in ping going into internap-gw.customer.alter.net So it seems there is an issue with that node or the links leading to it. But since it seems to be a problem coming from several directions into it I would guess there is an issue with the router itself.
There are also some packet losses starting when the trace crosses internap-gw.customer.alter.net, which is additional proof something is going on with that router.
The last trace is a good example of how it should look: * Small incremental jumps in ping for each hop * No packet losses
The only way to handle such problems is to raise the issue with your ISP. They should have the contacts to follow up on it.
Late last night and early this morning was very laggy for me. The day before I literally couldn't stay connected for more than 2 minutes before receving the "server not responding" message then the boot. Closed it out and restarted the client - same thing over and over.
From another part of the country. I haven't been able to do anything in game for a couple of days. Usually time out connecting to the login server from the char select screen.
Tracing route to launcher.playneverwinter.com [208.95.184.201] over a maximum of 30 hops:
1 1 ms 6 ms 1 ms MYNET [192.168.1.1] 2 11 ms 14 ms 10 ms 1-69-42-72.skybeam.com [72.42.69.1] 3 12 ms 180 ms 27 ms po5-rtc-1670.den.riseb.net [72.42.99.93] 4 11 ms 18 ms 28 ms po1-rtc-mst-1.den.riseb.net [72.42.98.169] 5 17 ms 18 ms 17 ms g0-20-rtc-dhd.den.skybeam.net [72.42.96.57] 6 32 ms 20 ms 21 ms v153-rtc-402-core-1.nco.riseb.net [208.73.252.89] 7 22 ms 17 ms 26 ms te4-3-rtc-402-bdr-1.nco.riseb.net [208.73.252.41] 8 72 ms 73 ms 67 ms 199.26.56.242 9 88 ms 39 ms 44 ms te0-0-1-2.nr12.b000326-3.dfw05.atlas.cogentco.com [38.122.56.101] 10 50 ms 43 ms 43 ms te0-0-1-1.rcr21.dfw05.atlas.cogentco.com [154.24.2.89] 11 46 ms * 79 ms be3236.ccr22.dfw03.atlas.cogentco.com [154.54.24.165] 12 72 ms 50 ms 87 ms be2269.ccr31.dfw01.atlas.cogentco.com [154.54.7.41] 13 39 ms 39 ms 64 ms be2432.ccr21.mci01.atlas.cogentco.com [154.54.3.134] 14 * 50 ms 48 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166] 15 60 ms 58 ms 61 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222] 16 79 ms 69 ms 71 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130] 17 74 ms 91 ms 84 ms be3599.ccr31.bos01.atlas.cogentco.com [66.28.4.238] 18 99 ms 72 ms 76 ms te0-3-1-5.rcr51.b002133-1.bos01.atlas.cogentco.com [66.28.4.42] 19 78 ms 94 ms 81 ms 38.111.40.114 20 80 ms 88 ms 236 ms 198.49.243.253 21 85 ms 71 ms 74 ms launcher.champions-online.com [208.95.184.201]
Pinging launcher.playneverwinter.com [208.95.184.201] with 32 bytes of data: Reply from 208.95.184.201: bytes=32 time=91ms TTL=46 Reply from 208.95.184.201: bytes=32 time=115ms TTL=46 Reply from 208.95.184.201: bytes=32 time=76ms TTL=46 Reply from 208.95.184.201: bytes=32 time=69ms TTL=46
Ping statistics for 208.95.184.201: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 69ms, Maximum = 115ms, Average = 87ms
So, the consensus seems to be that this is an internet connectivity issue that neither players nor Cryptic can do anything about -- except maybe call your ISP and ask them to talk to their upstream connections.
> @arachnicidus said: > So, the consensus seems to be that this is an internet connectivity issue that neither players nor Cryptic can do anything about -- except maybe call your ISP and ask them to talk to their upstream connections.
That does indeed seem to be the consensus. Specifically it seems like a Verizon router at alter.net is the issue. If you google Verizon and alter.net it seems they’ve used tactics of diliberately over congesting that route before to discourage people from using streaming services since they owned a state in redbox. My wife’s Netflix show was playing fine though while this was going on for me.
You probably need to look elsewhere for the source of your problems. Try run a full scan of the game files, or even reinstalling game, for a start. You could also make sure you have the latest driver from the graphics chip developer.
And if you reinstall game, make sure to do that to an empty directory, the point of the exercise being to refresh any old config/status files that could be bugged.
Comments
Tracing route to launcher.playneverwinter.com [208.95.184.201]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms homeportal [192.168.1.254]
2 24 ms 18 ms 18 ms 99-20-136-1.lightspeed.dctril.sbcglobal.net [99.20.136.1]
3 18 ms 19 ms 25 ms 99.4.195.13
4 * 20 ms 19 ms 99.136.7.32
5 25 ms 19 ms 19 ms 12.83.43.129
6 41 ms 43 ms 38 ms 12.122.117.97
7 42 ms 42 ms 41 ms 0.ae10.BR3.ATL4.ALTER.NET [204.255.168.253]
8 * * * Request timed out.
9 169 ms 169 ms 168 ms internap-gw.customer.alter.net [152.179.134.214]
10 166 ms 169 ms 166 ms border3.ae2-bbnet2.bsn.pnap.net [63.251.128.71]
11 166 ms 168 ms 167 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
12 167 ms 166 ms * 198.49.243.250
13 168 ms 166 ms 167 ms 198.49.243.253
14 170 ms 167 ms 171 ms launcher.playneverwinter.com [208.95.184.201]
Trace complete.
Pinging launcher.playneverwinter.com [208.95.184.201] with 32 bytes of data:
Reply from 208.95.184.201: bytes=32 time=167ms TTL=47
Reply from 208.95.184.201: bytes=32 time=166ms TTL=47
Request timed out.
Reply from 208.95.184.201: bytes=32 time=167ms TTL=47
Ping statistics for 208.95.184.201:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 167ms, Average = 166ms
This maybe inherent just to my system admittedly.. but it seemed possibly connected with a patch that changed the launcher? from 32 to 64 bit
Tracing route to launcher.playneverwinter.com [208.95.184.201]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Grassy-Knoll [192.168.1.1]
2 9 ms 7 ms 7 ms 10.104.192.1
3 8 ms 7 ms 11 ms 72-31-66-134.net.bhntampa.com [72.31.66.134]
4 10 ms 11 ms 12 ms ten0-15-0-9.orld71-car1.bhn.net [71.44.60.184]
5 9 ms 10 ms 28 ms 72-31-220-226.res.bhn.net [72.31.220.226]
6 16 ms 16 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
7 20 ms 16 ms 18 ms 0.ae1.pr0.mia00.tbone.rr.com [66.109.1.87]
8 16 ms 16 ms 16 ms be-201-pe03.nota.fl.ibone.comcast.net [173.167.57.117]
9 19 ms 16 ms 18 ms be-12297-cr02.miami.fl.ibone.comcast.net [68.86.82.69]
10 28 ms 26 ms 24 ms be-11422-cr02.56marietta.ga.ibone.comcast.net [68.86.84.153]
11 37 ms 37 ms 37 ms be-10114-cr02.ashburn.va.ibone.comcast.net [68.86.85.9]
12 42 ms 44 ms 42 ms be-10102-cr01.newark.nj.ibone.comcast.net [68.86.85.162]
13 42 ms 42 ms 53 ms be-10203-cr02.newyork.ny.ibone.comcast.net [68.86.85.186]
14 46 ms 54 ms 46 ms be-10373-pe02.onesummer.ma.ibone.comcast.net [68.86.86.158]
15 53 ms 46 ms 46 ms 96-87-8-114-static.hfc.comcastbusiness.net [96.87.8.114]
16 48 ms 49 ms 48 ms border3.ae1-bbnet1.bsn.pnap.net [63.251.128.7]
17 46 ms 47 ms 47 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
18 46 ms 55 ms 54 ms 198.49.243.250
19 49 ms 47 ms 47 ms 198.49.243.253
20 56 ms 50 ms 47 ms launcher.champions-online.com [208.95.184.201]
Trace complete.
There is a huge jump in ping going into internap-gw.customer.alter.net
So it seems there is an issue with that node or the links leading to it. But since it seems to be a problem coming from several directions into it I would guess there is an issue with the router itself.
There are also some packet losses starting when the trace crosses internap-gw.customer.alter.net, which is additional proof something is going on with that router.
The last trace is a good example of how it should look:
* Small incremental jumps in ping for each hop
* No packet losses
The only way to handle such problems is to raise the issue with your ISP. They should have the contacts to follow up on it.
Ereshkigal - 12k Tiefling SW
Aurora Ravensong - 11.6k Drow CW
Tracing route to launcher.playneverwinter.com [208.95.184.201]
over a maximum of 30 hops:
1 1 ms 6 ms 1 ms MYNET [192.168.1.1]
2 11 ms 14 ms 10 ms 1-69-42-72.skybeam.com [72.42.69.1]
3 12 ms 180 ms 27 ms po5-rtc-1670.den.riseb.net [72.42.99.93]
4 11 ms 18 ms 28 ms po1-rtc-mst-1.den.riseb.net [72.42.98.169]
5 17 ms 18 ms 17 ms g0-20-rtc-dhd.den.skybeam.net [72.42.96.57]
6 32 ms 20 ms 21 ms v153-rtc-402-core-1.nco.riseb.net [208.73.252.89]
7 22 ms 17 ms 26 ms te4-3-rtc-402-bdr-1.nco.riseb.net [208.73.252.41]
8 72 ms 73 ms 67 ms 199.26.56.242
9 88 ms 39 ms 44 ms te0-0-1-2.nr12.b000326-3.dfw05.atlas.cogentco.com [38.122.56.101]
10 50 ms 43 ms 43 ms te0-0-1-1.rcr21.dfw05.atlas.cogentco.com [154.24.2.89]
11 46 ms * 79 ms be3236.ccr22.dfw03.atlas.cogentco.com [154.54.24.165]
12 72 ms 50 ms 87 ms be2269.ccr31.dfw01.atlas.cogentco.com [154.54.7.41]
13 39 ms 39 ms 64 ms be2432.ccr21.mci01.atlas.cogentco.com [154.54.3.134]
14 * 50 ms 48 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
15 60 ms 58 ms 61 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222]
16 79 ms 69 ms 71 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130]
17 74 ms 91 ms 84 ms be3599.ccr31.bos01.atlas.cogentco.com [66.28.4.238]
18 99 ms 72 ms 76 ms te0-3-1-5.rcr51.b002133-1.bos01.atlas.cogentco.com [66.28.4.42]
19 78 ms 94 ms 81 ms 38.111.40.114
20 80 ms 88 ms 236 ms 198.49.243.253
21 85 ms 71 ms 74 ms launcher.champions-online.com [208.95.184.201]
Pinging launcher.playneverwinter.com [208.95.184.201] with 32 bytes of data:
Reply from 208.95.184.201: bytes=32 time=91ms TTL=46
Reply from 208.95.184.201: bytes=32 time=115ms TTL=46
Reply from 208.95.184.201: bytes=32 time=76ms TTL=46
Reply from 208.95.184.201: bytes=32 time=69ms TTL=46
Ping statistics for 208.95.184.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 115ms, Average = 87ms
> So, the consensus seems to be that this is an internet connectivity issue that neither players nor Cryptic can do anything about -- except maybe call your ISP and ask them to talk to their upstream connections.
That does indeed seem to be the consensus. Specifically it seems like a Verizon router at alter.net is the issue. If you google Verizon and alter.net it seems they’ve used tactics of diliberately over congesting that route before to discourage people from using streaming services since they owned a state in redbox. My wife’s Netflix show was playing fine though while this was going on for me.
You probably need to look elsewhere for the source of your problems. Try run a full scan of the game files, or even reinstalling game, for a start. You could also make sure you have the latest driver from the graphics chip developer.
And if you reinstall game, make sure to do that to an empty directory, the point of the exercise being to refresh any old config/status files that could be bugged.