The game itself has a traceroute built in, so I can trace the results to each zone within that server address. The traced route to the specific zone IP and port, shows 20ms average with 40ms high. It only shows 10 total hops, but it shows the same exact number of hops and average ping to each of the other zones. By all accounts, the only difference is I can get into zone 1 and zone 2, which are on different ports, but the same IP and I can't get into zone 3, which is on port 13500. I was told the packet types are TCP and UDP, but I would imagine there's really no difference in packets sent/received in the other zones, within the same game.

It seems like the problem is definitely in the port being used, somehow, whether it's traffic is being blocked or not. Unfortunately, I'm not sure how to remedy that. I have been told that other people experienced similar issues, only to have the issue simply resolve itself randomly. That led me to believe it has something to do with the IP and when it's released and renewed. Since I'm connecting through a router, I can see my WAN IP won't be "released" for another 2 days. I tried to use a service to run a different IP number, to see if it would work, but it actually made ONLY that zone, unavailable. With that service, P2P and torrent traffic is blocked, but otherwise it shouldn't have been an issue. With the other IP, every other zone was available, only the one running on port 13500 was shown in "red" indicating it was unavailable.