Seems the problem is with Funcom or their ISP, according to this trace log:
Tracing route to http://www.funcom.com [216.74.170.142]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms *.*.*.*
2 1 ms 1 ms 1 ms *.*.*.*.dd.nextgentel.com [*.*.*.*]
3 18 ms 18 ms 18 ms 129.80-202-79.nextgentel.com [80.202.79.129]
4 18 ms 18 ms 18 ms 217-13-7-65.dd.nextgentel.com [217.13.7.65]
5 19 ms 18 ms 18 ms 217-13-0-94.dd.nextgentel.com [217.13.0.94]
6 19 ms 19 ms 18 ms 217-13-0-2.dd.nextgentel.com [217.13.0.2]
7 18 ms 19 ms 18 ms 217-13-6-149.dd.nextgentel.com [217.13.6.149]
8 22 ms 20 ms 18 ms ge0-3-0-103.ar1.OSL1.gblx.net [208.51.41.57]
9 58 ms 58 ms 58 ms so0-0-0-2488M.ar3.LON2.gblx.net [67.17.71.25]
10 58 ms 58 ms 59 ms bcr1-ge-4-3-0.Londonlnx.savvis.net [195.66.224.39]
11 59 ms 58 ms 58 ms bcs2-so-1-1-0.Londonlnx.savvis.net [204.70.193.122]
12 59 ms 59 ms 59 ms bcs1-as0-0.Londonlnx.savvis.net [204.70.193.201]
13 125 ms 125 ms 125 ms bcs2-so-0-0-0.NewYork.savvis.net [204.70.192.121]
14 125 ms 125 ms 125 ms bcs1-so-6-0-0.NewYork.savvis.net [204.70.192.37]
15 131 ms 132 ms 131 ms bcs1-so-6-0-0.Washington.savvis.net [204.70.192.5]
16 135 ms 135 ms 135 ms ahr1-pos-10-0.Weehawkennj2.savvis.net [206.24.238.230]
17 * * * Request timed out.
18 * * * Request timed out.
