Well there's a few potential problems. Personally I would look on my machine, but for another slant, read below.
I think you'll get a lot more help if you stop saying things that aren't true. s144 is simply not down when you say it is for two reasons: (1) there would be quite a few more threads than just yours; and (2) I've been in it during the times you claim it's down without issue. So, let's eliminate the server being down a potential problem.
Here's something that might be part of your issue (might): Evony's hosting service peers with several providers:
ASN Name
174 COGENT-PSI-1
2828 XO-AS15
3356 LEVEL3
6130 AIS-WEST
6939 HURRICANE
9002 RETN-AS
19151WVFIBER-1
Their mix seems to heavily favor XO and Cogent. XO has had several peering disputes with large broadband operators (Comcast and TW being the largest). Cogent has had peering disputes with pretty much everyone on the planet. All of these disputes centered around the fact that XO and Cogent are host-heavy, so their traffic tends to be mostly outbound to their peering partners. As a result of these peering disputes, they both have really weird peering agreements and they both have lots of legacy rate limits hanging around with their peering partners that weren't correct when their peering disputes ended. This sometimes means that a connection to something hosted by an XO customer will work fine from your office, but when you try from your house between 7pm and 10pm you can't connect. Since there is still a rate limit from some long resolved fight between XO and someone upstream of your provider, traffic is sent to that peering connection but drops because the rate limit is fully saturated. This issue also might mean that 10 comcast connections in your area don't work or it works fine for 2hrs and then fails for 30mins over and over throughout the day.
Like I said, this might not be your problem, but I've personally worked on thousands of issues just like this and they are a dog to track down and resolve. Sometimes it is someone upstream of the host that has to isolate the issue. Sometimes it is someone upstream of the end user's connection.
Nevertheless, though, there are a million and one variables between you and evony. Add to that the fact that there could be something on your system....some obscure Windows 7 file that got horked in the last update maybe....that could be causing the issue. Nonetheless, despite all these thousands of "could be" issues, we can safely say that:
1.) Evony's servers are not down dozens of time a day; and
2.) There is no magic button at Evony that will fix this issue for you. There's a 99% chance that there's nothing Evony can do locally that will even help.
One thing I might recommend would be to first try and run a ping (say 500 samples) when the connection is working. Later on, when you connection fails, try that ping again. Once you have your ping data, run a traceroute to s144.evony.com. Keep doing that while the connection is failing and look for a dropped packet or a big amount of latency between hops. If you can isolate that, you'll know where you are having problems and can direct that information to your provider.
Anyway, good luck with your issue.





Bookmarks