Wave Broadband > [WA] 10%+ Packet Loss in Kitsap

[WA] 10%+ Packet Loss in Kitsap

Ping statistics for 74.125.67.100:
    Packets: Sent = 46, Received = 37, Lost = 9 (19% loss),
Approximate round trip times in milli-seconds:
    Minimum = 85ms, Maximum = 159ms, Average = 102ms

C:\Users\Drew>pathping 4.2.2.2

Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
  0  Wolfsheim [192.168.1.38]
  1  wrt-apbridge [192.168.1.1]
  2     *     24-113-110-1.wavecable.com [24.113.110.1]
  3  24-113-127-41.wavecable.com [24.113.127.41]
  4  64.146.249.93
  5  srp2-0.wtn-cor0.noanet.net [66.119.192.17]
  6     *     ge-6-20.car3.Seattle1.Level3.net [4.71.152.141]
  7     *     ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]
  8  ae-1-100.ebr1.Seattle1.Level3.net [4.69.132.17]
  9  ae-7.ebr2.SanJose1.Level3.net [4.69.132.49]
 10  ae-72-72.csw2.SanJose1.Level3.net [4.69.134.214]
 11  ge-11-0.core1.SanJose1.Level3.net [4.68.123.38]
 12  vnsc-bak.sys.gtei.net [4.2.2.2]

Computing statistics for 300 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Wolfsheim [192.168.1.38]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  wrt-apbridge [192.168.1.1]
                               12/ 100 = 12%   |
  2   23ms    17/ 100 = 17%     5/ 100 =  5%  24-113-110-1.wavecable.com [24.113
.110.1]
                                0/ 100 =  0%   |
  3   20ms    17/ 100 = 17%     5/ 100 =  5%  24-113-127-41.wavecable.com [24.11
3.127.41]
                                0/ 100 =  0%   |
  4   20ms    18/ 100 = 18%     6/ 100 =  6%  64.146.249.93
                                0/ 100 =  0%   |
  5   24ms    18/ 100 = 18%     6/ 100 =  6%  srp2-0.wtn-cor0.noanet.net [66.119
.192.17]
                                0/ 100 =  0%   |
  6   35ms    13/ 100 = 13%     1/ 100 =  1%  ge-6-20.car3.Seattle1.Level3.net [
4.71.152.141]
                                0/ 100 =  0%   |
  7   27ms    12/ 100 = 12%     0/ 100 =  0%  ae-32-52.ebr2.Seattle1.Level3.net
[4.68.105.62]
                                7/ 100 =  7%   |
  8   27ms    23/ 100 = 23%     4/ 100 =  4%  ae-1-100.ebr1.Seattle1.Level3.net
[4.69.132.17]
                                0/ 100 =  0%   |
  9   44ms    20/ 100 = 20%     1/ 100 =  1%  ae-7.ebr2.SanJose1.Level3.net [4.6
9.132.49]
                                0/ 100 =  0%   |
 10   46ms    20/ 100 = 20%     1/ 100 =  1%  ae-72-72.csw2.SanJose1.Level3.net
[4.69.134.214]
                                0/ 100 =  0%   |
 11   61ms    28/ 100 = 28%     9/ 100 =  9%  ge-11-0.core1.SanJose1.Level3.net
[4.68.123.38]
                                0/ 100 =  0%   |
 12   41ms    19/ 100 = 19%     0/ 100 =  0%  vnsc-bak.sys.gtei.net [4.2.2.2]

Trace complete.

Called tech support to see if they had any info on the outage and of course not.

"I remember hearing about something in your area just a little bit ago. Let me check the outage board."

hold...

"Nope, nothing on the board anymore so we'll treat this as a separate issue..."

*sigh*

"I can have him come sometime on Saturday to take a look."

*sigh*

Ping statistics for 74.125.53.100:
    Packets: Sent = 230, Received = 168, Lost = 62 (26% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 178ms, Average = 33ms

:rolleyes:

reply to drew
Ping statistics for 4.2.2.2:
Packets: Sent = 2520, Received = 2159, Lost = 361 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 216ms, Average = 49ms

Need I say more?
--
Come play Mafia! | My Picture Blog

reply to drew
Welcome to the world of wave, where at any given moment you could walk faster than the bandwidth your paying for!

I've been with wave from the beginning.

reply to drew

So not just me eh?

reply to drew
Ping statistics for 72.14.213.104:
Packets: Sent = 202, Received = 173, Lost = 29 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 153ms, Average = 30ms

Connection is horrible, down right unusable at night. Has been like this for the last 2 weeks.

reply to drew
Getting 10% to 40% here in Silverdale using Ping Plotter to 4.2.2.2. I called Wave, and of course the lady heard of no problem at all. She said she would send a tech to my house on wednesday. LOL

If Wave doesn't get their $hit together, I'm gonna go with another provider.

reply to drew

reply to drew
I would be concerned that they are blocking UDP ports nothing that uses UDP will work I cannot use ECHOLINK or IDENT (mIRC) I am upset with that.
--
The following statement is true...
The preceding statement was false!!--George Carlin

I haven't had problems with ident on my stuff.

Is this new? It's been a couple weeks.

reply to drew
Can you get Comcast in Port Orchard now?
I was under the impression when I moved here about 4 years ago that only Wave covered Port Orchard.

Location wise, I'm practically Olalla

reply to drew
i think it is a problem with the network setup...

reply to AD7BK
I use udp connections all the time...

You might check the settings on your router...
or even try another.

reply to drew
The packet loss was occuring on Noanet fiber and seemed to be affecting many users. Olypen used by my office was having the same issue...

1 1 ms 1 ms 1 ms firebox.airsignal.org [172.31.125.1]
2 10 ms 11 ms 10 ms 24.113.35.1
3 13 ms 10 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 14 ms 9 ms 13 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 12 ms 10 ms 12 ms ge-6-20.car3.Seattle1.Level3.net [4.71.152.141]
6 15 ms 13 ms 16 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]
7 33 ms 35 ms 36 ms ae-7.ebr2.SanJose1.Level3.net [4.69.132.49]
8 30 ms 30 ms 36 ms ae-62-62.csw1.SanJose1.Level3.net [4.69.134.210]
9 32 ms 29 ms 39 ms ge-10-0.core1.SanJose1.Level3.net [4.68.123.6]
10 30 ms 29 ms 30 ms vnsc-lc.sys.gtei.net [4.2.2.3]

Trace complete.

Good now though.

As I explained to the rep last night, it only happens really in the evenings.

They keep wanting to roll a truck even with acknowledged other reports.
--
Come play Mafia! | My Picture Blog

reply to chpalmer

C:\Users\Drew>ping -t 4.2.2.2 -w 350

Pinging 4.2.2.2 with 32 bytes of data:
Reply from 4.2.2.2: bytes=32 time=45ms TTL=55
Reply from 4.2.2.2: bytes=32 time=30ms TTL=55
Reply from 4.2.2.2: bytes=32 time=37ms TTL=55
Reply from 4.2.2.2: bytes=32 time=35ms TTL=55
Reply from 4.2.2.2: bytes=32 time=40ms TTL=55
Reply from 4.2.2.2: bytes=32 time=45ms TTL=55
Reply from 4.2.2.2: bytes=32 time=52ms TTL=55
Reply from 4.2.2.2: bytes=32 time=34ms TTL=55
Reply from 4.2.2.2: bytes=32 time=30ms TTL=55
Reply from 4.2.2.2: bytes=32 time=34ms TTL=55
Reply from 4.2.2.2: bytes=32 time=52ms TTL=55
Reply from 4.2.2.2: bytes=32 time=47ms TTL=55
Reply from 4.2.2.2: bytes=32 time=38ms TTL=55
Reply from 4.2.2.2: bytes=32 time=34ms TTL=55
Reply from 4.2.2.2: bytes=32 time=38ms TTL=55
Reply from 4.2.2.2: bytes=32 time=40ms TTL=55
Reply from 4.2.2.2: bytes=32 time=37ms TTL=55
Reply from 4.2.2.2: bytes=32 time=42ms TTL=55
Reply from 4.2.2.2: bytes=32 time=31ms TTL=55
Reply from 4.2.2.2: bytes=32 time=40ms TTL=55
Reply from 4.2.2.2: bytes=32 time=32ms TTL=55
Reply from 4.2.2.2: bytes=32 time=33ms TTL=55
Reply from 4.2.2.2: bytes=32 time=35ms TTL=55
Reply from 4.2.2.2: bytes=32 time=38ms TTL=55
Reply from 4.2.2.2: bytes=32 time=37ms TTL=55
Reply from 4.2.2.2: bytes=32 time=43ms TTL=55
Request timed out.
Reply from 4.2.2.2: bytes=32 time=47ms TTL=55
Reply from 4.2.2.2: bytes=32 time=42ms TTL=55
Reply from 4.2.2.2: bytes=32 time=38ms TTL=55
Reply from 4.2.2.2: bytes=32 time=58ms TTL=55
Request timed out.
Request timed out.
Reply from 4.2.2.2: bytes=32 time=31ms TTL=55
Reply from 4.2.2.2: bytes=32 time=40ms TTL=55
Request timed out.
Reply from 4.2.2.2: bytes=32 time=55ms TTL=55
Reply from 4.2.2.2: bytes=32 time=58ms TTL=55
Reply from 4.2.2.2: bytes=32 time=42ms TTL=55
Request timed out.
Reply from 4.2.2.2: bytes=32 time=39ms TTL=55
Reply from 4.2.2.2: bytes=32 time=31ms TTL=55
Request timed out.
Reply from 4.2.2.2: bytes=32 time=36ms TTL=55
Reply from 4.2.2.2: bytes=32 time=31ms TTL=55
Reply from 4.2.2.2: bytes=32 time=29ms TTL=55
Reply from 4.2.2.2: bytes=32 time=33ms TTL=55
Reply from 4.2.2.2: bytes=32 time=57ms TTL=55
Reply from 4.2.2.2: bytes=32 time=43ms TTL=55
Request timed out.
Request timed out.
Reply from 4.2.2.2: bytes=32 time=41ms TTL=55
Reply from 4.2.2.2: bytes=32 time=43ms TTL=55
Reply from 4.2.2.2: bytes=32 time=42ms TTL=55
Reply from 4.2.2.2: bytes=32 time=41ms TTL=55
Reply from 4.2.2.2: bytes=32 time=52ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 4.2.2.2: bytes=32 time=59ms TTL=55
Reply from 4.2.2.2: bytes=32 time=54ms TTL=55
Reply from 4.2.2.2: bytes=32 time=54ms TTL=55
Reply from 4.2.2.2: bytes=32 time=44ms TTL=55

Ping statistics for 4.2.2.2:
    Packets: Sent = 63, Received = 52, Lost = 11 (17% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 59ms, Average = 41ms
Control-C

C:\Users\Drew>pathping 4.2.2.2 -q 25

Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
  0  Wolfsheim [192.168.1.38]
  1  wrt-apbridge [192.168.1.1]
  2  24-113-110-1.wavecable.com [24.113.110.1]
  3  24-113-127-41.wavecable.com [24.113.127.41]
  4  64.146.249.93
  5  srp2-0.wtn-cor0.noanet.net [66.119.192.17]
  6     *     ge-6-20.car3.Seattle1.Level3.net [4.71.152.141]
  7  ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]
  8  ae-1-100.ebr1.Seattle1.Level3.net [4.69.132.17]
  9  ae-7.ebr2.SanJose1.Level3.net [4.69.132.49]
 10  ae-72-72.csw2.SanJose1.Level3.net [4.69.134.214]
 11  ge-11-0.core1.SanJose1.Level3.net [4.68.123.38]
 12  vnsc-bak.sys.gtei.net [4.2.2.2]

Computing statistics for 75 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Wolfsheim [192.168.1.38]
                                0/  25 =  0%   |
  1    1ms     0/  25 =  0%     0/  25 =  0%  wrt-apbridge [192.168.1.1]
                                0/  25 =  0%   |
  2   60ms     3/  25 = 12%     3/  25 = 12%  24-113-110-1.wavecable.com [24.113.110.1]
                                0/  25 =  0%   |
  3   57ms     2/  25 =  8%     2/  25 =  8%  24-113-127-41.wavecable.com [24.113.127.41]
                                0/  25 =  0%   |
  4   44ms     0/  25 =  0%     0/  25 =  0%  64.146.249.93
                                1/  25 =  4%   |
  5   42ms     5/  25 = 20%     4/  25 = 16%  srp2-0.wtn-cor0.noanet.net [66.119.192.17]
                                0/  25 =  0%   |
  6   59ms     1/  25 =  4%     0/  25 =  0%  ge-6-20.car3.Seattle1.Level3.net [4.71.152.1 41]
                                0/  25 =  0%   |
  7   52ms     2/  25 =  8%     1/  25 =  4%  ae-32-52.ebr2.Seattle1.Level3.net [4.68.105. 62]
                                0/  25 =  0%   |
  8   60ms     1/  25 =  4%     0/  25 =  0%  ae-1-100.ebr1.Seattle1.Level3.net [4.69.132. 17]
                                0/  25 =  0%   |
  9   70ms     3/  25 = 12%     2/  25 =  8%  ae-7.ebr2.SanJose1.Level3.net [4.69.132.49]
                                0/  25 =  0%   |
 10   88ms     4/  25 = 16%     3/  25 = 12%  ae-72-72.csw2.SanJose1.Level3.net [4.69.134. 214]
                                0/  25 =  0%   |
 11   82ms     1/  25 =  4%     0/  25 =  0%  ge-11-0.core1.SanJose1.Level3.net [4.68.123. 38]
                                2/  25 =  8%   |
 12   91ms     3/  25 = 12%     0/  25 =  0%  vnsc-bak.sys.gtei.net [4.2.2.2]

Trace complete.