Need some advice on crummy Internet Speeds (random)

[leeland]

My wife and I just built a new house...I pulled all the cable and CAT6.

I ran CAT6 keystones and have a CAT6 patch panel in the basement that is still in progress.

From office to the CAT6 patch panel I (right now) just have a single CAT6 cable going to the Buffalo wireless router then to the cable modem.

It started out blazing fast...I am rated for 7 Mbps down and .5 Mbps up.

I was getting close to 10 down and the rated speed up.

Then a week later the speed wouldn't go above 3 Mbps...sustained...

I tried everything I could think of...different cable, tried speeds via wireless (cause I thought I F'd up the wiring), disconnected the router and test straight to the modem, rebooted devices multiple times...no change.

Called out of frustration and scheduled a tech...then without fail the day before he was to show it went back to around 10 Mbps...and I canceled.

Then a week later (starting Saturday) it went down even lower to around 1.5 Mbps...sustained. I tried all the same steps and have a tech coming out again this week.


SO...I try when I get home today to test again and things are decent...around 6 Mbps...so I am like great...wtf...

But again tonight it dips down to dial up like speeds...

I called tech support three times over the past two weeks and each time I get some donkey who keeps on telling me everything is great...the modem 'reports' back fine...

The only thing I can think of is doing screen captures and downloading the speed reports to show I am not lying...



Does anyone have any basic troubleshooting that they generally do to 'test' out possibilities for inconsistent speeds?

As far as the speed tests go I am using Time Warner's own Cable Speed test website so I would hope it is reliable.


Thanks for reading.

lee

 

[pandemonium]

Oddly enough, I used to be a TSR for a cable company and did this all day long for years; however, the biggest advice I can offer is from when I didn't troubleshoot professionaly.

I had very random outtages with my DSL when I was younger and over the period of 7 months - going back and forth with our ISP and scheduling technicians several times - we eventually discovered the answer was more mundane than ever. It was because of a short in the electrical wiring for lighting. That would be several hours of testing RF ranges on the line while certain appliances, switches or circuits are being used in the house. Being that it's a new house, this is unlikely, but you never know and I wouldn't discount the possibility.

In response to the support donkeys you have to talk to (trust me, I worked with them and know your pain), get someone who can check the RF levels on the modem and further from that monitor the line. If your ISP won't do it, then take it into your own hands and get it done with dslreports.com, or something of that nature.

Hope this helps and good luck!

Edit: Each ISP says to only use their speed test for accuracy, but that's a load of bull. I'd recommend using dslreports.com for this as well.

 

[leeland]

Thanks for the post and I got confirmation from the technician who came out today that the 'node' for our internet is nearing capacity and they have to add additional capacity...which is probably why I was and still am seeing non-existent internet speeds during peek usage hours.

Why that couldn't have been divulged during 1 of my man service calls is beyond me...

The tech didn't even know until he called to find out the overall status of the neighborhood.

Anyways thanks again.

lee

 

[Emulex]

start
cmd
ping -t ip.of.your.router

should be 1ms = no dropped packets

start
cmd
ping -t gateway.ip.of.router (look on your router's config page for the gateway or it can be guessed from the router ip/subnet)
this should also be near 0% packet loss or there is bad wiring.

ping their dns servers (see router) using the same command. should be pretty good but not perfect is okay (0.5% or less loss)

ping google dns (8.8.8.8 or 8.8.4.4) - should be less than 1% or they has serious bandwidth issues

essentially (icmp is flawed) i would then regress that step using larger packet sizes up to your MTU . i forget how to specify block size on the windows. -b? /help ?

tell us the results

 

[pandemonium]

Glad they found out it was bandwidth issues at the node level. Though be vigilant and keep checking even after they "fix it".

Nice breakdown by hop, Emulex, however, his problems were random. So I'd also add to run ping -t's on the DNS, google, and his IP for 24-48 hours to really find out what's going on. Thus the recommedation for dslreports.com line monitoring.

Additionaly, leeland, you can do ping -t ip.of.the.test >> pinglog.txt / ping -t ip#2.of.the.test >> pinglog#2.txt, etc... and then check the logs later. A bit more in depth to diagnose where the problem is to run ping logs on several hops for a tracert to google even.

Glad you got some answers, regardless. ^^

 

[fuzzymath10]

This is pretty common with new/small ISPs. Teksavvy suffers from this in Toronto. They don't look forward very far, and Rogers also likes to delay them where possible.

Since I got the service last July, they've had to upgrade 3 times, when they should have just done it all at once. It should have been obvious that small ISPs tend to attract high-volume users.

In the several weeks prior to each upgrade, connections would be extremely slow anytime other than around 4-9am.

 

[leeland]

start
cmd
ping -t ip.of.your.router

should be 1ms = no dropped packets

start
cmd
ping -t gateway.ip.of.router (look on your router's config page for the gateway or it can be guessed from the router ip/subnet)
this should also be near 0% packet loss or there is bad wiring.

ping their dns servers (see router) using the same command. should be pretty good but not perfect is okay (0.5% or less loss)

ping google dns (8.8.8.8 or 8.8.4.4) - should be less than 1% or they has serious bandwidth issues

essentially (icmp is flawed) i would then regress that step using larger packet sizes up to your MTU . i forget how to specify block size on the windows. -b? /help ?

tell us the results

Ping from router


C:\Users\leeland>ping -t 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Control-C
^C
C:\Users\leeland>





ping from gateway (replaced the IP address)

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\leeland>ping -t Gateway

Pinging Gateway with 32 bytes of data:
Reply from Gateway: bytes=32 time=23ms TTL=254
Reply from Gateway: bytes=32 time=18ms TTL=254
Reply from Gateway: bytes=32 time=33ms TTL=254
Reply from Gateway: bytes=32 time=27ms TTL=254
Reply from Gateway: bytes=32 time=45ms TTL=254
Reply from Gateway: bytes=32 time=46ms TTL=254
Reply from Gateway: bytes=32 time=29ms TTL=254
Reply from Gateway: bytes=32 time=26ms TTL=254
Reply from Gateway: bytes=32 time=14ms TTL=254
Reply from Gateway: bytes=32 time=41ms TTL=254
Reply from Gateway: bytes=32 time=51ms TTL=254
Reply from Gateway: bytes=32 time=42ms TTL=254
Reply from Gateway: bytes=32 time=23ms TTL=254
Reply from Gateway: bytes=32 time=52ms TTL=254
Reply from Gateway: bytes=32 time=39ms TTL=254
Reply from Gateway: bytes=32 time=33ms TTL=254
Reply from Gateway: bytes=32 time=18ms TTL=254
Reply from Gateway: bytes=32 time=26ms TTL=254
Reply from Gateway: bytes=32 time=7ms TTL=254
Reply from Gateway: bytes=32 time=19ms TTL=254
Reply from Gateway: bytes=32 time=24ms TTL=254
Reply from Gateway: bytes=32 time=25ms TTL=254
Reply from Gateway: bytes=32 time=52ms TTL=254
Reply from Gateway: bytes=32 time=39ms TTL=254
Reply from Gateway: bytes=32 time=39ms TTL=254
Reply from Gateway: bytes=32 time=12ms TTL=254
Request timed out.
Reply from Gateway: bytes=32 time=48ms TTL=254
Reply from Gateway: bytes=32 time=20ms TTL=254
Reply from Gateway: bytes=32 time=37ms TTL=254
Reply from Gateway: bytes=32 time=34ms TTL=254
Reply from Gateway: bytes=32 time=36ms TTL=254
Reply from Gateway: bytes=32 time=24ms TTL=254
Reply from Gateway: bytes=32 time=15ms TTL=254
Reply from Gateway: bytes=32 time=29ms TTL=254

Ping statistics for Gateway:
Packets: Sent = 35, Received = 34, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 52ms, Average = 30ms
Control-C
^C
C:\Users\leeland>



Results from DNS ping (I let it run for awhile and only 1 or 2 timeouts 1% loss)


C:\Users\leeland>ping -t DNS

Pinging DNS with 32 bytes of data:
Reply from DNS: bytes=32 time=54ms TTL=107
Reply from DNS: bytes=32 time=58ms TTL=107
Reply from DNS: bytes=32 time=60ms TTL=107
Reply from DNS: bytes=32 time=40ms TTL=107
Reply from DNS: bytes=32 time=44ms TTL=107
Reply from DNS: bytes=32 time=51ms TTL=107
Reply from DNS: bytes=32 time=31ms TTL=107
Reply from DNS: bytes=32 time=39ms TTL=107
Reply from DNS: bytes=32 time=28ms TTL=107
Reply from DNS: bytes=32 time=55ms TTL=107
Reply from DNS: bytes=32 time=44ms TTL=107
Reply from DNS: bytes=32 time=37ms TTL=107
Reply from DNS: bytes=32 time=52ms TTL=107
Reply from DNS: bytes=32 time=54ms TTL=107
Reply from DNS: bytes=32 time=38ms TTL=107
Reply from DNS: bytes=32 time=51ms TTL=107
Reply from DNS: bytes=32 time=65ms TTL=107
Reply from DNS: bytes=32 time=33ms TTL=107
Reply from DNS: bytes=32 time=41ms TTL=107
Reply from DNS: bytes=32 time=87ms TTL=107
Reply from DNS: bytes=32 time=62ms TTL=107
Reply from DNS: bytes=32 time=45ms TTL=107
Reply from DNS: bytes=32 time=94ms TTL=107
Reply from DNS: bytes=32 time=88ms TTL=107
Reply from DNS: bytes=32 time=78ms TTL=107
Reply from DNS: bytes=32 time=78ms TTL=107
Reply from DNS: bytes=32 time=56ms TTL=107
Reply from DNS: bytes=32 time=66ms TTL=107
Reply from DNS: bytes=32 time=56ms TTL=107
Reply from DNS: bytes=32 time=48ms TTL=107
Reply from DNS: bytes=32 time=30ms TTL=107
Reply from DNS: bytes=32 time=64ms TTL=107
Reply from DNS: bytes=32 time=46ms TTL=107
Reply from DNS: bytes=32 time=47ms TTL=107
Reply from DNS: bytes=32 time=80ms TTL=107
Reply from DNS: bytes=32 time=55ms TTL=107
Reply from DNS: bytes=32 time=70ms TTL=107
Reply from DNS: bytes=32 time=76ms TTL=107
Reply from DNS: bytes=32 time=56ms TTL=107
Reply from DNS: bytes=32 time=74ms TTL=107


Ping from both Google DNS servers


C:\Users\leeland>ping -t 8.8.4.4

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=47ms TTL=49
Reply from 8.8.4.4: bytes=32 time=43ms TTL=49
Reply from 8.8.4.4: bytes=32 time=60ms TTL=49
Reply from 8.8.4.4: bytes=32 time=55ms TTL=49
Reply from 8.8.4.4: bytes=32 time=49ms TTL=49
Reply from 8.8.4.4: bytes=32 time=47ms TTL=49
Reply from 8.8.4.4: bytes=32 time=53ms TTL=49
Reply from 8.8.4.4: bytes=32 time=47ms TTL=49
Reply from 8.8.4.4: bytes=32 time=47ms TTL=49
Reply from 8.8.4.4: bytes=32 time=42ms TTL=49
Reply from 8.8.4.4: bytes=32 time=48ms TTL=49
Reply from 8.8.4.4: bytes=32 time=33ms TTL=49
Reply from 8.8.4.4: bytes=32 time=59ms TTL=49
Reply from 8.8.4.4: bytes=32 time=28ms TTL=49
Reply from 8.8.4.4: bytes=32 time=53ms TTL=49
Reply from 8.8.4.4: bytes=32 time=65ms TTL=49
Reply from 8.8.4.4: bytes=32 time=60ms TTL=49
Reply from 8.8.4.4: bytes=32 time=48ms TTL=49
Reply from 8.8.4.4: bytes=32 time=39ms TTL=49
Reply from 8.8.4.4: bytes=32 time=63ms TTL=49
Reply from 8.8.4.4: bytes=32 time=61ms TTL=49
Reply from 8.8.4.4: bytes=32 time=100ms TTL=49
Reply from 8.8.4.4: bytes=32 time=57ms TTL=49
Reply from 8.8.4.4: bytes=32 time=43ms TTL=49
Reply from 8.8.4.4: bytes=32 time=73ms TTL=49
Reply from 8.8.4.4: bytes=32 time=60ms TTL=49
Reply from 8.8.4.4: bytes=32 time=52ms TTL=49
Reply from 8.8.4.4: bytes=32 time=59ms TTL=49
Reply from 8.8.4.4: bytes=32 time=61ms TTL=49
Reply from 8.8.4.4: bytes=32 time=78ms TTL=49
Reply from 8.8.4.4: bytes=32 time=46ms TTL=49
Reply from 8.8.4.4: bytes=32 time=76ms TTL=49
Reply from 8.8.4.4: bytes=32 time=36ms TTL=49
Reply from 8.8.4.4: bytes=32 time=42ms TTL=49
Reply from 8.8.4.4: bytes=32 time=52ms TTL=49
Reply from 8.8.4.4: bytes=32 time=88ms TTL=49
Reply from 8.8.4.4: bytes=32 time=76ms TTL=49
Reply from 8.8.4.4: bytes=32 time=34ms TTL=49
Reply from 8.8.4.4: bytes=32 time=54ms TTL=49
Reply from 8.8.4.4: bytes=32 time=76ms TTL=49
Reply from 8.8.4.4: bytes=32 time=58ms TTL=49
Reply from 8.8.4.4: bytes=32 time=67ms TTL=49
Reply from 8.8.4.4: bytes=32 time=63ms TTL=49
Reply from 8.8.4.4: bytes=32 time=79ms TTL=49
Reply from 8.8.4.4: bytes=32 time=48ms TTL=49
Request timed out.
Reply from 8.8.4.4: bytes=32 time=61ms TTL=49
Reply from 8.8.4.4: bytes=32 time=71ms TTL=49
Reply from 8.8.4.4: bytes=32 time=53ms TTL=49
Reply from 8.8.4.4: bytes=32 time=55ms TTL=49
Reply from 8.8.4.4: bytes=32 time=80ms TTL=49
Reply from 8.8.4.4: bytes=32 time=53ms TTL=49
Reply from 8.8.4.4: bytes=32 time=73ms TTL=49
Reply from 8.8.4.4: bytes=32 time=52ms TTL=49
Reply from 8.8.4.4: bytes=32 time=51ms TTL=49
Reply from 8.8.4.4: bytes=32 time=78ms TTL=49
Reply from 8.8.4.4: bytes=32 time=67ms TTL=49
Reply from 8.8.4.4: bytes=32 time=45ms TTL=49
Reply from 8.8.4.4: bytes=32 time=55ms TTL=49
Reply from 8.8.4.4: bytes=32 time=56ms TTL=49
Reply from 8.8.4.4: bytes=32 time=87ms TTL=49
Reply from 8.8.4.4: bytes=32 time=36ms TTL=49
Reply from 8.8.4.4: bytes=32 time=57ms TTL=49
Reply from 8.8.4.4: bytes=32 time=45ms TTL=49
Reply from 8.8.4.4: bytes=32 time=31ms TTL=49
Reply from 8.8.4.4: bytes=32 time=48ms TTL=49
Request timed out.
Reply from 8.8.4.4: bytes=32 time=75ms TTL=49
Reply from 8.8.4.4: bytes=32 time=83ms TTL=49
Reply from 8.8.4.4: bytes=32 time=68ms TTL=49
Reply from 8.8.4.4: bytes=32 time=67ms TTL=49
Reply from 8.8.4.4: bytes=32 time=122ms TTL=49
Reply from 8.8.4.4: bytes=32 time=89ms TTL=49
Reply from 8.8.4.4: bytes=32 time=49ms TTL=49
Reply from 8.8.4.4: bytes=32 time=45ms TTL=49
Reply from 8.8.4.4: bytes=32 time=69ms TTL=49
Reply from 8.8.4.4: bytes=32 time=47ms TTL=49
Reply from 8.8.4.4: bytes=32 time=54ms TTL=49
Reply from 8.8.4.4: bytes=32 time=62ms TTL=49
Reply from 8.8.4.4: bytes=32 time=62ms TTL=49
Reply from 8.8.4.4: bytes=32 time=78ms TTL=49
Reply from 8.8.4.4: bytes=32 time=68ms TTL=49
Reply from 8.8.4.4: bytes=32 time=72ms TTL=49
Reply from 8.8.4.4: bytes=32 time=61ms TTL=49
Reply from 8.8.4.4: bytes=32 time=70ms TTL=49
Reply from 8.8.4.4: bytes=32 time=60ms TTL=49
Reply from 8.8.4.4: bytes=32 time=116ms TTL=49
Reply from 8.8.4.4: bytes=32 time=82ms TTL=49
Reply from 8.8.4.4: bytes=32 time=64ms TTL=49
Reply from 8.8.4.4: bytes=32 time=84ms TTL=49
Reply from 8.8.4.4: bytes=32 time=61ms TTL=49
Reply from 8.8.4.4: bytes=32 time=50ms TTL=49
Request timed out.
Request timed out.
Reply from 8.8.4.4: bytes=32 time=49ms TTL=49
Reply from 8.8.4.4: bytes=32 time=56ms TTL=49
Reply from 8.8.4.4: bytes=32 time=35ms TTL=49
Reply from 8.8.4.4: bytes=32 time=49ms TTL=49
Reply from 8.8.4.4: bytes=32 time=31ms TTL=49
Reply from 8.8.4.4: bytes=32 time=45ms TTL=49
Reply from 8.8.4.4: bytes=32 time=44ms TTL=49
Reply from 8.8.4.4: bytes=32 time=54ms TTL=49
Reply from 8.8.4.4: bytes=32 time=41ms TTL=49
Reply from 8.8.4.4: bytes=32 time=45ms TTL=49
Reply from 8.8.4.4: bytes=32 time=52ms TTL=49
Reply from 8.8.4.4: bytes=32 time=64ms TTL=49
Reply from 8.8.4.4: bytes=32 time=59ms TTL=49
Reply from 8.8.4.4: bytes=32 time=75ms TTL=49
Reply from 8.8.4.4: bytes=32 time=57ms TTL=49
Reply from 8.8.4.4: bytes=32 time=61ms TTL=49
Reply from 8.8.4.4: bytes=32 time=66ms TTL=49
Reply from 8.8.4.4: bytes=32 time=50ms TTL=49
Reply from 8.8.4.4: bytes=32 time=76ms TTL=49
Reply from 8.8.4.4: bytes=32 time=45ms TTL=49
Reply from 8.8.4.4: bytes=32 time=56ms TTL=49

Ping statistics for 8.8.4.4:
Packets: Sent = 115, Received = 111, Lost = 4 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 122ms, Average = 58ms
Control-C
^C
C:\Users\leeland>ping -t 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=63ms TTL=49
Reply from 8.8.8.8: bytes=32 time=60ms TTL=49
Reply from 8.8.8.8: bytes=32 time=46ms TTL=49
Reply from 8.8.8.8: bytes=32 time=40ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=56ms TTL=49
Reply from 8.8.8.8: bytes=32 time=30ms TTL=49
Reply from 8.8.8.8: bytes=32 time=40ms TTL=49
Reply from 8.8.8.8: bytes=32 time=91ms TTL=49
Reply from 8.8.8.8: bytes=32 time=74ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=88ms TTL=49
Reply from 8.8.8.8: bytes=32 time=76ms TTL=49
Reply from 8.8.8.8: bytes=32 time=56ms TTL=49
Reply from 8.8.8.8: bytes=32 time=71ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=59ms TTL=49
Reply from 8.8.8.8: bytes=32 time=70ms TTL=49
Reply from 8.8.8.8: bytes=32 time=93ms TTL=49
Reply from 8.8.8.8: bytes=32 time=69ms TTL=49
Reply from 8.8.8.8: bytes=32 time=67ms TTL=49
Reply from 8.8.8.8: bytes=32 time=61ms TTL=49
Reply from 8.8.8.8: bytes=32 time=105ms TTL=49
Reply from 8.8.8.8: bytes=32 time=86ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=112ms TTL=49
Reply from 8.8.8.8: bytes=32 time=96ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=40ms TTL=49
Reply from 8.8.8.8: bytes=32 time=69ms TTL=49
Reply from 8.8.8.8: bytes=32 time=55ms TTL=49
Reply from 8.8.8.8: bytes=32 time=56ms TTL=49
Reply from 8.8.8.8: bytes=32 time=72ms TTL=49
Reply from 8.8.8.8: bytes=32 time=53ms TTL=49
Reply from 8.8.8.8: bytes=32 time=40ms TTL=49
Reply from 8.8.8.8: bytes=32 time=59ms TTL=49
Reply from 8.8.8.8: bytes=32 time=57ms TTL=49
Reply from 8.8.8.8: bytes=32 time=89ms TTL=49
Reply from 8.8.8.8: bytes=32 time=68ms TTL=49
Reply from 8.8.8.8: bytes=32 time=115ms TTL=49
Reply from 8.8.8.8: bytes=32 time=111ms TTL=49
Reply from 8.8.8.8: bytes=32 time=66ms TTL=49
Reply from 8.8.8.8: bytes=32 time=73ms TTL=49
Reply from 8.8.8.8: bytes=32 time=69ms TTL=49
Reply from 8.8.8.8: bytes=32 time=92ms TTL=49
Reply from 8.8.8.8: bytes=32 time=74ms TTL=49
Reply from 8.8.8.8: bytes=32 time=53ms TTL=49
Reply from 8.8.8.8: bytes=32 time=68ms TTL=49
Reply from 8.8.8.8: bytes=32 time=88ms TTL=49
Reply from 8.8.8.8: bytes=32 time=68ms TTL=49
Reply from 8.8.8.8: bytes=32 time=106ms TTL=49
Reply from 8.8.8.8: bytes=32 time=85ms TTL=49
Reply from 8.8.8.8: bytes=32 time=55ms TTL=49
Reply from 8.8.8.8: bytes=32 time=67ms TTL=49
Reply from 8.8.8.8: bytes=32 time=62ms TTL=49
Reply from 8.8.8.8: bytes=32 time=44ms TTL=49
Reply from 8.8.8.8: bytes=32 time=100ms TTL=49
Reply from 8.8.8.8: bytes=32 time=114ms TTL=49
Reply from 8.8.8.8: bytes=32 time=82ms TTL=49
Reply from 8.8.8.8: bytes=32 time=97ms TTL=49
Reply from 8.8.8.8: bytes=32 time=67ms TTL=49
Reply from 8.8.8.8: bytes=32 time=49ms TTL=49
Reply from 8.8.8.8: bytes=32 time=71ms TTL=49
Reply from 8.8.8.8: bytes=32 time=30ms TTL=49
Reply from 8.8.8.8: bytes=32 time=45ms TTL=49
Reply from 8.8.8.8: bytes=32 time=86ms TTL=49
Reply from 8.8.8.8: bytes=32 time=52ms TTL=49
Reply from 8.8.8.8: bytes=32 time=61ms TTL=49
Reply from 8.8.8.8: bytes=32 time=37ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=49
Reply from 8.8.8.8: bytes=32 time=74ms TTL=49
Reply from 8.8.8.8: bytes=32 time=84ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=93ms TTL=49
Reply from 8.8.8.8: bytes=32 time=48ms TTL=49
Reply from 8.8.8.8: bytes=32 time=68ms TTL=49
Reply from 8.8.8.8: bytes=32 time=78ms TTL=49
Reply from 8.8.8.8: bytes=32 time=82ms TTL=49
Reply from 8.8.8.8: bytes=32 time=69ms TTL=49
Reply from 8.8.8.8: bytes=32 time=58ms TTL=49
Reply from 8.8.8.8: bytes=32 time=44ms TTL=49
Reply from 8.8.8.8: bytes=32 time=94ms TTL=49
Reply from 8.8.8.8: bytes=32 time=59ms TTL=49
Reply from 8.8.8.8: bytes=32 time=66ms TTL=49
Reply from 8.8.8.8: bytes=32 time=65ms TTL=49
Reply from 8.8.8.8: bytes=32 time=47ms TTL=49
Reply from 8.8.8.8: bytes=32 time=72ms TTL=49
Reply from 8.8.8.8: bytes=32 time=73ms TTL=49
Reply from 8.8.8.8: bytes=32 time=72ms TTL=49
Reply from 8.8.8.8: bytes=32 time=74ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=47ms TTL=49
Reply from 8.8.8.8: bytes=32 time=87ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=108ms TTL=49
Reply from 8.8.8.8: bytes=32 time=94ms TTL=49
Reply from 8.8.8.8: bytes=32 time=31ms TTL=49
Reply from 8.8.8.8: bytes=32 time=74ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=87ms TTL=49
Reply from 8.8.8.8: bytes=32 time=47ms TTL=49
Reply from 8.8.8.8: bytes=32 time=57ms TTL=49
Reply from 8.8.8.8: bytes=32 time=85ms TTL=49
Reply from 8.8.8.8: bytes=32 time=44ms TTL=49
Reply from 8.8.8.8: bytes=32 time=78ms TTL=49
Reply from 8.8.8.8: bytes=32 time=58ms TTL=49
Reply from 8.8.8.8: bytes=32 time=74ms TTL=49
Reply from 8.8.8.8: bytes=32 time=117ms TTL=49
Reply from 8.8.8.8: bytes=32 time=59ms TTL=49
Reply from 8.8.8.8: bytes=32 time=81ms TTL=49
Reply from 8.8.8.8: bytes=32 time=61ms TTL=49
Reply from 8.8.8.8: bytes=32 time=44ms TTL=49
Reply from 8.8.8.8: bytes=32 time=49ms TTL=49
Reply from 8.8.8.8: bytes=32 time=101ms TTL=49
Reply from 8.8.8.8: bytes=32 time=91ms TTL=49
Reply from 8.8.8.8: bytes=32 time=91ms TTL=49
Reply from 8.8.8.8: bytes=32 time=56ms TTL=49
Reply from 8.8.8.8: bytes=32 time=42ms TTL=49
Reply from 8.8.8.8: bytes=32 time=68ms TTL=49
Reply from 8.8.8.8: bytes=32 time=57ms TTL=49
Reply from 8.8.8.8: bytes=32 time=39ms TTL=49
Reply from 8.8.8.8: bytes=32 time=63ms TTL=49
Reply from 8.8.8.8: bytes=32 time=98ms TTL=49
Reply from 8.8.8.8: bytes=32 time=54ms TTL=49
Reply from 8.8.8.8: bytes=32 time=60ms TTL=49
Reply from 8.8.8.8: bytes=32 time=60ms TTL=49
Reply from 8.8.8.8: bytes=32 time=53ms TTL=49
Reply from 8.8.8.8: bytes=32 time=61ms TTL=49
Reply from 8.8.8.8: bytes=32 time=71ms TTL=49
Reply from 8.8.8.8: bytes=32 time=68ms TTL=49
Reply from 8.8.8.8: bytes=32 time=64ms TTL=49
Reply from 8.8.8.8: bytes=32 time=41ms TTL=49
Reply from 8.8.8.8: bytes=32 time=68ms TTL=49
Reply from 8.8.8.8: bytes=32 time=91ms TTL=49
Reply from 8.8.8.8: bytes=32 time=117ms TTL=49
Reply from 8.8.8.8: bytes=32 time=86ms TTL=49
Reply from 8.8.8.8: bytes=32 time=104ms TTL=49
Reply from 8.8.8.8: bytes=32 time=98ms TTL=49
Reply from 8.8.8.8: bytes=32 time=100ms TTL=49
Reply from 8.8.8.8: bytes=32 time=94ms TTL=49
Reply from 8.8.8.8: bytes=32 time=71ms TTL=49
Reply from 8.8.8.8: bytes=32 time=114ms TTL=49
Reply from 8.8.8.8: bytes=32 time=126ms TTL=49
Reply from 8.8.8.8: bytes=32 time=66ms TTL=49
Reply from 8.8.8.8: bytes=32 time=49ms TTL=49
Reply from 8.8.8.8: bytes=32 time=71ms TTL=49
Reply from 8.8.8.8: bytes=32 time=106ms TTL=49

Ping statistics for 8.8.8.8:
Packets: Sent = 148, Received = 138, Lost = 10 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 126ms, Average = 70ms
Control-C
^C
C:\Users\leeland>
as I type this I did a speed test for chagrins and it came back @ 1.5 Mbps...been like this all weekend...

 

[Texashiker]

My wife and I just built a new house...I pulled all the cable and CAT6.

What kind of cable did you run from the outside of the house to the attic for the cable modem, and throughout the rest of the house?? RG-59, RG-6, dual shield, quad shield,,,, or something else?

Lets talk about grounding, does the cable enter the house at the same location as the power lines? Go outside and look at the cable line, is there a ground wire going from what looks like a splitter to the ground wire?

If your feeling extra spunky, at the ground block on the outside of the house, disconnect the cable line going from the attic to outside, lick your finger, touch your finger it to the copper on the inside of the cable line. Did you receive a "tingle" - dont worry, it should be at the most 60 volts. If you did receive a "tingle" that is not normal.

 

[Emulex]

the gateway should be like 10ms unless you have wifi or are doing heavy leeching. i get 60ms on clearwire 4g (via wifi) and about 100-120ms on 3G (AT&T tethering wifi).

could be your node is overloaded or your connection to the node is overloaded.

 

[pandemonium]

leeland, I'd still have a technician check the Rf levels and dB levels on your lines to see if noise or interference is hurting your connection. That's just me being thorough. /shrug

 

[leeland]

What kind of cable did you run from the outside of the house to the attic for the cable modem, and throughout the rest of the house?? RG-59, RG-6, dual shield, quad shield,,,, or something else?

Lets talk about grounding, does the cable enter the house at the same location as the power lines? Go outside and look at the cable line, is there a ground wire going from what looks like a splitter to the ground wire?

If your feeling extra spunky, at the ground block on the outside of the house, disconnect the cable line going from the attic to outside, lick your finger, touch your finger it to the copper on the inside of the cable line. Did you receive a "tingle" - dont worry, it should be at the most 60 volts. If you did receive a "tingle" that is not normal.

I am not sure what was run from the box attached to our home to inside to the cable modem...it would be what ever they supplied. Probably the cheapest bulk cable possible.

The line from the road to my house I was told was RG-11. The cable runs from a box in our yard and is buried undergroud with the other service lines and runs around back to the power meter and the cable junction box. From there it goes into the basement to my central drop zone for cable and CAT6

I am positive it isn't RG-6 quad shield because the original guy that F'd up the wiring even told me he didn't have the correct tools for RG-6.


Two nights ago the cable company apparently did the servicing as we got an automated phone call.

I checked last night during peak user hours and the internet speeds were as expected...I did several tests throughout the night on various speed test websites and the below example is what the speeds look like after the servicing to the neighborhood...

------------------------------------------------------------------
File size transferred : 59.01 MB (61874896 bytes)
Total time taken : 62.97 seconds (62975 milliseconds)
Throughput : 982.0 KB/sec [Kilobyte-per-second]
= 0.98 MB/sec [Megabyte-per-second]
= 7856.0 Kbps [Kilobit-per-second]
= 7.86 Mbps [Megabit-per-second]

So I am assuming it is going to be fine from this point forward...

leeland, I'd still have a technician check the Rf levels and dB levels on your lines to see if noise or interference is hurting your connection. That's just me being thorough. /shrug

Thanks for the input...it is a good point know and if this starts to deteriorate again or I have another issue this will be one of the first talking points.

Is that something they can monitor from the box to the house or that is monitored from inside the home?

Reason I ask is each time (of the 3 guys that have come to my home) the cable tech has been out they don't even give me a chance to ask...they say 'I already checked your line and it is fine'.

 

[Texashiker]

leeland, I'd still have a technician check the Rf levels and dB levels on your lines to see if noise or interference is hurting your connection.

Measuring the signal with a standard meter does not tell you the signal-to-noise ratio.

Given a signal strength of 20 decibels, most meters can not tell the difference between a local radio station that is getting into the line (ingress), and the actual internet signal.

There are signal meters out there that measure the sign-to-noise ratio, but they are expensive. The meter I carried while I worked for a cable company cost about $1,000, and it was a cheap model.

 

[OlafSicky]

I just saw this thread. I had weird internet problems speed was fine than it would go out etc. I wasted lots of time and effort with the dsl provider. I had the line tested several times and it was “fine”. I ran into problems again a guy came out tested the line in the house and said fine than he decided to test again at my insistence where it was coming into the house. It turns out that when testing inside my noise looked fine no problems strong signal but when he tested again at the source there was a problem. It turns out i had another line “interfering” they switched me over to a different one and i have a very solid connection now. So all noise testing equipment is not equal ,speed test doesn’t tell the whole story. Do some sort of line quality test.

 

[leeland]

going on 10 days past the expected fix date because they are still apparently waiting for hardware and a time to install it to 'expand the node' due to high utilization for our hood.

I HOPE that cleans things up...