Quod nos non interficit, nos fortiores facitrnrn
(\__/)
(='.'=)This is Bunny. Copy and paste bunny into your
(")_(")signature to help him gain world domination.
It was round 17.00 server time yesterday when lot of people on ss59 (cannot be sure that all, but a lot) got booted and we were not able to get in for some time. I was attacking, trying to time attacks, so I got screwed up as I could not get there the rest of waves in time by timing them and had to recall.
For 30-60 minutes yesterday, the San Diego data center had some sort of issue. A trace looked like this:
>tracert www.evony.com
Tracing route to www.evony.com [64.156.194.17]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
.
.
.
6 21 ms 26 ms 23 ms te0-3-0-5.ccr22.dca01.atlas.cogentco.com [154.54.7.161]
7 52 ms 51 ms 51 ms te0-2-0-6.ccr22.atl01.atlas.cogentco.com [154.54.1.121]
8 53 ms 51 ms 49 ms te0-0-0-1.ccr22.iah01.atlas.cogentco.com [154.54.5.94]
9 56 ms 55 ms 53 ms te3-1.ccr01.sat01.atlas.cogentco.com [154.54.27.114]
10 83 ms 84 ms 97 ms te7-1.ccr01.phx02.atlas.cogentco.com [154.54.6.249]
11 88 ms 89 ms 88 ms te4-1.ccr01.san01.atlas.cogentco.com [154.54.7.86]
12 84 ms 83 ms 84 ms vl3506.na21.b006590-1.san01.atlas.cogentco.com [66.28.67.70]
13 89 ms 89 ms 90 ms 38.96.10.250
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
...
Normally it looks like this:
>tracert www.evony.com
Tracing route to www.evony.com [64.156.194.17]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.1
.
.
.
6 27 ms 19 ms 31 ms te0-3-0-5.ccr22.dca01.atlas.cogentco.com [154.54.7.161]
7 53 ms 53 ms 51 ms te0-2-0-6.ccr22.atl01.atlas.cogentco.com [154.54.1.121]
8 50 ms 49 ms 50 ms te0-0-0-1.ccr22.iah01.atlas.cogentco.com [154.54.5.94]
9 54 ms 56 ms 56 ms te3-1.ccr01.sat01.atlas.cogentco.com [154.54.27.114]
10 83 ms 83 ms 84 ms te7-1.ccr01.phx02.atlas.cogentco.com [154.54.6.249]
11 88 ms 87 ms 88 ms te4-1.ccr01.san01.atlas.cogentco.com [154.54.7.86]
12 85 ms 97 ms 83 ms vl3506.na21.b006590-1.san01.atlas.cogentco.com [66.28.67.70]
13 87 ms 87 ms 88 ms 38.96.10.250
14 82 ms 86 ms 85 ms m00002-sd.evony.com [64.156.194.17]
Trace complete.
Its regular occurance on SS60, has taken me up to 12 hrs sometimes to log back in after maintenence, only a couple of days a week can I get straight in after, this has been happening for a couple of months now......when it first started happening I reported it to be told it was my PC, since that time I have a new laptop, modem and router and its still happening, so obviously the problem is not at my end, also had quite a few folks in our alliance and others complaining of same thing.
I think that is a different issue - the one plaguing the Washington data center. What I saw happen yesterday would've kicked off everyone playing on San Diego hosted servers, and would've prevented logins, as the login server was unreachable. What happened yesterday was a shortened version of what happened when there was the game-wide outage and we got the outage compensation in June.
happens to me thou its at random times and can sign back on right after usually. i thought it was from inactivity since i noticed it when i would switch tabs for 10-20mins then come back to see it loged off but once when i was sending out farmers it happend so i guess its lag
Bookmarks