Peak time latency issues

Forums › New Zealand Broadband › Peak time latency issues

Stasis007

58 posts

Master Geek

Topic # 85851 27-Jun-2011 00:56

First up, I've always found Woosh's wired ADSL service to be extremely good, and I've enjoyed better international pings than any other ISP I've used here or in Australia.

That was until last week...

Now I'm getting horrible pings between about 7pm and 11:30pm; at 11:30 it magically becomes awesome again, which leads me to suspect I'm either being shaped, or Woosh has taken too on many customers and we're all trying to squeeze through at the same time.

I didn't think to screen shot, but pinging "woosh.co.nz" was returning 140ms average pings, compared to 28ms now and normally. Pingtest.net was showing similar results.

A fortnight ago I wouldn't choose to switch from Woosh to any other ISP, I was thoroughly satisfied with their service. Now, if this is working as intended, I'm unable to use the internet in the way that I need to, so will need to find an alternate provider.

Anyone else experienced this? It's definitely something new, I've had no issues for the last 6 months or so and now I'm getting this every night between dinnertime and 11:30pm.

johnr

19282 posts

Uber Geek
+1 received by user: 2600
Inactive user

Reply # 486251 27-Jun-2011 00:58

Have you logged a fault ticket with Woosh and showed them any trace routes?

Stasis007

58 posts

Master Geek

Reply # 486254 27-Jun-2011 01:18

No, not yet. Kinda hoping to hear that other people are having similar issues before girding my loins and doing battle with tech support...

Stasis007

58 posts

Master Geek

Reply # 487091 28-Jun-2011 19:53

Emailed Woosh with my complaint and tracerts. Waiting to hear back.

This is what I'm seeing: between 23:00 and 18:00 it looks like this:

Pinging woosh.co.nz [202.74.207.16] with 32 bytes of data:

Reply from 202.74.207.16: bytes=32 time=31ms TTL=124
Reply from 202.74.207.16: bytes=32 time=28ms TTL=124
Reply from 202.74.207.16: bytes=32 time=29ms TTL=124
Reply from 202.74.207.16: bytes=32 time=32ms TTL=124

Ping statistics for 202.74.207.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 32ms, Average = 30ms

Tracing route to woosh.co.nz [202.74.207.16]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms mygateway1.ar7 [10.1.1.1]
2 39 ms 36 ms 33 ms lns3.sky.woosh.net.nz [202.74.206.9]
3 * * * Request timed out.
4 84 ms 82 ms 72 ms 202.74.207.182
5 91 ms 88 ms 97 ms woosh.co.nz [202.74.207.16]

Trace complete.

And, for the last 2 weeks, between 18:00 and 23:00 it looks like this:

Pinging woosh.co.nz [202.74.207.16] with 32 bytes of data:
Reply from 202.74.207.16: bytes=32 time=158ms TTL=124
Reply from 202.74.207.16: bytes=32 time=138ms TTL=124
Reply from 202.74.207.16: bytes=32 time=161ms TTL=124
Reply from 202.74.207.16: bytes=32 time=161ms TTL=124

Ping statistics for 202.74.207.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 138ms, Maximum = 161ms, Average = 154ms

Tracing route to woosh.co.nz [202.74.207.16]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms mygateway1.ar7 [10.1.1.1]
2 195 ms 140 ms 177 ms lns3.sky.woosh.net.nz [202.74.206.9]
3 * * * Request timed out.
4 136 ms 129 ms 152 ms 202.74.207.182
5 143 ms 140 ms 150 ms woosh.co.nz [202.74.207.16]

Trace complete.

I hadn't had any issues for the last 6 months, it just started 2 weeks ago and is consistently bad
every night during 'peak' hours.

I've tried the 'isolation test' etc, and much of the time my wired router is the only device connected
to the phone line. I make sure the (filtered) phone is unplugged when I'm gaming anyways.
No alarm/sky/whatever connected.

MLabs' Shaperprobe doesn't detect any traffic shaping, for what it's worth. And the Glasnost test
doesn't detect any P2P shaping.

Could it be cabinet congestion possibly? I live in Christchurch, and it's possible that there's been
cabinet and/or exchange damage, although the quality degraded well after the significant shakes.
Anyway I can test that from my end?

If it's due to network congestion caused by over-subscribing, are there grounds to be released from
contract under a Quality of Service complaint? Considering the service that I'm receiving now isn't the
service that I expected when I signed up? I signed a new contract when I moved house, so I was
well aware of how good their service was prior to signing.

I realize that ISP's aren't 'required' to provide excellent service, and network congestion is part
and parcel of New Zealand's crappy internet access, but being unable to online game between 6pm
and 11pm is a deal breaker for me.

And finally this may well not be Woosh's problem, like I'd mentioned, I've found my speed and latency
to be excellent up 'til now. Far, far better than any of my friends with other NZ ISPs. I certainly hoping
that it's fixable and I'll get back to enjoying my connection again.

Ragnor

8027 posts

Uber Geek
+1 received by user: 387

Trusted

Subscriber

Reply # 487619 30-Jun-2011 00:35

If you don't get much of a response try pm'ing this guy on GP Forums that works for Woosh and has helped out users over there in the past

http://www.gpforums.co.nz/showthread.php?s=&postid=8127729&highlight=woosh#post8127729

Stasis007

58 posts

Master Geek

Reply # 490266 6-Jul-2011 21:14

Thanks for the tip Ragnor

So, a few days after contacting Gambit, and receiving the awesome customer service that I'm starting to expect from Woosh, I'm now on a EUBA connection and enjoying rock-solid internet :)

This is at 20:40 today:
Tracing route to woosh.co.nz [202.74.207.16]
over a maximum of 30 hops:

1 2 24 ms 24 ms 24 ms lns4.sky.woosh.net.nz [202.74.206.10]
3 * * * Request timed out.
4 25 ms 26 ms 25 ms 202.74.207.182
5 25 ms 25 ms 26 ms woosh.co.nz [202.74.207.16]

Trace complete.

Pinging woosh.co.nz [202.74.207.16] with 32 bytes of data:
Reply from 202.74.207.16: bytes=32 time=24ms TTL=124
Reply from 202.74.207.16: bytes=32 time=25ms TTL=124
Reply from 202.74.207.16: bytes=32 time=25ms TTL=124
Reply from 202.74.207.16: bytes=32 time=25ms TTL=124

Ping statistics for 202.74.207.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 25ms

Best thing is the stability. I've been Speedtesting, Pinging and Tracert'ing a lot over the last 24 hours
and getting basically identical results.

And enjoying a stable 140-180 latency in WoW, no tunneling.

Thanks Woosh! Got to love a happy ending.

sbiddle

26953 posts

Uber Geek
+1 received by user: 6400

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 490276 6-Jul-2011 21:31

EUBA is a million times better than the old UBA/UBS connections.

I just wish people who keep of repeating the same old "broadband in NZ sux" and "Telecom's 45kbps handovers suck" would at least look around at the options and ISP's who offer alternatives and are migrating customers to EUBA plans that in effect removes all handover contention.

Gamgetta

14 posts

Geek
+1 received by user: 2

Reply # 490986 8-Jul-2011 11:01

Stasis007: Thanks for the tip Ragnor

So, a few days after contacting Gambit, and receiving the awesome customer service that I'm starting to expect from Woosh, I'm now on a EUBA connection and enjoying rock-solid internet :)

This is at 20:40 today:
Tracing route to woosh.co.nz [202.74.207.16]
over a maximum of 30 hops:

1 2 24 ms 24 ms 24 ms lns4.sky.woosh.net.nz [202.74.206.10]
3 * * * Request timed out.
4 25 ms 26 ms 25 ms 202.74.207.182
5 25 ms 25 ms 26 ms woosh.co.nz [202.74.207.16]

Trace complete.

Pinging woosh.co.nz [202.74.207.16] with 32 bytes of data:
Reply from 202.74.207.16: bytes=32 time=24ms TTL=124
Reply from 202.74.207.16: bytes=32 time=25ms TTL=124
Reply from 202.74.207.16: bytes=32 time=25ms TTL=124
Reply from 202.74.207.16: bytes=32 time=25ms TTL=124

Ping statistics for 202.74.207.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 25ms

Best thing is the stability. I've been Speedtesting, Pinging and Tracert'ing a lot over the last 24 hours
and getting basically identical results.

And enjoying a stable 140-180 latency in WoW, no tunneling.

Thanks Woosh! Got to love a happy ending.

Glad to hear your connection is a whole lot better :) Glad i could help.