Do you get the same approximate results if you run tracert several times against the same address?
Looks like it. I tried Isquared three times and each time it started out under 30, then jumped up to 70's, then 90's, and finally request timed out.
What results should I be getting?
There's also a strange issue whenever I try to upload a file - three out of four times the file will come out 0k. I've been trying to do website updates and I have to manually upload each file one by one because uploading a group, they'll all fail. Sometimes image files cut off in the middle.
There's no way to tell exactly what results you should be getting with a traceroute, unfortunately. It depends on lots of different things. Basically, you want as few hops as possible, consistency, and responses as short as possible. If you have few hops but one or two that always approach a second, you are in as much trouble as with a long series of hops that use 50 milliseconds each.
But given the upload issue you mention, I wonder if the problem is closer to you than that.
Are you behind a router at home? The upload problem reminds me of a router I used to own that was misbehaving. Basically, the problem was that it tried to take on too large packages up- or downstream and choked about halfway through.
Most routers have a setting for this, hidden somewhere within the config pages. It's called MPU and the default is usually around 1500.
I experimented with lowering the value to around 1200, which helped.
If your router is something like a Netgear or DLink, or the cheaper Linksys models for home use, the problem might also be caused by the router breaking down. Overheating problems can cause this, as can a power supply about to fail.
was it something I said?