Peak Hour Slowdowns in WA in Wave Broadband

Re: Peak Hour Slowdowns in WA

Wed, 31 Dec 2008 02:30:03 EDT

drew :

maybe they fixed it..

Tracing route to dslreports.com [209.123.109.175]over a maximum of 30 hops:   1     1 ms     1 ms    <1 ms  192.168.1.1  2    15 ms    12 ms    11 ms  24-113-100-1.wavecable.com [24.113.100.1]  3    12 ms    12 ms    10 ms  24-113-127-41.wavecable.com [24.113.127.41]  4    16 ms    13 ms    14 ms  ip-64-184-129-237.noanet.net [64.184.129.237]  5    15 ms    14 ms    13 ms  ge-6-20.car3.Seattle1.Level3.net [4.71.152.141]   6    21 ms    16 ms    17 ms  ae-32-54.ebr2.Seattle1.Level3.net [4.68.105.126]   7    46 ms    56 ms    50 ms  ae-2.ebr2.Denver1.Level3.net [4.69.132.54]  8    64 ms    64 ms    63 ms  ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]  9    67 ms    67 ms    65 ms  ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]  10    81 ms    82 ms    83 ms  ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]  11   103 ms    87 ms    87 ms  ae-4-4.ebr2.Newark1.Level3.net [4.69.132.102] 12    88 ms    88 ms    87 ms  ae-21-56.car1.Newark1.Level3.net [4.68.99.165] 13   105 ms    95 ms    97 ms  4.79.189.74 14    97 ms    94 ms    94 ms  0.e1-4.tbr2.oct.nac.net [209.123.10.126] 15    99 ms   103 ms    98 ms  vlan808.esd1.oct.nac.net [209.123.10.42] 16    95 ms    99 ms    96 ms  www.dslreports.com [209.123.109.175] Trace complete.

Re: Peak Hour Slowdowns in WA

Tue, 30 Dec 2008 23:00:03 EDT

chpalmer : Tracing route to olypen.com [208.200.248.3]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Router [172.31.125.1]
2 12 ms 13 ms 12 ms 24-113-123-1.wavecable.com [24.113.123.1]
3 14 ms 10 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 316 ms 308 ms 310 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 938 ms 647 ms 657 ms olypen-cust.fa6-7.978.oly-cor0.noanet.net [64.146.232.238]
6 617 ms 615 ms 623 ms r2.olypen.com [208.238.204.2]
7 618 ms 619 ms 604 ms webhosting.olypen.com [208.200.248.3]

Trace complete.

Re: Peak Hour Slowdowns in WA

Tue, 30 Dec 2008 22:56:06 EDT

chpalmer : Me too... :(

Tracing route to www.l.google.com [209.85.171.103]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router [172.31.125.1]
2 10 ms 11 ms 12 ms 24-113-123-1.wavecable.com [24.113.123.1]
3 13 ms 10 ms 12 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 296 ms 293 ms 287 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 277 ms 278 ms 273 ms six.sea01.google.com [198.32.180.17]
6 275 ms 283 ms 274 ms 209.85.255.61
7 285 ms 297 ms 296 ms 72.14.239.12
8 * * * Request timed out.
9 300 ms 296 ms 306 ms 216.239.48.141
10 294 ms 308 ms 310 ms 209.85.251.125
11 326 ms 311 ms 298 ms 74.125.30.6
12 299 ms 300 ms 294 ms cg-in-f103.google.com [209.85.171.103]

Trace complete.

Re: Peak Hour Slowdowns in WA

Tue, 30 Dec 2008 22:31:43 EDT

anon : Here in Port Orchard it's been pretty horrible since the smallish snow storm last week.

Here is the tracert I did just a little bit ago.

Still a wee bit surprised they've been in business this long.

C:\Users\*****>tracert www.google.com

Tracing route to www.l.google.com [209.85.171.147]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 9 ms 9 ms 11 ms 24-113-102-1.wavecable.com [24.113.102.1]
3 10 ms 9 ms 9 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 230 ms 258 ms 219 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 227 ms 222 ms 223 ms six.sea01.google.com [198.32.180.17]
6 217 ms 232 ms 303 ms 209.85.255.63
7 226 ms 229 ms 226 ms 209.85.249.17
8 234 ms 228 ms 229 ms 216.239.46.212
9 224 ms 230 ms 230 ms 64.233.174.125
10 231 ms 231 ms 235 ms 209.85.251.133
11 250 ms 236 ms 236 ms 74.125.31.130
12 214 ms 223 ms 226 ms cg-in-f147.google.com [209.85.171.147]

Trace complete.

Re: Peak Hour Slowdowns in WA

Tue, 30 Dec 2008 22:23:54 EDT
anon :

In Port Angeles WA

Have had issues since 6pm this evening, apparently the a fiber cable in Kirkland broke...meh, whatever. They are sending a tech out on Friday anyway.

Re: Peak Hour Slowdowns in WA

Tue, 30 Dec 2008 11:41:07 EDT
drew : I'm back down below 2mbps in the evening.

Re: Peak Hour Slowdowns in WA

Tue, 30 Dec 2008 00:48:25 EDT
gtojim : Speeds in Concord Ca. Astound is owned by Wave. I won't post any more speeds for awhile.

Re: Peak Hour Slowdowns in WA

Tue, 21 Oct 2008 12:11:34 EDT
drew : Oh, I was logging bi-weekly phone calls.

Re: Peak Hour Slowdowns in WA

Tue, 21 Oct 2008 12:10:36 EDT
chpalmer :
And do complain! They wont know there is an issue if everyone is quiet...

Re: Peak Hour Slowdowns in WA

Tue, 21 Oct 2008 11:59:24 EDT
drew : My problems have mysteriously vanished.

I know it sounds absolutely insane, but if you're using a router, power down the modem, ethernet it to a computer and turn the modem back on. See how your speeds are. Then power down the modem and the router and plug the WAN on the router back into the modem. Power the modem up first then the router. See how things go.

I'd rebooted my modem numerous times, especially when I was re-wiring my house, since the first time I experienced (noticed is more like it) the slowdowns and it never helped. This last time though was magic it seems.

Re: Peak Hour Slowdowns in WA

Tue, 21 Oct 2008 11:12:46 EDT
anon : It has gotten much worse here PO. I'm on 10/1 and never got over 1100 last night and some were 100 down. Web pages just wouldn't load or took forever, I gave up. Everything is fine at 8am.

Re: Peak Hour Slowdowns in WA

Tue, 21 Oct 2008 00:32:45 EDT
chpalmer : Just did one here from the Gorst area... To give you something to compare to.

Try this also. C:>ping -n 50 192.168.100.1 and see if you get any packet loss...

Good Luck!

While a couple of downloads happening...-

C:\>tracert dslreports.com

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms My Firewall [**.**.**.**]
2 14 ms 10 ms 8 ms 24-113-123-1.wavecable.com [24.113.123.1]
3 18 ms 13 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 16 ms 18 ms 22 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 20 ms 20 ms 15 ms 64.209.96.85
6 86 ms 88 ms 81 ms tiscali-1.ar1.SJC2.gblx.net [208.50.13.26]
7 108 ms 105 ms 110 ms 89.149.186.206
8 104 ms 109 ms 107 ms 213.200.66.202
9 109 ms 107 ms 104 ms 0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
10 103 ms 108 ms 105 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
11 110 ms 109 ms 106 ms vlan808.esd1.oct.nac.net [209.123.10.42]
12 114 ms 106 ms 107 ms www.dslreports.com [209.123.109.175]

Trace complete.

Re: Peak Hour Slowdowns in WA

Tue, 21 Oct 2008 00:04:40 EDT
anon : I've been having some serious issues this evening which prompted me to search for a wavebroadband forum. Trace route is reporting several hops with 33% packet loss. I'll be contacting Wave is this continues.

In Port Orchard

Re: Peak Hour Slowdowns in WA

Wed, 15 Oct 2008 01:17:29 EDT
gtojim : From the lack of posts most people must be pretty happy with the service. I'm in California.

Re: Peak Hour Slowdowns in WA

Tue, 30 Sep 2008 20:23:13 EDT
drew :

hmmm...

--
Come play Mafia!

Re: Peak Hour Slowdowns in WA

Tue, 30 Sep 2008 00:45:34 EDT
drew : Best yet.

--
Come play Mafia!

Re: Peak Hour Slowdowns in WA

Sun, 28 Sep 2008 01:18:41 EDT
drew :

Surprise surprise.
--
Come play Mafia!

Re: Peak Hour Slowdowns in WA

Thu, 04 Sep 2008 03:04:54 EDT
gtojim : I live in Concord California, just changed to the 6mb/1mb plan from 10md/1mb. No difference in speed during evening hours, saves me $10 per month.

Re: Peak Hour Slowdowns in WA

Thu, 04 Sep 2008 02:02:55 EDT
drew :

Imagine that...

Re: Peak Hour Slowdowns in WA

Mon, 23 Jun 2008 10:41:51 EDT
Badluckguy : I too have been experiencing slowdowns in the evening. I have the 10/1 package and usually get 4MB down unless it's early in the AM. I then get 10+.

Oh yea, I'm also in the Bremerton area.

Peak Hour Slowdowns in WA

Mon, 23 Jun 2008 00:50:24 EDT
drew : Just as a FYI, I talked to a super nice guy at Wave this evening.

I mentioned that for about the past 1.5 months, I've gotten ~1.5mbps during peak hours instead of the 6mbps I get during the day. I also mentioned there were other people in the area experiencing the same issue. I mentioned DSLR and he'd said that he'd put a note in the ticket for his supervisor to come read the posts.

So, go ahead and post here if you've got some problems.

Here's mine from tonight: