I'm having similar problems. It takes a while to check the patch, then lets me engage, the game loads, taking a bit longer than normal. It takes between 5 and 10 mins to load any character, usually just the one selected, longer if I click on another one to load. When it finally lets me select play, it takes about 1 - 2 mins showing me the loading screen background (no loading bar or anything, just the background picture) before I get the error message connection to the login server timed out. This has been going on for about a week now!! UK here, on Virgin.
having the same kind of issues, also with virgin in the UK, but from what I can ascertain, via pathping, tracert, nettest etc. it looks like cogentco.com are the culprits...
Guys when dealing with lag, unable to auth or login server issues posting information from http://sto-forum.perfectworld.com/showthread.php?t=225155 helps as with just saying "I cant connect" doesn't help diagnose any issues what so ever.
Yes, I'm that Askray@Batbayer in game. Yes, I still play. No, I don't care. Former Community Moderator, Former SSR DJ, Now Full time father to two kids, Husband, Retail Worker. Tiktok: @Askray Facebook: Askray113
Guys when dealing with lag, unable to auth or login server issues posting information from http://sto-forum.perfectworld.com/showthread.php?t=225155 helps as with just saying "I cant connect" doesn't help diagnose any issues what so ever.
Aren't you the same guy that blew everyone off last time when the big crash occurred on 3/21?
I'll post over there like you suggest but in the meantime, any chance you can use your pull with the powers that be and notify them of the problem before we experience another 3/21?
Delayed or dropped logins and dropped connections have been happening to me as well.
There is a known issue with Verizon throttling data to/from Cogent (the ISP that STO uses)
due to Netflix/Youtube traffic that could be causing this. Every so often, Verizon throttles
the data so much that connections to STO are just not possible. That may be the case here.
So I need to ask, How many of you having connection problems are Verizon customers?
I use Verizon, and I'm experiencing this.
Edit: Also from Texas.
Guys when dealing with lag, unable to auth or login server issues posting information from http://sto-forum.perfectworld.com/showthread.php?t=225155 helps as with just saying "I cant connect" doesn't help diagnose any issues what so ever.
Yep, done all that, tracert all good, nettest all good, any chance you can send someone round to the cogentco.com premises and sort out their servers? or at least give em a call, as they are throttling the life out of the sto launcher, they seem to be the common denominator if you run a pathping.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 10 ms 142.254.214.69
3 10 ms 8 ms 10 ms gi5-2-22-cmts.jmtwnyba-rtr001.cny.northeast.rr.c
om [24.94.32.167]
4 14 ms 16 ms 13 ms ae9.ithcnycy-rtr001.cny.northeast.rr.com [74.74.
108.90]
5 32 ms 32 ms 36 ms rdc-74-74-108-116.cny.east.twcable.com [74.74.10
8.116]
6 33 ms 31 ms 33 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 30 ms 30 ms 30 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
8 34 ms 32 ms 31 ms te0-3-0-27.ccr21.ord03.atlas.cogentco.com [154.5
4.11.145]
9 31 ms 30 ms 31 ms be2003.ccr42.ord01.atlas.cogentco.com [154.54.29
.21]
10 46 ms 46 ms 46 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
.202]
11 69 ms 45 ms 44 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 54 ms 54 ms 53 ms 38.111.40.114
13 49 ms 56 ms 49 ms patchserver2.crypticstudios.com [208.95.185.41]
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=44ms TTL=50
Reply from 208.95.185.41: bytes=32 time=47ms TTL=50
Reply from 208.95.185.41: bytes=32 time=48ms TTL=50
Reply from 208.95.185.41: bytes=32 time=48ms TTL=50
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 48ms, Average = 46ms
Can you provide that info in the link askray provided (scroll to his post about 3 or 4 replies ahead of yours). I'm seeing hails all over the forums from people unable to log in. It would be great if cryptic acknowledged the hails and/or responded with some sort of information.
Can you provide that info in the link askray provided (scroll to his post about 3 or 4 replies ahead of yours). I'm seeing hails all over the forums from people unable to log in. It would be great if cryptic acknowledged the hails and/or responded with some sort of information.
Yes in Texas here as well, and using Verizon DSL as well. Yesterday played till about 2pm my time, took a couple hour break came back and it was screwed up. Even went so far as to RE-INSTALL the damned game, and the same thing. Characters not loading, dropping on changing locations, and now that Error -118 on the launcher.
yea, whats the deal just started playing................ havent been able to log in since yesterday about 1700 CST. love the game so far and jsut started, but jeeeezzz been out a long time to have login issues.
ima Texas verizon user too...................hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
2 mins after i posted this it did start working, but i had uninstalled so now its patching............ and continuingly locking up.........
After days of too'ing and fro'ing between cryptic tech support and the quite useless virgin media UK tech support, the common denominator I have found is cogent communications, when you do a path ping to the cryptic patch servers where you patch/login etc. no packets of info are getting past atlas.cogentco.com.
I know of two isp's so far that route their traffic through their servers one is Verizon and the other is Virgin media UK.
Having failed miserably at pathing my traffic round cogentco to bypass this roadblock, I have reluctantly come to the conclusion that either I have to change my isp which is a pain, or use a virtual private network such as WTFast which solved my patch/login issues.
WTFast do a 30 day free trial, so you lose nothing by giving them a try to see if it sorts out your problem, if it doesn't, no harm no foul, and uninstall it.
Also getting many timeouts and rubber-banding effects. Just refreshed my PC on Friday to it should be completely clean now. Ping is showing some data loss. I am from Eastern Canada.
yea, whats the deal just started playing................ havent been able to log in since yesterday about 1700 CST. love the game so far and jsut started, but jeeeezzz been out a long time to have login issues.
ima Texas verizon user too...................hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
2 mins after i posted this it did start working, but i had uninstalled so now its patching............ and continuingly locking up.........
It appears that their are network issues. I KNOW if it frustrating but hope you will stay with it. This is really quite an awesome game
Not seeing any issues with the launcher here, but I am getting "Server Not Responding" for about 20s then a disconnect. I can log right back in, but all too often it will immediately go back to "Server Not Responding" and dump me back out within 1-5 minutes. It's made the game nigh-unplayable.
The primary ISP I use is coming through Time Warner Business Class, and even they are being routed through Cogent. Oddly enough, if I switch to my Verizon wifi hotspot, I get a clean connection - no lag, no rubberbanding, no disconnects.
What's even stranger is that the TWC network through the hotel I'm in looks completely clean, even after multiple Traceroute/Nettest runs. Prior to the Thursday patch, I'd been playing using that network for several months without issues, and I'm not having issues to any other game. Definitely looks like something server-side to me.
Traceroute (TWC):
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 2 ms 2 ms rrcs-50-84-159-105.sw.biz.rr.com [50.84.159.105]
3 7 ms 7 ms 7 ms RTR97-77-0-130.tx.twcbiz.com [97.77.0.130]
4 9 ms 11 ms 11 ms tge0-9-0-2.plantxmp02r.texas.rr.com [24.175.50.1
36]
5 10 ms 11 ms 12 ms agg27.dllbtxlb02r.texas.rr.com [24.175.36.184]
6 9 ms 7 ms 11 ms agg21.hstqtxl301r.texas.rr.com [24.175.49.8]
7 9 ms 10 ms 7 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
8 9 ms 11 ms 11 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
9 7 ms 7 ms 7 ms ae1.pr1.dfw10.tbone.rr.com [107.14.17.234]
10 8 ms 8 ms 8 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
11 8 ms 8 ms 8 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
12 18 ms 18 ms 18 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.
157]
13 30 ms 30 ms 30 ms be2159.ccr42.ord01.atlas.cogentco.com [154.54.24
.82]
14 58 ms 58 ms 57 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
.202]
15 57 ms 58 ms 60 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
16 55 ms 52 ms 53 ms 38.111.40.114
17 51 ms 51 ms 50 ms patchserver2.crypticstudios.com [208.95.185.41]
Not seeing any issues with the launcher here, but I am getting "Server Not Responding" for about 20s then a disconnect. I can log right back in, but all too often it will immediately go back to "Server Not Responding" and dump me back out within 1-5 minutes. It's made the game nigh-unplayable.
The primary ISP I use is coming through Time Warner Business Class, and even they are being routed through Cogent. Oddly enough, if I switch to my Verizon wifi hotspot, I get a clean connection - no lag, no rubberbanding, no disconnects.
What's even stranger is that the TWC network through the hotel I'm in looks completely clean, even after multiple Traceroute/Nettest runs. Prior to the Thursday patch, I'd been playing using that network for several months without issues, and I'm not having issues to any other game. Definitely looks like something server-side to me.
C:\WINDOWS\SYSTEM32>pathping 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
It's pretty evident from this that something is up with Cogent, or server-side on Cryptic's systems, or some combination of both.
The 'Path Ping' confirms that you have a connection quality issue that shows up in the 'Net Test' results, but...
You shouldn't be getting a 2% Packet drop on ALL the nodes of your connection, even before the packets hit your router. Its almost as if theirs a loose connection on your Ethernet cable, or your network interface is starting to go bad... You might have to call your ISP Tech Support and have them send someone to find out what is causing this, as results scream HARDWARE ISSUE of some kind...
The 'Path Ping' confirms that you have a connection quality issue that shows up in the 'Net Test' results, but...
You shouldn't be getting a 2% Packet drop on ALL the nodes of your connection, even before the packets hit your router. Its almost as if theirs a loose connection on your Ethernet cable, or your network interface is starting to go bad... You might have to call your ISP Tech Support and have them send someone to find out what is causing this, as results scream HARDWARE ISSUE of some kind...
Normally I'd agree... especially since I'm on hotel wifi at the moment, but I don't really have issues with any other game or service. Netflix goes for hours without a hiccup, as does Diablo III and The Secret World. If it was a hardware issue, then the problem would be pandemic to all connections.
That said, I have tested using a mobile hotspot on Verizon, and that behaves in a rock-solid fashion. Could very well be something with the hotel net, or even TWC side. I have some memory of issues with them when I was on them in the Austin, TX area, and being in Dallas now, I'm in the same general 'neighborhood,' so to speak.
No issues using ComCast at home in MI, either. In fact, I wasn't having issues at all until last Thursday's patch went live. A friend of mine in St. Louis has also reported the exact same problem, both with STO and Champions Online.
Seems like there could be a lot of variables to this puzzle. I'll keep testing and post any findings here.
For comparison, here's the tracert coming over the Verizon hotspot. Note that I do not have any problems on this network (aside from the obvious metered bandwidth, but nothing I can do about that), and I think a significant difference is that this way, I am not coming across Cogent's network:
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 25 ms 39 ms 39 ms 145.sub-66-174-43.myvzw.com [66.174.43.145]
2 45 ms 32 ms 38 ms 49.sub-69-83-107.myvzw.com [69.83.107.49]
3 36 ms 48 ms 29 ms 2.sub-69-83-107.myvzw.com [69.83.107.2]
4 49 ms 38 ms 35 ms 104.sub-69-83-96.myvzw.com [69.83.96.104]
5 * * * Request timed out.
6 44 ms 47 ms 32 ms 69.sub-69-83-96.myvzw.com [69.83.96.69]
7 45 ms 31 ms 40 ms TenGigE0-0-2-0.GW15.DFW9.ALTER.NET [152.179.167.
185]
8 79 ms 79 ms 79 ms 0.ae2.XL3.BOS4.ALTER.NET [140.222.226.17]
9 81 ms 78 ms 78 ms 0.xe-8-3-0.GW15.BOS4.ALTER.NET [152.63.24.38]
10 77 ms 79 ms 87 ms internap-gw.customer.alter.net [152.179.134.214]
11 91 ms 79 ms 77 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
12 81 ms 88 ms 72 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
13 75 ms 79 ms 82 ms 208.95.186.32
Trace complete.
PathPing doesn't get past Hop 5 due to Verizon's firewall, seems like. Whatever it is, Hop 5 definitely isn't responding to ICMP.
Sure, there may be something wrong with the hotel network... but reading through other posts on this and other threads, there definitely seems to be a correlation with lag, rubberbanding, and disconnect issues and Cogent.
Whatevers going on, its petty much now locked me out. I had terrible problems logging in but could at times do it. Last few days, its a write off and I'm always getting timed out of logins. All since the Thursday patch.
Had an update from support for this issue. Having gone through several weeks worth of back and forth to solve this issue, something, finally, seems to have worked. They recommended that I use the US proxy server. Once the launcher opened, I went to options, unticked the On-Demand Patching box and selected to use the US proxy (I think it's a drop down box under Use a Proxy Server, you have a choice, US or EU.) I don't know about the EU server, but the US server has allowed me to get into the game and removed any stability issues.I did have to wait whilst it patched the game, took about an hour and a half - two hours. Hopefully this will help others get back into the game!
Comments
Unable to authenticate over and over and over again
Former Community Moderator, Former SSR DJ, Now Full time father to two kids, Husband, Retail Worker.
Tiktok: @Askray Facebook: Askray113
Aren't you the same guy that blew everyone off last time when the big crash occurred on 3/21?
I'll post over there like you suggest but in the meantime, any chance you can use your pull with the powers that be and notify them of the problem before we experience another 3/21?
I use Verizon, and I'm experiencing this.
Edit: Also from Texas.
Yep, done all that, tracert all good, nettest all good, any chance you can send someone round to the cogentco.com premises and sort out their servers? or at least give em a call, as they are throttling the life out of the sto launcher, they seem to be the common denominator if you run a pathping.
Thank you.
---and to the moderator dude, I apologize. I re-read my post and that sounded terse. Not at all how I meant it. Live long and prosper, cowpokes!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 10 ms 142.254.214.69
3 10 ms 8 ms 10 ms gi5-2-22-cmts.jmtwnyba-rtr001.cny.northeast.rr.c
om [24.94.32.167]
4 14 ms 16 ms 13 ms ae9.ithcnycy-rtr001.cny.northeast.rr.com [74.74.
108.90]
5 32 ms 32 ms 36 ms rdc-74-74-108-116.cny.east.twcable.com [74.74.10
8.116]
6 33 ms 31 ms 33 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 30 ms 30 ms 30 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
8 34 ms 32 ms 31 ms te0-3-0-27.ccr21.ord03.atlas.cogentco.com [154.5
4.11.145]
9 31 ms 30 ms 31 ms be2003.ccr42.ord01.atlas.cogentco.com [154.54.29
.21]
10 46 ms 46 ms 46 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
.202]
11 69 ms 45 ms 44 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 54 ms 54 ms 53 ms 38.111.40.114
13 49 ms 56 ms 49 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=44ms TTL=50
Reply from 208.95.185.41: bytes=32 time=47ms TTL=50
Reply from 208.95.185.41: bytes=32 time=48ms TTL=50
Reply from 208.95.185.41: bytes=32 time=48ms TTL=50
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 48ms, Average = 46ms
Can you provide that info in the link askray provided (scroll to his post about 3 or 4 replies ahead of yours). I'm seeing hails all over the forums from people unable to log in. It would be great if cryptic acknowledged the hails and/or responded with some sort of information.
k, I re-posted what i said in the link ( http://sto-forum.perfectworld.com/sh...d.php?t=225155 ) askray posted. I hope i heard you right, if not im going to feel like a ditz lol
scratch scratch scratch
Be well.
I know how you feel lol Im getting behind on my Dilithium grind and my undine Rep. Im going to be behind one day and its driving me nuts lol
ima Texas verizon user too...................hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
2 mins after i posted this it did start working, but i had uninstalled so now its patching............ and continuingly locking up.........
I know of two isp's so far that route their traffic through their servers one is Verizon and the other is Virgin media UK.
Having failed miserably at pathing my traffic round cogentco to bypass this roadblock, I have reluctantly come to the conclusion that either I have to change my isp which is a pain, or use a virtual private network such as WTFast which solved my patch/login issues.
WTFast do a 30 day free trial, so you lose nothing by giving them a try to see if it sorts out your problem, if it doesn't, no harm no foul, and uninstall it.
GL
The primary ISP I use is coming through Time Warner Business Class, and even they are being routed through Cogent. Oddly enough, if I switch to my Verizon wifi hotspot, I get a clean connection - no lag, no rubberbanding, no disconnects.
What's even stranger is that the TWC network through the hotel I'm in looks completely clean, even after multiple Traceroute/Nettest runs. Prior to the Thursday patch, I'd been playing using that network for several months without issues, and I'm not having issues to any other game. Definitely looks like something server-side to me.
Traceroute (TWC):
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 2 ms 2 ms rrcs-50-84-159-105.sw.biz.rr.com [50.84.159.105]
3 7 ms 7 ms 7 ms RTR97-77-0-130.tx.twcbiz.com [97.77.0.130]
4 9 ms 11 ms 11 ms tge0-9-0-2.plantxmp02r.texas.rr.com [24.175.50.1
36]
5 10 ms 11 ms 12 ms agg27.dllbtxlb02r.texas.rr.com [24.175.36.184]
6 9 ms 7 ms 11 ms agg21.hstqtxl301r.texas.rr.com [24.175.49.8]
7 9 ms 10 ms 7 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
8 9 ms 11 ms 11 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
9 7 ms 7 ms 7 ms ae1.pr1.dfw10.tbone.rr.com [107.14.17.234]
10 8 ms 8 ms 8 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
11 8 ms 8 ms 8 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
12 18 ms 18 ms 18 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.
157]
13 30 ms 30 ms 30 ms be2159.ccr42.ord01.atlas.cogentco.com [154.54.24
.82]
14 58 ms 58 ms 57 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
.202]
15 57 ms 58 ms 60 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
16 55 ms 52 ms 53 ms 38.111.40.114
17 51 ms 51 ms 50 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
NetTest (TWC):
contacting nettest server..
Local IP: 50.84.159.106
Ping: 50.9 msec
Port: 80: 1350 KB/sec 45 KB/sec 1432 KB/sec 500
Port: 80: 461 KB/sec 22 KB/sec 493 KB/sec 500
Port: 443: 1352 KB/sec 45 KB/sec 1433 KB/sec 500
Port: 443: 944 KB/sec 44 KB/sec 1110 KB/sec 500
Port: 7255: 1362 KB/sec 45 KB/sec 1446 KB/sec 500
Port: 7255: 1349 KB/sec 44 KB/sec 1433 KB/sec 500
Port: 7003: 1356 KB/sec 45 KB/sec 1442 KB/sec 500
Port: 7003: 1352 KB/sec 46 KB/sec 1446 KB/sec 500
Port: 7202: 208 KB/sec 8 KB/sec 224 KB/sec 500
Port: 7202: 681 KB/sec 28 KB/sec 758 KB/sec 500
Port: 7499: 1348 KB/sec 44 KB/sec 1430 KB/sec 500
Port: 7499: 1436 KB/sec 50 KB/sec 1524 KB/sec 500
Port: 80: 1352 KB/sec 45 KB/sec 1434 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
==============
Edited to add a pathping to the login server:
C:\WINDOWS\SYSTEM32>pathping 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
0 TARDIS [192.168.1.TRIBBLE]
1 192.168.1.1
2 rrcs-50-84-159-105.sw.biz.rr.com [50.84.159.105]
3 RTR97-77-0-130.tx.twcbiz.com [97.77.0.130]
4 tge0-9-0-2.plantxmp02r.texas.rr.com [24.175.50.136]
5 agg27.dllbtxlb02r.texas.rr.com [24.175.36.184]
6 agg21.hstqtxl301r.texas.rr.com [24.175.49.8]
7 ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
8 ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
9 * 107.14.19.97
10 te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
11 be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
12 be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.113]
13 be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
14 be2137.ccr21.bos01.atlas.cogentco.com [154.54.43.194]
15 te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
16 38.111.40.114
17 208.95.186.32
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 TARDIS [192.168.1.TRIBBLE]
2/ 100 = 2% |
1 0ms 2/ 100 = 2% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 2ms 2/ 100 = 2% 0/ 100 = 0% rrcs-50-84-159-105.sw.biz.rr.com [50.84.159.105]
0/ 100 = 0% |
3 1ms 2/ 100 = 2% 0/ 100 = 0% RTR97-77-0-130.tx.twcbiz.com [97.77.0.130]
0/ 100 = 0% |
4 3ms 2/ 100 = 2% 0/ 100 = 0% tge0-9-0-2.plantxmp02r.texas.rr.com [24.175.50.136]
0/ 100 = 0% |
5 4ms 2/ 100 = 2% 0/ 100 = 0% agg27.dllbtxlb02r.texas.rr.com [24.175.36.184]
0/ 100 = 0% |
6 9ms 2/ 100 = 2% 0/ 100 = 0% agg21.hstqtxl301r.texas.rr.com [24.175.49.8]
0/ 100 = 0% |
7 9ms 2/ 100 = 2% 0/ 100 = 0% ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
0/ 100 = 0% |
8 11ms 3/ 100 = 3% 1/ 100 = 1% ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
0/ 100 = 0% |
9 12ms 3/ 100 = 3% 1/ 100 = 1% 107.14.19.97
0/ 100 = 0% |
10 8ms 3/ 100 = 3% 1/ 100 = 1% te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
0/ 100 = 0% |
11 --- 100/ 100 =100% 98/ 100 = 98% be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
0/ 100 = 0% |
12 --- 100/ 100 =100% 98/ 100 = 98% be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.113]
0/ 100 = 0% |
13 --- 100/ 100 =100% 98/ 100 = 98% be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
0/ 100 = 0% |
14 58ms 3/ 100 = 3% 1/ 100 = 1% be2137.ccr21.bos01.atlas.cogentco.com [154.54.43.194]
0/ 100 = 0% |
15 80ms 2/ 100 = 2% 0/ 100 = 0% te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
0/ 100 = 0% |
16 56ms 2/ 100 = 2% 0/ 100 = 0% 38.111.40.114
0/ 100 = 0% |
17 50ms 2/ 100 = 2% 0/ 100 = 0% 208.95.186.32
Trace complete.
It's pretty evident from this that something is up with Cogent, or server-side on Cryptic's systems, or some combination of both.
The 'Path Ping' confirms that you have a connection quality issue that shows up in the 'Net Test' results, but...
You shouldn't be getting a 2% Packet drop on ALL the nodes of your connection, even before the packets hit your router. Its almost as if theirs a loose connection on your Ethernet cable, or your network interface is starting to go bad... You might have to call your ISP Tech Support and have them send someone to find out what is causing this, as results scream HARDWARE ISSUE of some kind...
Normally I'd agree... especially since I'm on hotel wifi at the moment, but I don't really have issues with any other game or service. Netflix goes for hours without a hiccup, as does Diablo III and The Secret World. If it was a hardware issue, then the problem would be pandemic to all connections.
That said, I have tested using a mobile hotspot on Verizon, and that behaves in a rock-solid fashion. Could very well be something with the hotel net, or even TWC side. I have some memory of issues with them when I was on them in the Austin, TX area, and being in Dallas now, I'm in the same general 'neighborhood,' so to speak.
No issues using ComCast at home in MI, either. In fact, I wasn't having issues at all until last Thursday's patch went live. A friend of mine in St. Louis has also reported the exact same problem, both with STO and Champions Online.
Seems like there could be a lot of variables to this puzzle. I'll keep testing and post any findings here.
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 25 ms 39 ms 39 ms 145.sub-66-174-43.myvzw.com [66.174.43.145]
2 45 ms 32 ms 38 ms 49.sub-69-83-107.myvzw.com [69.83.107.49]
3 36 ms 48 ms 29 ms 2.sub-69-83-107.myvzw.com [69.83.107.2]
4 49 ms 38 ms 35 ms 104.sub-69-83-96.myvzw.com [69.83.96.104]
5 * * * Request timed out.
6 44 ms 47 ms 32 ms 69.sub-69-83-96.myvzw.com [69.83.96.69]
7 45 ms 31 ms 40 ms TenGigE0-0-2-0.GW15.DFW9.ALTER.NET [152.179.167.
185]
8 79 ms 79 ms 79 ms 0.ae2.XL3.BOS4.ALTER.NET [140.222.226.17]
9 81 ms 78 ms 78 ms 0.xe-8-3-0.GW15.BOS4.ALTER.NET [152.63.24.38]
10 77 ms 79 ms 87 ms internap-gw.customer.alter.net [152.179.134.214]
11 91 ms 79 ms 77 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
12 81 ms 88 ms 72 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
13 75 ms 79 ms 82 ms 208.95.186.32
Trace complete.
PathPing doesn't get past Hop 5 due to Verizon's firewall, seems like. Whatever it is, Hop 5 definitely isn't responding to ICMP.
Sure, there may be something wrong with the hotel network... but reading through other posts on this and other threads, there definitely seems to be a correlation with lag, rubberbanding, and disconnect issues and Cogent.