0zero01
join:2000-08-01
Port Orchard, WA
 ·wavebroadband
| Major crap!
For the last 2 months I've been experiencing packet loss and high ping times, as well as slow speeds. The slow downs started occurring during peak times, but now have dropped into the the twilight hours as well. I can't even hold a conversation on my voip and it's not my voip providers fault. Obviously (if you look at the attachments) my local network is healthy. I have packet loss to Waves gateway. My Signal levels are good.
(info attached).
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
chpalmer
join:2002-11-18
Bremerton, WA
 ·VOIPo
edit:
August 18th, @07:20PM
| Ping your modem 192.168.100.1
Im on a docsis 2.0 modem here. It actually puts me on differnt channels than your on. But your node could have problems mine doesnt and visa versa... |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| Well everything is fine so far today. If any more problems arise I'll continue to post them here. Here's the modem ping, and a speed test.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
chpalmer
join:2002-11-18
Bremerton, WA
·VOIPo
| reply to 0zero01
First thing I always do is to run a ping -t 192.168.100.1 (or whatever is furthest out on my clients equipment) and then start wiggling cables.
About 25% of the time I do find a bad connection. Whether or not thats the cause of my/their problem is hit and miss.
Just a tool in the box.  |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
|  
No problem now! |
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
chpalmer
join:2002-11-18
Bremerton, WA
·VOIPo
| reply to 0zero01
If its a problem directly on the node, going docsis 2.0 may or may not help. Just because it puts you on another frequency. If the problem is elsewhere on the line, it wont help.
Id do it, if it were me. Keep the 4100 series modem around for backup.
If you do post your signal page here when your up. |
|
BlackIceXP
join:2005-01-13
Port Orchard, WA | reply to 0zero01
I have been noticing similar issues here in Port Orchard. Ping times seem mediocre at best, although my speed seems to not have been affected. I'll keep an eye out. I wonder what's up? |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| reply to 0zero01
Here we go again but not quite as bad. This is beginning to be an every night occurrence. The lagging packets are wreaking havoc with my voip. :-(
To put it bluntly . . .This Sucks!
I say every night because I'm not at home during the day.
No difference if with my router or direct to my 4pc's or laptop. I'm on the verge of going to Qwest. Many years ago when I had dsl at this address I had no problems, except I can only get 1.5Mb here on dsl.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
edit:
September 14th, @03:00AM
| reply to 0zero01
Down to an all time low . . .
I dropped my voip as I can no longer use it. (Got a cell instead). $65 a month for 8Mb/1.5, and this is all I get when I use my connection at 11:00pm.
My latest speed test result from Speedtest.net
Seattle was at 417kbps/235. I also tried Speak Easy and the speed tests provided here at DSLReports.
Modem signal levels are:
SNR = 36db
Downstream signal at +0 dbmv
Upstream = 42dbmv
My packet loss/latency is ridiculous.
(Even to my local cmts).
This has been tested and documented with multiple pc's
and routers. |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| reply to 0zero01
Good Signal levels remain a constant for what it's worth. Unfortunately, I'm not home during the day because of work but when I get home this is what I've been getting. It's not worth it . . .I may have to go 1.5Mb dsl soon :-(. I'm not getting much more from Wave anyway. Along with my slow speeds I have extremely bad latency problems that forced me to drop my voip and get a cell phone. At least with DSL I know my ping times will be good. Is anyone else in my area experiencing this? I live on Sedgwick Rd. in Port Orchard, WA. I'm curios if anyone else here in my node is having the same problems. It seems like a classic case of an over sold node that may need re-segmenting. On my days off my speeds and latency seem to be OK, but my voip would still cut out like crazy. Anyways I'm sick of it. I've been in the Cable business over 8 years (TCI, AT&T and now Comcast). I didn't just fall off the Cable Truck (I was an @home technician when we still supported Intel 486 PCs). I've exhausted every avenue of repair I can get my hands on, short of touching Waves plant, Witch I would never do because I could lose my job. I've replaced everything to no avail. (Modem, Drop, Router, PC, Ground block, Wall plate, You name it, It's been done). The node I'm on is on the corner of Converse and Sedgwick RD. I'm maybe Two taps back from the node towards Jackson RD. I'm really frustrated with this. The service was awesome a few months back, but now it's almost unusable for me. I'm going to contact Wave support and give them the link to this thread. I won't call a CSR because they'll just want to send a "Tap to House" tech out. It won't do any good unless they come out at 9:00pm on a week day, and that will never happen . . .
Latest speed test below. I hope other customers aren't experiencing this, Just imagine if I had WAVE Digital Voice with pings to the gateway like that.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
chpalmer
join:2002-11-18
Bremerton, WA
·VOIPo
| Heres a ping from the Gorst area at 6:45pm Friday night.
Pinging wavebroadband.com [64.79.201.140] with 32 bytes of data:
Reply from 64.79.201.140: bytes=32 time=18ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Reply from 64.79.201.140: bytes=32 time=13ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=23ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=14ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Reply from 64.79.201.140: bytes=32 time=13ms TTL=55
Reply from 64.79.201.140: bytes=32 time=14ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=19ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Reply from 64.79.201.140: bytes=32 time=13ms TTL=55
Reply from 64.79.201.140: bytes=32 time=14ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Ping statistics for 64.79.201.140:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 23ms, Average = 15ms
Ill post one in a couple hours.
You can use this as comparison when you talk to them.
Voip works great here. Testing Voipo |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| Thank you Chpalmer. I wish I had pings like that.
Here it is almost 10:00pm and again Packet loss. I'll try to make time on my day off during the early hours to test it, but usually it's 7:00pm to 1:00am when I have the most problems.
Pinging www.wavebroadband.com [64.79.201.140] with 32 bytes of data:
Reply from 64.79.201.140: bytes=32 time=24ms TTL=54
Reply from 64.79.201.140: bytes=32 time=27ms TTL=54
Reply from 64.79.201.140: bytes=32 time=17ms TTL=54
Reply from 64.79.201.140: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 64.79.201.140: bytes=32 time=20ms TTL=54
Reply from 64.79.201.140: bytes=32 time=19ms TTL=54
Reply from 64.79.201.140: bytes=32 time=20ms TTL=54
Reply from 64.79.201.140: bytes=32 time=65ms TTL=54
Reply from 64.79.201.140: bytes=32 time=22ms TTL=54
Reply from 64.79.201.140: bytes=32 time=27ms TTL=54
Reply from 64.79.201.140: bytes=32 time=20ms TTL=54
Reply from 64.79.201.140: bytes=32 time=19ms TTL=54
Reply from 64.79.201.140: bytes=32 time=17ms TTL=54
Reply from 64.79.201.140: bytes=32 time=15ms TTL=54
Reply from 64.79.201.140: bytes=32 time=15ms TTL=54
Reply from 64.79.201.140: bytes=32 time=20ms TTL=54
Reply from 64.79.201.140: bytes=32 time=20ms TTL=54
Reply from 64.79.201.140: bytes=32 time=29ms TTL=54
Reply from 64.79.201.140: bytes=32 time=24ms TTL=54
Reply from 64.79.201.140: bytes=32 time=19ms TTL=54
Reply from 64.79.201.140: bytes=32 time=20ms TTL=54
Reply from 64.79.201.140: bytes=32 time=16ms TTL=54
Reply from 64.79.201.140: bytes=32 time=15ms TTL=54
Reply from 64.79.201.140: bytes=32 time=15ms TTL=54
Reply from 64.79.201.140: bytes=32 time=18ms TTL=54
Reply from 64.79.201.140: bytes=32 time=19ms TTL=54
Reply from 64.79.201.140: bytes=32 time=882ms TTL=54
Reply from 64.79.201.140: bytes=32 time=344ms TTL=54
Reply from 64.79.201.140: bytes=32 time=100ms TTL=54
Reply from 64.79.201.140: bytes=32 time=103ms TTL=54
Reply from 64.79.201.140: bytes=32 time=22ms TTL=54
Ping statistics for 64.79.201.140:
Packets: Sent = 32, Received = 31, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 882ms, Average = 65ms
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| 4:06pm on Sunday :-(
Can't do anything with this. |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| Speed test results since Aug 17th from speedtest.net seattle
8/17/2007 5:59 AM GMT 1089 kb/s 743 kb/s 140 ms
8/17/2007 6:01 AM GMT 5280 kb/s 1445 kb/s 49 ms
8/17/2007 6:20 AM GMT 3480 kb/s 1343 kb/s 34 ms
8/17/2007 6:28 AM GMT 2796 kb/s 1169 kb/s 34 ms
8/19/2007 3:12 AM GMT 12789 kb/s 1435 kb/s 31 ms
8/19/2007 3:16 AM GMT 13338 kb/s 1432 kb/s 33 ms
8/19/2007 10:46 PM GMT 8801 kb/s 1311 kb/s 50 ms
8/19/2007 10:47 PM GMT 11379 kb/s 1328 kb/s 36 ms
8/21/2007 9:51 PM GMT 4626 kb/s 1003 kb/s 41 ms
8/21/2007 9:52 PM GMT 9570 kb/s 1125 kb/s 37 ms
8/24/2007 4:35 AM GMT 5755 kb/s 1206 kb/s 56 ms
8/25/2007 5:06 AM GMT 8111 kb/s 1082 kb/s 44 ms
8/31/2007 4:26 AM GMT 11063 kb/s 1216 kb/s 69 ms
9/11/2007 4:18 PM GMT 12003 kb/s 1060 kb/s 31 ms
9/12/2007 4:16 AM GMT 1887 kb/s 1098 kb/s 101 ms
9/13/2007 5:53 AM GMT 417 kb/s 256 kb/s 227 ms
9/13/2007 6:02 AM GMT 3595 kb/s 959 kb/s 97 ms
9/14/2007 5:40 AM GMT 2157 kb/s 290 kb/s 62 ms
9/16/2007 11:20 PM GMT 6435 kb/s 1166 kb/s 49 ms
They're all over the place.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
chpalmer
join:2002-11-18
Bremerton, WA
·VOIPo
| reply to 0zero01
Wow!!! That SUCKS!
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
Pinging wavebroadband.com [64.79.201.140] with 32 bytes of data:
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=18ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=18ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=16ms TTL=55
Reply from 64.79.201.140: bytes=32 time=15ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Reply from 64.79.201.140: bytes=32 time=18ms TTL=55
Reply from 64.79.201.140: bytes=32 time=18ms TTL=55
Reply from 64.79.201.140: bytes=32 time=17ms TTL=55
Ping statistics for 64.79.201.140:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 18ms, Average = 16ms
10:20 Sunday Night
Im betting EVDO becomes a real viable competitor with this industry. Hopefully they get you fixed!
If you get on another gateway does it change any? |
|
chpalmer
join:2002-11-18
Bremerton, WA
·VOIPo
| reply to 0zero01
Im Third down on this page...»/testhistory?v···pen=&p=2
You should try and get on here also.
»Extended Pacific Northwest Line Monitoring SignUps |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| I did a little mac address cloning last night, I could get my IP to change but the gateway stayed the same every time.
I also switched direct to my pc and then to my laptop even though I knew things wouldn't change. Here we are the next morning.
I'm sure this evening will bring another round of massive packet loss though. My gateway is 24.113.58.1 I'm going to be in Auburn until tomorrow but I'm going to ping that gateway IP tonight and see what results I get. If you have time I'm curious what your results might be.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
chpalmer
join:2002-11-18
Bremerton, WA
·VOIPo
| 1:20am Little spikes here and there
C:>ping -n 25 24.113.58.
Pinging 24.113.58.1 with 32 bytes of data:
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=15ms TTL=255
Reply from 24.113.58.1: bytes=32 time=21ms TTL=255
Reply from 24.113.58.1: bytes=32 time=17ms TTL=255
Reply from 24.113.58.1: bytes=32 time=10ms TTL=255
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=20ms TTL=255
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=17ms TTL=255
Reply from 24.113.58.1: bytes=32 time=19ms TTL=255
Reply from 24.113.58.1: bytes=32 time=12ms TTL=255
Reply from 24.113.58.1: bytes=32 time=13ms TTL=255
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=8ms TTL=255
Reply from 24.113.58.1: bytes=32 time=11ms TTL=255
Reply from 24.113.58.1: bytes=32 time=12ms TTL=255
Reply from 24.113.58.1: bytes=32 time=29ms TTL=255
Reply from 24.113.58.1: bytes=32 time=9ms TTL=255
Reply from 24.113.58.1: bytes=32 time=16ms TTL=255
Reply from 24.113.58.1: bytes=32 time=10ms TTL=255
Reply from 24.113.58.1: bytes=32 time=10ms TTL=255
Reply from 24.113.58.1: bytes=32 time=15ms TTL=255
Ping statistics for 24.113.58.1:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 29ms, Average = 13ms |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| Thanks Chpalmer. I wasn't able to get to a pc last night, but that didn't look to bad pinging from your side. If I have any problems tonight I'll ping it and see what happens.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
0zero01
join:2000-08-01
Port Orchard, WA
·wavebroadband
| Beggining to be an every evening occurence.
Microsoft Windows XP [Version 5.1.2600]
Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:
Reply from 209.131.36.158: bytes=32 time=35ms TTL=52
Reply from 209.131.36.158: bytes=32 time=36ms TTL=52
Reply from 209.131.36.158: bytes=32 time=32ms TTL=52
Reply from 209.131.36.158: bytes=32 time=55ms TTL=52
Reply from 209.131.36.158: bytes=32 time=198ms TTL=52
Reply from 209.131.36.158: bytes=32 time=35ms TTL=53
Reply from 209.131.36.158: bytes=32 time=79ms TTL=52
Request timed out.
Reply from 209.131.36.158: bytes=32 time=52ms TTL=52
Reply from 209.131.36.158: bytes=32 time=52ms TTL=52
Reply from 209.131.36.158: bytes=32 time=60ms TTL=52
Reply from 209.131.36.158: bytes=32 time=57ms TTL=52
Reply from 209.131.36.158: bytes=32 time=159ms TTL=53
Reply from 209.131.36.158: bytes=32 time=43ms TTL=52
Reply from 209.131.36.158: bytes=32 time=59ms TTL=53
Reply from 209.131.36.158: bytes=32 time=61ms TTL=52
Reply from 209.131.36.158: bytes=32 time=54ms TTL=52
Reply from 209.131.36.158: bytes=32 time=35ms TTL=52
Reply from 209.131.36.158: bytes=32 time=34ms TTL=52
Reply from 209.131.36.158: bytes=32 time=38ms TTL=52
Reply from 209.131.36.158: bytes=32 time=41ms TTL=52
Reply from 209.131.36.158: bytes=32 time=37ms TTL=53
Reply from 209.131.36.158: bytes=32 time=36ms TTL=52
Reply from 209.131.36.158: bytes=32 time=73ms TTL=53
Reply from 209.131.36.158: bytes=32 time=150ms TTL=52
Reply from 209.131.36.158: bytes=32 time=286ms TTL=52
Reply from 209.131.36.158: bytes=32 time=56ms TTL=52
Reply from 209.131.36.158: bytes=32 time=34ms TTL=52
Reply from 209.131.36.158: bytes=32 time=36ms TTL=53
Reply from 209.131.36.158: bytes=32 time=37ms TTL=52
Reply from 209.131.36.158: bytes=32 time=42ms TTL=53
Reply from 209.131.36.158: bytes=32 time=38ms TTL=52
Reply from 209.131.36.158: bytes=32 time=41ms TTL=52
Ping statistics for 209.131.36.158:
Packets: Sent = 33, Received = 32, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 286ms, Average = 65ms
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
