This is the a very similar symptom to was exhibited by the people from Europe / UK.
Switching to my path to that same system, I've noticed what I think is a shift in Cogent's network in San Diego. I don't remember the route happening like this:
>tracert battless47.evony.com
Tracing route to battless47.evony.com [64.156.194.60]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
6 58 ms 57 ms 66 ms te0-2-0-5.ccr22.dca01.atlas.cogentco.com [154.54.41.117]
7 56 ms 58 ms 65 ms te0-1-0-2.ccr22.atl01.atlas.cogentco.com [154.54.28.229]
8 58 ms 57 ms 58 ms te0-3-0-2.ccr22.iah01.atlas.cogentco.com [66.28.4.90]
9 142 ms 220 ms 204 ms te3-1.ccr01.sat01.atlas.cogentco.com [154.54.27.114]
10 87 ms 88 ms 88 ms te7-2.ccr01.phx02.atlas.cogentco.com [154.54.40.161]
11 87 ms 88 ms 88 ms te3-1.ccr01.san01.atlas.cogentco.com [154.54.27.109]
12 88 ms 87 ms 88 ms te4-2.ccr01.san03.atlas.cogentco.com [154.54.82.70] Don't remember a second hop in San Diego
13 107 ms 97 ms 98 ms multi-use.cogentco.com [66.250.11.38] Eh???
14 86 ms 88 ms 87 ms 38.96.10.250
15 77 ms 80 ms 79 ms m00022-sd.evony.com [64.156.194.60]
Trace complete.
I also had severe issues getting the forum to work with letting the routing go to the normal DNS entry for bbs.evony.com, which routes to San Diego, so I am posting this routed through Issaquah, Washington.
With what you posted, combined with what I think is some difference in routing in Cogent's network in San Diego, along with the forum problem, my first opinion on this is that M5 Hosting (the data center in San Diego) has been doing some network maintenance, and something is not set up appropriately by someone in San Diego. Now, I'm not sure if that's M5, or, in your case, Cable and Wireless (the CWIE hop before the timeouts).
I'm going to flip back over to the normal DNS for bbs.evony.com and see if things are better now.
Edit: Yes, things are working better through the normal San Diego DNS address.



Bookmarks