3
2
I recently moved two blocks south. That move moved me from Comcast to Broadstripe (high-speed internet cable providers). Comcast was pretty good. Broadstripe sucks. I called them on the phone, and they basically brushed me off (politely). I want to come to them with some numbers, so I can say more than just "it's really slow".
I still have access to my old Comcast service, so I can run the tests using both providers.
Here's what I'm seeing with my new Broadstripe service:
- When I browse to most sites, there is a long delay (5-10 seconds) before the page starts loading in my browser
- The speed test tell me I have 12 megs down (crazy)
- I have a server at my office. I just downloaded some files (using scp on the command line). It said I'm getting 3.5 KB/s
I'm an experienced programmer and spend most of my days on the command line and in vim. Networking, however is not a strong point. I've played around with traceroute, but I'm not sure if that's the right tool to use.
I have access to servers all over the country (I would just use Amazon EC2 to set up a test server), and I prefer to use Ubuntu for my testing.
How can I come up with some hard numbers to show Broadstripe how crappy their service is?
EDIT: Above is my original question. I'm going to specify a little more what I'm looking for.
How can I tell where the latency in is happening. I was trying to scp a file from my desktop to a server hosted in the same city. It took a very long time (~2KB/s with some pretty long periods of inactivity). How can I figure out what is causing this?
Have you checked the round-trip latency? just traceroute somewhere on the internet and see how long it takes for packets to get there and back. Your internet might suck because you have plenty of speed but way too much latency (this really messes with protocols like SCP). – jcrawfordor – 2011-01-17T05:29:10.347
It takes a long time for packets to get there and back. I clocked it with a stopwatch. Here's what I ran $ traceroute -m100 newegg.com. It took 25, 13, 13, 8, 8, 8, ... seconds for each line to come back. I'm not clear what this is telling me, however. – three-cups – 2011-01-17T06:07:38.047
did you solve it or conformed? i heard about a trick on windows 7 to get a better ping. it functions for me... what is your OS? – kokbira – 2011-07-25T14:07:30.557
ICSI Netalyzr is a great broad-based network troubleshooting solution. It gives you a lot of info, so if you know how to use it, it can be very powerful. I don't think you're going to get anywhere by trying to debug things using
traceroute
; most common sources of awful slowness like this originate in (a) the cable modem; (b) physically damaged or defective cable line or ISP-side networking equipment; (c) bad WiFi transceiver in the modem/router, or poorly configured- just AS A START, the chosen wifi channel, GHz band, and frag threshold are a few to check – allquixotic – 2012-08-20T18:35:57.200I know this is old, but the fact that you were able to use a stopwatch to measure the latency of the packets, means that the latency wasn't good at all. – James Mertz – 2013-03-07T15:55:28.740