FWIW (and probably not much), I'm running a MacBook Pro, and I use Boot Camp for Windows, and I tried the same thing through OS X, and got the same result ("You may not log in from this IP address") Not sure how to run a tracert in OS X, or if it would even make a difference...
on a mac you would open Terminal.app and then type:
on a mac you would open Terminal.app and then type:
traceroute -I patchserver.crypticstudios.com
Here's the trace route through OS X. Didn't seem to yield a different result than when I ran it through Windows. All the jumps look about the same.
traceroute -I patchserver.crypticstudios.com
traceroute to patchserver.crypticstudios.com (208.95.185.41), 64 hops max, 72 byte packets
1 10.14.192.1 (10.14.192.1) 13.661 ms 9.939 ms 19.749 ms
2 ip72-214-194-81.ga.at.cox.net (72.214.194.81) 10.463 ms 8.985 ms 8.009 ms
3 dalsbprj01-ae1.0.rd.dl.cox.net (68.1.2.109) 53.729 ms 45.720 ms 55.077 ms
4 68.105.30.22 (68.105.30.22) 33.964 ms 34.928 ms 33.213 ms
5 ae7.cr2.dfw2.us.zip.zayo.com (64.125.20.233) 33.910 ms 34.010 ms 34.047 ms
6 ae2.cr2.iah1.us.zip.zayo.com (64.125.21.62) 40.712 ms 39.105 ms 39.411 ms
7 ae14.cr2.dca2.us.zip.zayo.com (64.125.21.53) 51.236 ms 51.060 ms 51.675 ms
8 ae0.mpr4.bos2.us.zip.zayo.com (64.125.20.29) 74.678 ms 60.182 ms 60.433 ms
9 ae2.mpr3.bos2.us.zip.zayo.com (64.125.25.41) 59.022 ms 60.127 ms 61.833 ms
10 208.184.110.70.ipyx-072053-002-zyo.above.net (208.184.110.70) 60.075 ms 60.153 ms 60.378 ms
11 border11.te8-1-bbnet2.bsn.pnap.net (63.251.128.104) 60.372 ms 58.927 ms 60.288 ms
12 perfectworldent-4.border11.bsn.pnap.net (216.52.61.78) 67.141 ms 67.043 ms 70.318 ms
13 patchserver2.crypticstudios.com (208.95.185.41) 57.861 ms 62.326 ms 59.002 ms
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms READYSHARE [10.0.0.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 14 ms 13 ms 13 ms cpe-24-167-32-1.rgv.res.rr.com [24.167.32.1]
4 13 ms 24 ms 12 ms cpe-24-167-32-1.rgv.res.rr.com [24.167.32.1]
5 12 ms 14 ms 14 ms tge7-5.mssntx0802h.texas.rr.com [66.68.193.253]
6 27 ms 19 ms 18 ms tge0-8-0-3.hrlntxcb01r.texas.rr.com [24.175.56.128]
7 29 ms 27 ms 27 ms agg26.hstqtxl301r.texas.rr.com [24.175.56.74]
8 27 ms 23 ms 26 ms bu-ether46.hstqtx0209w-bcr00.tbone.rr.com [107.14.19.94]
9 35 ms 39 ms 47 ms bu-ether32.dllstx976iw-bcr00.tbone.rr.com [107.14.19.218]
10 29 ms 28 ms 25 ms 0.ae4.pr1.dfw10.tbone.rr.com [107.14.19.97]
11 32 ms 30 ms 27 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
12 37 ms 39 ms 28 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.53]
13 60 ms 37 ms 43 ms be2146.ccr22.iah01.atlas.cogentco.com [154.54.25.241]
14 44 ms 43 ms 44 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29.117]
15 65 ms 63 ms 64 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
16 85 ms 69 ms 143 ms be2151.ccr42.jfk02.atlas.cogentco.com [154.54.40.74]
17 83 ms 78 ms 74 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
18 74 ms 78 ms 79 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
19 96 ms 70 ms 71 ms 38.111.40.114
20 66 ms 63 ms 65 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
I don't know if this helps at all but my theory is that xboxpatchserver, and patchserver2 are being reserved for the XBOX One launch of NWO and have been accidentally linked to the accounts.crypticstudios.com or the PC client's account servers.
Just a theory... maybe we're all a part of a test to see if the servers are up and functional before the release of the XBOX client.
Or maybe the xboxpatchserver and patchserver2 have been prematurely booted.
I like many others can't log in, so I have a question. Since it's looking like I won't be able to log on today thus not being able to do the crystalline entity event daily, can we get a one day extension on it to compensate for today's login issue?
I don't know if this helps at all but my theory is that xboxpatchserver, and patchserver2 are being reserved for the XBOX One launch of NWO and have been accidentally linked to the accounts.crypticstudios.com or the PC client's account servers.
Just a theory... maybe we're all a part of a test to see if the servers are up and functional before the release of the XBOX client.
Or maybe the xboxpatchserver and patchserver2 have been prematurely booted.
they all point to the same IP so there are multiple reverse dns entries being returned by cryptic's authoritative nameserver for the 208.95.184.0/22 netblock for 208.95.185.41, which is generally a not a best practice. (while having multple PTR records for an IP is not prohibited by the RFC it's also an edge case that can lead to nondeterministic/undefined behavior).
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 * * * Request timed out.
3 7 ms 11 ms 7 ms acr01barbwi-tge-0-7-0-6.barb.wi.charter.com [96.
34.24.46]
4 17 ms 15 ms 15 ms crr01euclwi-tge-0-5-0-8.eucl.wi.charter.com [96.
34.17.47]
5 18 ms 15 ms 15 ms bbr01euclwi-bue-4.eucl.wi.charter.com [96.34.2.4
]
6 18 ms 15 ms 15 ms bbr02euclwi-bue-5.eucl.wi.charter.com [96.34.0.7
]
7 20 ms 22 ms 20 ms bbr01chcgil-bue-1.chcg.il.charter.com [96.34.0.9
]
8 18 ms 19 ms 23 ms bbr02chcgil-bue-6.chcg.il.charter.com [96.34.0.6
7]
9 27 ms 27 ms 25 ms te0-5-0-2.ccr21.ord03.atlas.cogentco.com [38.104
.102.233]
10 25 ms 24 ms 24 ms be2003.ccr42.ord01.atlas.cogentco.com [154.54.29
.21]
11 43 ms 32 ms 35 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43
.178]
12 46 ms 45 ms 45 ms be2189.ccr22.alb02.atlas.cogentco.com [154.54.43
.185]
13 47 ms 47 ms 48 ms be2302.ccr22.bos01.atlas.cogentco.com [154.54.43
.13]
14 48 ms 47 ms 47 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.130]
15 46 ms 54 ms 52 ms 38.111.40.114
16 47 ms 46 ms 45 ms patchserver2.crypticstudios.com [208.95.185.41]
Anything on this matter , thread is over 3 hours old and nothing on a timeframe or what is causing the problems or if it will be fixed anytime soon. Really enjoying the game and would like to know if there is a chance of getting back on tonight?
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 11 ms 12 ms 11 ms rc2nr-tge0-1-0-22-1.wp.shawcable.net [64.59.178.109]
3 60 ms 68 ms 61 ms 66.163.75.222
4 63 ms 61 ms 64 ms 66.163.64.2
5 57 ms 59 ms 60 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
6 67 ms 69 ms 61 ms ae6.cr1.dca2.us.zip.zayo.com [64.125.20.117]
7 68 ms 69 ms 79 ms ae5.cr1.lga5.us.zip.zayo.com [64.125.26.98]
8 70 ms 69 ms 70 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
9 71 ms 72 ms 68 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
10 69 ms 71 ms 67 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
11 83 ms 88 ms 69 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
12 62 ms 71 ms 62 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
We're seeing a trend on the NWO thread. It looks like a majority of the folks having issues have IP addresses that begin with 24.xx.xx.TRIBBLE. http://www.whatismyip.com/
We're seeing a trend on the NWO thread. It looks like a majority of the folks having issues have IP addresses that begin with 24.xx.xx.TRIBBLE. http://www.whatismyip.com/
Let's see if that trend continues here.
Mine is working fine, and ip starts with 68.xx.xx.xx, for what its worth.
traceroute to patchserver.crypticstudios.com (208.95.185.41), 64 hops max, 72 byte packets
1 10.0.1.1 (10.0.1.1) 1.328 ms 0.824 ms 0.683 ms
2 24.130.104.1 (24.130.104.1) 10.024 ms 9.690 ms 9.441 ms
3 te-0-4-0-13-sur04.rohnertpr.ca.sfba.comcast.net (68.87.198.109) 9.996 ms 10.027 ms 10.382 ms
4 te-0-7-0-23-sur03.rohnertpr.ca.sfba.comcast.net (69.139.198.225) 9.767 ms 9.516 ms 9.886 ms
5 te-1-0-0-3-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.2) 13.811 ms
te-1-0-0-2-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.234) 14.652 ms
te-1-0-0-1-ar01.sfsutro.ca.sfba.comcast.net (68.85.154.162) 12.877 ms
6 * * *
7 be-10910-cr01.sanjose.ca.ibone.comcast.net (68.86.86.102) 26.196 ms 13.141 ms 16.008 ms
8 be-26-pe02.529bryant.ca.ibone.comcast.net (68.86.86.66) 15.381 ms 14.642 ms 14.572 ms
9 50.248.118.238 (50.248.118.238) 13.960 ms 22.729 ms 13.993 ms
10 be2015.ccr21.sfo01.atlas.cogentco.com (154.54.7.173) 14.953 ms 15.201 ms 16.172 ms
11 be2132.ccr21.mci01.atlas.cogentco.com (154.54.30.54) 57.703 ms 58.681 ms 58.791 ms
12 be2156.ccr41.ord01.atlas.cogentco.com (154.54.6.86) 65.294 ms 64.062 ms 64.068 ms
13 be2351.ccr21.cle04.atlas.cogentco.com (154.54.44.86) 71.181 ms 72.262 ms 70.695 ms
14 be2009.ccr21.alb02.atlas.cogentco.com (154.54.25.89) 84.184 ms 91.991 ms 84.606 ms
15 be2299.ccr21.bos01.atlas.cogentco.com (154.54.43.9) 88.315 ms 88.116 ms 87.551 ms
16 te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com (154.54.46.134) 87.873 ms 88.437 ms 88.010 ms
17 38.111.40.114 (38.111.40.114) 96.527 ms 98.584 ms 89.278 ms
18 xboxpatchserver.crypticstudios.com (208.95.185.41) 87.109 ms 86.898 ms 86.358 ms
Anything on this matter , thread is over 3 hours old and nothing on a timeframe or what is causing the problems or if it will be fixed anytime soon. Really enjoying the game and would like to know if there is a chance of getting back on tonight?
Still trying to nail down a solution with my engineering team.
1 2 ms 3 ms 2 ms Dlink-Router.Dlink [192.168.0.1]
2 34 ms 31 ms 22 ms 10.95.255.254
3 108 ms 37 ms 56 ms ae0-439.bbr01.perm.ertelecom.ru [212.33.233.57]
4 52 ms 54 ms 53 ms ertelekom-ic-306585-sap-b2.c.telia.net [80.239.160.202]
5 36 ms 35 ms 30 ms sap-b2-link.telia.net [80.239.160.201]
6 46 ms 45 ms 43 ms s-bb3-link.telia.net [80.91.250.3]
7 83 ms 69 ms 60 ms kbn-bb3-link.telia.net [62.115.139.171]
8 136 ms 139 ms 209 ms nyk-bb1-link.telia.net [62.115.141.101]
9 144 ms 146 ms 145 ms bost-b1-link.telia.net [80.91.246.125]
10 230 ms 164 ms 154 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
11 159 ms 158 ms 168 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 157 ms 147 ms 165 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 167 ms 185 ms 178 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
... because your internet is down? lol, don't know if that was a trick question or something, but 0.0.0.0 means you don't have an ip address. If its NOT a trick question, I suppose you could have some security or something thats blocking the website from displaying it ... but that really doesn't make sense to me.
I cloned my other pc's mac for my router to get my ISP to issue a new IP addy.
My old IP was 107.147.253.41 (gave msg cant login from this ip), my New IP starts with a 97. and I can log in just fine. SE MI BHN
Thank you for the traceroutes everyone. The engineering team and web team is looking into them to see what they can figure out from the data.
Honestly though - it seems like a Cryptic game account server configuration issue in that something has either triggered a mass account ban; or somehow large IP ranges have in effect been blocked/blacklisted. I did provide a traceroute; but I honestly fail to see (since everyone with the issue can connect to the account server, and that server is denying/blocking Cryptic account login completion due to an unintended account ban, or an IP address block/ban.)
However, I assume the engineers asked for the data for a reason, and I hope they can find and correct the glitch.
Formerly known as Armsman from June 2008 to June 20, 2012 PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
Comments
It stands for "Virtual Private Network"
http://en.wikipedia.org/wiki/Virtual_private_network
[SIGPIC][/SIGPIC]
on a mac you would open Terminal.app and then type:
traceroute -I patchserver.crypticstudios.com
A VPN will work, if the VPN isn't effected, as that's basically like changing ISPs when it comes to an issue like this.
traceroute -I patchserver.crypticstudios.com
traceroute to patchserver.crypticstudios.com (208.95.185.41), 64 hops max, 72 byte packets
1 10.14.192.1 (10.14.192.1) 13.661 ms 9.939 ms 19.749 ms
2 ip72-214-194-81.ga.at.cox.net (72.214.194.81) 10.463 ms 8.985 ms 8.009 ms
3 dalsbprj01-ae1.0.rd.dl.cox.net (68.1.2.109) 53.729 ms 45.720 ms 55.077 ms
4 68.105.30.22 (68.105.30.22) 33.964 ms 34.928 ms 33.213 ms
5 ae7.cr2.dfw2.us.zip.zayo.com (64.125.20.233) 33.910 ms 34.010 ms 34.047 ms
6 ae2.cr2.iah1.us.zip.zayo.com (64.125.21.62) 40.712 ms 39.105 ms 39.411 ms
7 ae14.cr2.dca2.us.zip.zayo.com (64.125.21.53) 51.236 ms 51.060 ms 51.675 ms
8 ae0.mpr4.bos2.us.zip.zayo.com (64.125.20.29) 74.678 ms 60.182 ms 60.433 ms
9 ae2.mpr3.bos2.us.zip.zayo.com (64.125.25.41) 59.022 ms 60.127 ms 61.833 ms
10 208.184.110.70.ipyx-072053-002-zyo.above.net (208.184.110.70) 60.075 ms 60.153 ms 60.378 ms
11 border11.te8-1-bbnet2.bsn.pnap.net (63.251.128.104) 60.372 ms 58.927 ms 60.288 ms
12 perfectworldent-4.border11.bsn.pnap.net (216.52.61.78) 67.141 ms 67.043 ms 70.318 ms
13 patchserver2.crypticstudios.com (208.95.185.41) 57.861 ms 62.326 ms 59.002 ms
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 READYSHARE [10.0.0.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 14 ms 13 ms 13 ms cpe-24-167-32-1.rgv.res.rr.com [24.167.32.1]
4 13 ms 24 ms 12 ms cpe-24-167-32-1.rgv.res.rr.com [24.167.32.1]
5 12 ms 14 ms 14 ms tge7-5.mssntx0802h.texas.rr.com [66.68.193.253]
6 27 ms 19 ms 18 ms tge0-8-0-3.hrlntxcb01r.texas.rr.com [24.175.56.128]
7 29 ms 27 ms 27 ms agg26.hstqtxl301r.texas.rr.com [24.175.56.74]
8 27 ms 23 ms 26 ms bu-ether46.hstqtx0209w-bcr00.tbone.rr.com [107.14.19.94]
9 35 ms 39 ms 47 ms bu-ether32.dllstx976iw-bcr00.tbone.rr.com [107.14.19.218]
10 29 ms 28 ms 25 ms 0.ae4.pr1.dfw10.tbone.rr.com [107.14.19.97]
11 32 ms 30 ms 27 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
12 37 ms 39 ms 28 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.53]
13 60 ms 37 ms 43 ms be2146.ccr22.iah01.atlas.cogentco.com [154.54.25.241]
14 44 ms 43 ms 44 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29.117]
15 65 ms 63 ms 64 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
16 85 ms 69 ms 143 ms be2151.ccr42.jfk02.atlas.cogentco.com [154.54.40.74]
17 83 ms 78 ms 74 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
18 74 ms 78 ms 79 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
19 96 ms 70 ms 71 ms 38.111.40.114
20 66 ms 63 ms 65 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Trace complete.
xboxpatchserver.crypticstudios.com
patchserver2.crypticstudios.com
accounts.crypticstudios.com
I don't know if this helps at all but my theory is that xboxpatchserver, and patchserver2 are being reserved for the XBOX One launch of NWO and have been accidentally linked to the accounts.crypticstudios.com or the PC client's account servers.
Just a theory... maybe we're all a part of a test to see if the servers are up and functional before the release of the XBOX client.
Or maybe the xboxpatchserver and patchserver2 have been prematurely booted.
they all point to the same IP so there are multiple reverse dns entries being returned by cryptic's authoritative nameserver for the 208.95.184.0/22 netblock for 208.95.185.41, which is generally a not a best practice. (while having multple PTR records for an IP is not prohibited by the RFC it's also an edge case that can lead to nondeterministic/undefined behavior).
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 * * * Request timed out.
3 7 ms 11 ms 7 ms acr01barbwi-tge-0-7-0-6.barb.wi.charter.com [96.
34.24.46]
4 17 ms 15 ms 15 ms crr01euclwi-tge-0-5-0-8.eucl.wi.charter.com [96.
34.17.47]
5 18 ms 15 ms 15 ms bbr01euclwi-bue-4.eucl.wi.charter.com [96.34.2.4
]
6 18 ms 15 ms 15 ms bbr02euclwi-bue-5.eucl.wi.charter.com [96.34.0.7
]
7 20 ms 22 ms 20 ms bbr01chcgil-bue-1.chcg.il.charter.com [96.34.0.9
]
8 18 ms 19 ms 23 ms bbr02chcgil-bue-6.chcg.il.charter.com [96.34.0.6
7]
9 27 ms 27 ms 25 ms te0-5-0-2.ccr21.ord03.atlas.cogentco.com [38.104
.102.233]
10 25 ms 24 ms 24 ms be2003.ccr42.ord01.atlas.cogentco.com [154.54.29
.21]
11 43 ms 32 ms 35 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43
.178]
12 46 ms 45 ms 45 ms be2189.ccr22.alb02.atlas.cogentco.com [154.54.43
.185]
13 47 ms 47 ms 48 ms be2302.ccr22.bos01.atlas.cogentco.com [154.54.43
.13]
14 48 ms 47 ms 47 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.130]
15 46 ms 54 ms 52 ms 38.111.40.114
16 47 ms 46 ms 45 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
over a maximum of 30 hops:
1 * * * Request timed out.
2 11 ms 12 ms 11 ms rc2nr-tge0-1-0-22-1.wp.shawcable.net [64.59.178.109]
3 60 ms 68 ms 61 ms 66.163.75.222
4 63 ms 61 ms 64 ms 66.163.64.2
5 57 ms 59 ms 60 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
6 67 ms 69 ms 61 ms ae6.cr1.dca2.us.zip.zayo.com [64.125.20.117]
7 68 ms 69 ms 79 ms ae5.cr1.lga5.us.zip.zayo.com [64.125.26.98]
8 70 ms 69 ms 70 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
9 71 ms 72 ms 68 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
10 69 ms 71 ms 67 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
11 83 ms 88 ms 69 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
12 62 ms 71 ms 62 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Trace complete.
Let's see if that trend continues here.
Mine is working fine, and ip starts with 68.xx.xx.xx, for what its worth.
Well, thats 3 with 24.xx.xx.xx having issues, its still a small sample size but I think we may be onto something now.
1 10.0.1.1 (10.0.1.1) 1.328 ms 0.824 ms 0.683 ms
2 24.130.104.1 (24.130.104.1) 10.024 ms 9.690 ms 9.441 ms
3 te-0-4-0-13-sur04.rohnertpr.ca.sfba.comcast.net (68.87.198.109) 9.996 ms 10.027 ms 10.382 ms
4 te-0-7-0-23-sur03.rohnertpr.ca.sfba.comcast.net (69.139.198.225) 9.767 ms 9.516 ms 9.886 ms
5 te-1-0-0-3-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.2) 13.811 ms
te-1-0-0-2-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.234) 14.652 ms
te-1-0-0-1-ar01.sfsutro.ca.sfba.comcast.net (68.85.154.162) 12.877 ms
6 * * *
7 be-10910-cr01.sanjose.ca.ibone.comcast.net (68.86.86.102) 26.196 ms 13.141 ms 16.008 ms
8 be-26-pe02.529bryant.ca.ibone.comcast.net (68.86.86.66) 15.381 ms 14.642 ms 14.572 ms
9 50.248.118.238 (50.248.118.238) 13.960 ms 22.729 ms 13.993 ms
10 be2015.ccr21.sfo01.atlas.cogentco.com (154.54.7.173) 14.953 ms 15.201 ms 16.172 ms
11 be2132.ccr21.mci01.atlas.cogentco.com (154.54.30.54) 57.703 ms 58.681 ms 58.791 ms
12 be2156.ccr41.ord01.atlas.cogentco.com (154.54.6.86) 65.294 ms 64.062 ms 64.068 ms
13 be2351.ccr21.cle04.atlas.cogentco.com (154.54.44.86) 71.181 ms 72.262 ms 70.695 ms
14 be2009.ccr21.alb02.atlas.cogentco.com (154.54.25.89) 84.184 ms 91.991 ms 84.606 ms
15 be2299.ccr21.bos01.atlas.cogentco.com (154.54.43.9) 88.315 ms 88.116 ms 87.551 ms
16 te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com (154.54.46.134) 87.873 ms 88.437 ms 88.010 ms
17 38.111.40.114 (38.111.40.114) 96.527 ms 98.584 ms 89.278 ms
18 xboxpatchserver.crypticstudios.com (208.95.185.41) 87.109 ms 86.898 ms 86.358 ms
don't really understand any of this
2 34 ms 31 ms 22 ms 10.95.255.254
3 108 ms 37 ms 56 ms ae0-439.bbr01.perm.ertelecom.ru [212.33.233.57]
4 52 ms 54 ms 53 ms ertelekom-ic-306585-sap-b2.c.telia.net [80.239.160.202]
5 36 ms 35 ms 30 ms sap-b2-link.telia.net [80.239.160.201]
6 46 ms 45 ms 43 ms s-bb3-link.telia.net [80.91.250.3]
7 83 ms 69 ms 60 ms kbn-bb3-link.telia.net [62.115.139.171]
8 136 ms 139 ms 209 ms nyk-bb1-link.telia.net [62.115.141.101]
9 144 ms 146 ms 145 ms bost-b1-link.telia.net [80.91.246.125]
10 230 ms 164 ms 154 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
11 159 ms 158 ms 168 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 157 ms 147 ms 165 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 167 ms 185 ms 178 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
My IP is 46.146.29.TRIBBLE.
... because your internet is down? lol, don't know if that was a trick question or something, but 0.0.0.0 means you don't have an ip address. If its NOT a trick question, I suppose you could have some security or something thats blocking the website from displaying it ... but that really doesn't make sense to me.
My old IP was 107.147.253.41 (gave msg cant login from this ip), my New IP starts with a 97. and I can log in just fine. SE MI BHN
Honestly though - it seems like a Cryptic game account server configuration issue in that something has either triggered a mass account ban; or somehow large IP ranges have in effect been blocked/blacklisted. I did provide a traceroute; but I honestly fail to see (since everyone with the issue can connect to the account server, and that server is denying/blocking Cryptic account login completion due to an unintended account ban, or an IP address block/ban.)
However, I assume the engineers asked for the data for a reason, and I hope they can find and correct the glitch.
PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."