Peak time latency jumping to over 700 ms - Milson, Palmerston North

Forums › Vodafone New Zealand (including Vodafone, WxC, Farmside) › Peak time latency jumping to over 700 ms - Milson, Palmerston North

1 | 2 | 3

240 posts

Master Geek

#1168556 4-Nov-2014 15:14

Yes it could be, but it could also be 100% related.
I have been sending graphs, times, traceroutes, and MTR reports through to your team for almost two months now without any apparent progress.
I have been promised regular phone call / text message updates and then never heard back from the person.
I'm simply trying to add as much information as I possibly can to aid with diagnosis and fault resolution.

Cheers,
Nigel

icepicknz

309 posts

Ultimate Geek

Trusted

#1168567 4-Nov-2014 15:24

Its a common occurance that chorus dont know the congestion exists, we know the right people to talk to and even tell them what commands to run to prove the issue.
Once the agree there is a congestion issue of some sort it goes up the chain and the RFS date is usually 6-12 weeks out before repair as they have to order new cards which take 4-5 weeks for delivery.

Havlock North currently has congestion and has done for a few months, latency goes to 600ms from 5pm till 11pm, though we were advised that a week ago new 10gigs were provisioned and the problem should be gone.
Unfortunately this isnt the case and they are still investigating, I suspect the network didnt rebalanced and we're still on a congested path.

With the new proposed broadband metrics chorus advised a couple of weeks ago, there is little you can do to speed them up as it's not a fault if you can get 64k across your circuit

Barry Murphy
ISPMap - New Zealand ISP map
Vibe Communications LTD - Business ISP and Wholesale Carrier

Any comments made by myself don't reflect the views of my employer, they are mine and mine alone

icepicknz

309 posts

Ultimate Geek

Trusted

#1168575 4-Nov-2014 15:29

Here is the Havlock congestion for comparison...

Barry Murphy
ISPMap - New Zealand ISP map
Vibe Communications LTD - Business ISP and Wholesale Carrier

Any comments made by myself don't reflect the views of my employer, they are mine and mine alone

icepicknz

309 posts

Ultimate Geek

Trusted

#1168577 4-Nov-2014 15:33

Actually looking at your smokeping and comparing to mine, I would say your circuit transits the same path as mine.
Ask VF to compare your case to SD1804202 and ask them to see if the EPIPE/VLL take the same path in any way.

cheers

Barry Murphy
ISPMap - New Zealand ISP map
Vibe Communications LTD - Business ISP and Wholesale Carrier

Any comments made by myself don't reflect the views of my employer, they are mine and mine alone

nbroad

240 posts

Master Geek

#1168590 4-Nov-2014 15:38

That's the most comprehensive and informative response I have received in the 1.5 months that I have had my fault logged with Vodafone. Thanks for that Barry.
All I have had is "have you rebooted your modem" and "we have had monitoring on your line and it's fine".

Your graph looks almost identical to mine.

All I need to know is where this is at... if congestion has been identified and there is work underway to resolve it then I'll be a happy chap :-)

Cheers,
Nigel

johnr

19282 posts

Uber Geek
Inactive user

#1168591 4-Nov-2014 15:38

This seems to be a issue on the Chorus side not Vodafone, See Snap thread

http://www.geekzone.co.nz/forums.asp?forumid=90&topicid=154574

nbroad

240 posts

Master Geek

#1169090 5-Nov-2014 10:17

johnr: This seems to be a issue on the Chorus side not Vodafone, See Snap thread

http://www.geekzone.co.nz/forums.asp?forumid=90&topicid=154574

Reminds me of the radio ad for our local ISP... Palmerstonians will know it "not my problem".
So I can refer back to your statement in future comms with your people?
Considering the end customer cannot talk with Chorus directly, should I be expecting a call from my ISP to let me know that an issue has been confirmed and what the next steps are?
I have been aware of this issue for 2 months now and provided all the evidence and all I have been told is "please reboot your modem".
I was even asked by a Vodafone employee to walk up and down my street, knock on my neighbours doors and ask them if they were having the same problem.
Just a little frustrating.

Cheers.

johnr

19282 posts

Uber Geek
Inactive user

#1169155 5-Nov-2014 11:27

nbroad:
johnr: This seems to be a issue on the Chorus side not Vodafone, See Snap thread

http://www.geekzone.co.nz/forums.asp?forumid=90&topicid=154574

Reminds me of the radio ad for our local ISP... Palmerstonians will know it "not my problem".
So I can refer back to your statement in future comms with your people?
Considering the end customer cannot talk with Chorus directly, should I be expecting a call from my ISP to let me know that an issue has been confirmed and what the next steps are?
I have been aware of this issue for 2 months now and provided all the evidence and all I have been told is "please reboot your modem".
I was even asked by a Vodafone employee to walk up and down my street, knock on my neighbours doors and ask them if they were having the same problem.
Just a little frustrating.

Cheers.

If the speed meets or exceeds the regulated speeds / requirements set out by the comcom is it actually a fault?

nbroad

240 posts

Master Geek

#1169165 5-Nov-2014 11:43

johnr:
If the speed meets or exceeds the regulated speeds / requirements set out by the comcom is it actually a fault?

Are you trying to say that I should not have logged this as a fault?
If Vodafone advertise fast and reliable broadband, is that actually false advertising?

johnr

19282 posts

Uber Geek
Inactive user

#1169171 5-Nov-2014 11:54

nbroad:
johnr:
If the speed meets or exceeds the regulated speeds / requirements set out by the comcom is it actually a fault?

Are you trying to say that I should not have logged this as a fault?
If Vodafone advertise fast and reliable broadband, is that actually false advertising?

Ask that to the customers connected to congested Conklins cabinets and remember internet speed is regulated in NZ by the comcom

nbroad

240 posts

Master Geek

#1169359 5-Nov-2014 16:15

johnr:
nbroad:
johnr:
If the speed meets or exceeds the regulated speeds / requirements set out by the comcom is it actually a fault?

Are you trying to say that I should not have logged this as a fault?
If Vodafone advertise fast and reliable broadband, is that actually false advertising?

Ask that to the customers connected to congested Conklins cabinets and remember internet speed is regulated in NZ by the comcom

I'm well aware of the trials and tribulations of being connected to a rural Conklin believe you me.
I had a running commentary on the issue for over a year when I had a family member connected to one.

I'm not sure what point you are trying to make though when talking about the Commerce Commission in relation to the issue.
I'll ask the question again... Is this a fault?

nbroad

240 posts

Master Geek

#1169373 5-Nov-2014 16:19

It has kicked in early today - started at midday:

johnr

19282 posts

Uber Geek
Inactive user

#1169394 5-Nov-2014 16:50

Yes the performance you are getting is not what to be expected for the type of connection you are on,

toejam316

925 posts

Ultimate Geek

Trusted

#1169471 5-Nov-2014 18:29

One person supports this post

johnr:
nbroad:
johnr:
If the speed meets or exceeds the regulated speeds / requirements set out by the comcom is it actually a fault?

Are you trying to say that I should not have logged this as a fault?
If Vodafone advertise fast and reliable broadband, is that actually false advertising?

Ask that to the customers connected to congested Conklins cabinets and remember internet speed is regulated in NZ by the comcom

It's okay, the Conklin's are only a temporary measure, remember?

Anything I say is the ramblings of an ill informed, opinionated so-and-so, and not representative of any of my past, present or future employers, and is also probably best disregarded.

nbroad

240 posts

Master Geek

#1177773 18-Nov-2014 09:41

Hi,

It took 2 months, but this is now resolved and latency/speed is back to normal.
I wasn't given much detail as to what the problem was, apart from it being a Chorus fault.

Cheers.

1 | 2 | 3