Quote Originally Posted by Jasarius View Post
20 98 ms 97 ms 98 ms CWIE-LLC.hsa1.SanDiego1.Level3.net [4.79.33.230]

21 97 ms 98 ms 97 ms m00022-sd.evony.com [64.156.194.60]

Trace complete.


Anything you can tell on how to possibly fix this for the next time (because knowing Evony, there WILL be a next time
There's nothing you can do to correct the issue, other than use a different ISP or a proxy server.

The problem was located in San Diego or the surrounding area, which is a nice area, I've been once...started out the night with a meal at Casa de Bandini (now closed and moved to another location), then some drinks at Rock Bottom, and finishing getting drunk at The Tipsy Crow, which at that time was called The Bitter End, all in the Gaslamp Quarter...

At any rate, either Cable and Wireless had a misconfiguration, or M5 Hosting (the data center provider there) had a misconfiguration, and your traffic was blocked. The only thing that you can do to get around this is attempt to connect through a different ISP that either uses a different route or does not have its' traffic blocked, or use a proxy server, which has the same general effect, but has security ramifications.

Beyond that, you could've done the ole' FFR (FDISK, Format, Reinstall), and you would've still had a problem, because the problem existed beyond the point where you or your individual ISP has control.

Also, it is not technically a problem with Evony's server, as the server was still up and operational. It was however a problem with a pathway to reach the server. This is where I stand firm on the responsibilities of the various parties involved, which is not understood and/or not liked. I won't dwell on it too much, since this issue is no longer impacting you, but basically the general gist of what I'm trying to get across is that there needs to be a more cooperative environment, where the location of the failure is attempted to be isolated, and then the proper responsible party takes action.

Clearly you cannot demand that Cable and Wireless fix an issue when you are not a customer of them, and the issue is thousands of miles away from you. The same thing goes for M5 hosting. You are not their customer.

Anyway, glad to see that the issue was corrected by whoever it was that corrected it in San Diego.