Some discoveries with respect to kiagsuva's situation...
The 64.156.194.8 IP that every server traces to would appear to be their central login server farm.
Once you go beyond that, you will be routed by the name-based routing that gets embedded with the HTTP request in the browser to the appropriate game server IP.
For example, logging into server 145 gives a connection to m00002-ad.evony.com currently clear over at IP 208.88.18.4.
Kiagsuva, if you're watching, a trace to that from your side would be good. I go through some interesting hops to get there from where I'm at:
Tracing route to m00002-ad.evony.com [208.88.18.4]
over a maximum of 30 hops:
6 104 ms 152 ms 108 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.4.182]
7 * * * Request timed out.
8 113 ms 111 ms 110 ms ge-1-3.r00.sttlwa01.us.ce.gin.ntt.net [198.104.202.114]
9 113 ms 115 ms 115 ms er6-1-0-25-6.issywa.adtaq.NET [66.228.208.43]
10 102 ms 102 ms 101 ms m00002-ad.evony.com [208.88.18.4]
Trace complete.
Logging into server 150, however, gives a connection to a different subnet. The name there is not listed in DNS, at IP 64.156.195.110.
Oddly enough, kiagsuva stated that they could log into 150, but not 145. However, in the other thread that was referenced, someone else stated that they can log into 146, but nothing else, and they too are a Primus user.
Logging into server 146 gives a connection to m00031-lw.evony.com at IP 64.156.195.80.
In both instances, a trace passes through an additional router that is not present for the 64.156.194.xxx IPs:
Tracing route to m00031-lw.evony.com [64.156.195.80]
over a maximum of 30 hops:
12 85 ms 85 ms 85 ms vl3506.na21.b006590-1.san01.atlas.cogentco.com [66.28.67.70]
13 89 ms 89 ms 88 ms 38.96.10.250
14 87 ms 85 ms 86 ms 38.96.14.246
15 85 ms 87 ms 87 ms m00031-lw.evony.com [64.156.195.80]
Trace complete.
It does not make sense that these random IPs would all be getting blocked by a local ISP. It makes a lot more sense to look a lot closer at Evony / colocation equipment, specifically at the devices at / around 38.96.10.250 and 38.96.14.246, and anything else in Evony's LAN or their colocation partner's LAN, to make sure they have their routing tables in proper working order.





Bookmarks