[zenith]

Weathers Wrote:My connection (not just here, in general) has been FUBAR since all the snow came down.

My archaic building can't handle new fangled things like weather.

I just got in contact with our datacenter and our contact said he had the exact same issues from home, but the datacenter isn't seeing those issues. Our server is on a backbone and the graphs show it is still chugging along as normal.

He said to do a traceroute to our server. The hops should show some of the issues. If that's too technical for some, I could attempt to walk you through it but I haven't used Windows in ages...

Windows Key + R
A window will pop up. Type the following and hit enter...
cmd
A dos box should pop up. Type the following...
tracert http://www.awakenedlands.com

Check the hops. If you want to cut and paste the results here we can nitpick at the hop lag. Just try to edit out your first hop IP since it's normally your public IP address (unless it starts with 192.168) For example, mine looks like...

Code:

1  masked ip (masked ip)  0.598 ms  0.243 ms  0.203 ms
2  * * *
3  ip68-4-13-217.oc.oc.cox.net (68.4.13.217)  6.059 ms  5.759 ms  6.474 ms
4  ip68-4-13-9.oc.oc.cox.net (68.4.13.9)  7.985 ms  8.746 ms  7.942 ms
5  ip68-4-13-50.oc.oc.cox.net (68.4.13.50)  7.995 ms  8.707 ms  7.400 ms
6  wsip-64-58-133-86.oc.oc.cox.net (64.58.133.86)  7.236 ms  8.334 ms  7.959 ms
7  wsip-24-249-247-70.oc.oc.cox.net (24.249.247.70)  7.916 ms  6.810 ms  7.934 ms
8  awakenedlands.com (70.182.140.221)  7.956 ms  6.786 ms  7.948 ms

Look for lines that have asterisks. Mine is showing the second hop as a potential issue. Err, who's on the same provider doesn't have this issue, and uses almost a completely different route than me even though we live a few minutes from each other.

I've checked the dslreports forums for my provider and it looks like they are suggesting it's not really Cox Communications, but a greater problem caused by some bad weather.