Okay, now that the servers are live, I've confirmed Balmung's IP to be 204.2.229.82 and here's my results from a ping and tracert which appears to confirm Sacramento:
Code:
C:\Users\#####>ping 204.2.229.82
Pinging 204.2.229.82 with 32 bytes of data:
Reply from 204.2.229.82: bytes=32 time=49ms TTL=53
Reply from 204.2.229.82: bytes=32 time=46ms TTL=53
Reply from 204.2.229.82: bytes=32 time=39ms TTL=53
Reply from 204.2.229.82: bytes=32 time=49ms TTL=53
Ping statistics for 204.2.229.82:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 49ms, Average = 45ms
C:\Users\#####>tracert 204.2.229.82
Tracing route to 204.2.229.82 over a maximum of 30 hops
1 3 ms 10 ms 8 ms 192.168.0.1
2 19 ms 14 ms 19 ms 24.86.64.1
3 16 ms 29 ms 63 ms rd3st-tge0-4-0-1-1.vc.shawcable.net [64.59.147.205]
4 104 ms 19 ms 24 ms rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
5 23 ms 26 ms 29 ms xe-0-5-0-17.r04.sttlwa01.us.bb.gin.ntt.net [129.250.197.17]
6 19 ms 26 ms 20 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
7 46 ms * 40 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
8 46 ms 41 ms 48 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
9 47 ms 38 ms 44 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
10 48 ms 40 ms 47 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
11 43 ms 171 ms 129 ms 204.2.229.234
12 50 ms 49 ms 49 ms 204.2.229.82
Trace complete.
So, I went from ~90 ping from Montreal to ~45 ping from Sacramento.