UO Second Age

Not sure if theres anything I can do about my connection to the server, but I've recently started experiencing terrible lag/packet loss.. Heres me pinging and runnin tracert on uosecondage.com. Any feedback would help, Thanks. (ITs all jibberish to me)


C:\Users\Ben>ping uosecondage.com

Pinging uosecondage.com [64.34.215.106] with 32 bytes of data:
Reply from 64.34.215.106: bytes=32 time=155ms TTL=115
Reply from 64.34.215.106: bytes=32 time=140ms TTL=115
Reply from 64.34.215.106: bytes=32 time=279ms TTL=115
Reply from 64.34.215.106: bytes=32 time=334ms TTL=115

Ping statistics for 64.34.215.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 334ms, Average = 227ms

C:\Users\Ben>tracert uosecondage.com

Tracing route to uosecondage.com [64.34.215.106]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.1.1
2 581 ms 642 ms 535 ms 10.239.24.1
3 541 ms 304 ms 263 ms gig3-9.austtxak-er03.texas.rr.com [24.27.12.134]

4 373 ms 301 ms 428 ms tge0-4-0-6.austtxrdcsc-tr01.texas.rr.com [24.175
.42.22]
5 234 ms 243 ms 295 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]

6 404 ms 400 ms 439 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 348 ms 401 ms 472 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 298 ms 153 ms 203 ms 173.167.57.117
9 149 ms 118 ms 144 ms pos-2-4-0-0-cr01.dallas.tx.ibone.comcast.net [68
.86.87.217]
10 179 ms 202 ms 193 ms pos-0-9-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.87.234]
11 225 ms 237 ms 227 ms he-0-3-0-0-cr01.ashburn.va.ibone.comcast.net [68
.86.89.149]
12 238 ms 318 ms 280 ms be-20-pe06.ashburn.va.ibone.comcast.net [68.86.8
2.98]
13 258 ms 321 ms 252 ms 173.167.58.22
14 297 ms 275 ms 299 ms 10ge-xe-0-0-1.wdc-sp225-sbdis-1.peer1.net [216.1
87.120.106]
15 283 ms 289 ms 261 ms uosecondage.com [64.34.215.106]

Trace complete.

I inexplicably had terrible lag like this last week while everyone else seemed unaffected. I'm not an expert regarding what happens when you send a packet out onto the interweb, but I can imagine that somehow my packets were being routed through some kind of bogged down node or something; the next day it was back to normal.