cancel
Showing results for 
Search instead for 
Did you mean: 

Interleaving request to be turned ON

markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Interleaving request to be turned ON

 

I'm having issues with latency spikes at idle network load aswell as under full load. Here are my results with interleaving off. As you can see pings at idle (less than 20% saturation) are fluctuating between 20ms-50ms which is extremely jittery making VOIP and other latency sensitive services difficult to use. Latency at this amount of load should rarely spike if at all and should more or less stay at a solid 20ms. The second screen shows my latency at 100% line saturation where the latency just goes crazy. I have also included my line stats which show an SNR of 10.4/15 although line stats appear fine i would just like to document this as i expect i will need to have an engineer round and they will want to see how it all changes with interleaving turned on/off.

So can i have interleaving turned on please? I will post my results again once its turned on.

Thanks

idle-ping-qos-on.gifmaxed-ping-qos-on.gifline-stats.gif

11 REPLIES
Plusnet Help Team
Plusnet Help Team
Posts: 4,086
Thanks: 791
Fixes: 171
Registered: 25-03-2015

Re: Interleaving request to be turned ON

Hi @markb5000 I've applied interleaving to your connection for you.

If this post resolved your issue please click the 'This fixed my problem' button
 Harry Beesley
 Plusnet Help Team
Community Veteran
Posts: 4,979
Thanks: 376
Fixes: 16
Registered: 10-06-2010

Re: Interleaving request to be turned ON

I expect interleaving won't make any difference to the variability of the ping times. Interleaving will increase all the response times by a fixed amount, and the error correction might reduce the chance of packets being lost, but your DSL stats had hardly any errors anyway, and even packets being lost wouldn't explain the variable ping times.

I would suspect the problem is with the 2704N router, which apparently suffers particularly badly from bufferbloat.

markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Re: Interleaving request to be turned ON

Results with interleaving on.

modem.png

 

Idle pings are somewhat more stable although still jittery overall. I averaged at 35ms with frequent spikes up to 60-70ms so still around 20ms of jitter.

idle-qos-on.png

At roughly 20-40% bandwidth the ping are just out of control reaching as high as 1000ms. With this amount of jitter VOIP and other sensitive services are no fun at all.

traffic-qos-on.png

Graph to show my bandwidth utilisation.

traffic-ping-qos-on-with-bandwidth.png

And finally a ping command output as i know not everyone can read pingplotter. Note the varying latency time at idle. All thats running is the ping command.

Pinging bbc.co.uk [212.58.244.23] with 32 bytes of data:
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=45ms TTL=55
Reply from 212.58.244.23: bytes=32 time=37ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=37ms TTL=55
Reply from 212.58.244.23: bytes=32 time=40ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=39ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=37ms TTL=55
Reply from 212.58.244.23: bytes=32 time=41ms TTL=55
Reply from 212.58.244.23: bytes=32 time=34ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=34ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=40ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=39ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=37ms TTL=55
Reply from 212.58.244.23: bytes=32 time=36ms TTL=55
Reply from 212.58.244.23: bytes=32 time=35ms TTL=55
Reply from 212.58.244.23: bytes=32 time=39ms TTL=55
Reply from 212.58.244.23: bytes=32 time=42ms TTL=55
Reply from 212.58.244.23: bytes=32 time=38ms TTL=55
Reply from 212.58.244.23: bytes=32 time=39ms TTL=55

So it seems i have a line problem or something along the route although it would be nice if an expert could take a look over this before i open a line issue ticket.

@ejs - i'm running the 2704n in modem mode bridged to an Asus N66U. I also tried a HG612 and my latency exhibit the same issue so although the 2704n has its issues its not to blame here. This appears to be a line issue from what i can gather. If it was bufferbloat i would only experience the issue at around 90-100% bandwidth.

Plusnet Staff
Plusnet Staff
Posts: 17,641
Thanks: 535
Fixes: 159
Registered: 05-04-2007

Re: Interleaving request to be turned ON

Based on the speed of your connection, and the amount of upload going through it, it does seem to be causing the issue. The amount of data (230Mb per hour) is close to maxing out the upstream on an 832 upload. Can you try stopping anything uploading and doing the ping tests again?

If this post resolved your issue please click the 'This fixed my problem' button
 Chris Parr
 Plusnet Staff
markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Re: Interleaving request to be turned ON

@Chris I always disconnect any other devices and stop any network activity when running these tests. Please check your bandwidth graphs for today 28/07/2016 for the period 13:10-13:50 it should match up to my bandwidth graphs which reports a max of 525kbit/s (down) and 120kbit/s (up) for this period while i was running tests.

I'm sure you will agree this amount of latency at these loads (5-10%) is not acceptable. I am pinging what are supposedly local servers here (BBC, BT, Plusnet) yet somehow the latency is fluctuating by 20ms.

Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=46ms TTL=56
Reply from 212.159.8.2: bytes=32 time=55ms TTL=56
Reply from 212.159.8.2: bytes=32 time=49ms TTL=56
Reply from 212.159.8.2: bytes=32 time=49ms TTL=56
Reply from 212.159.8.2: bytes=32 time=55ms TTL=56
Reply from 212.159.8.2: bytes=32 time=62ms TTL=56
Reply from 212.159.8.2: bytes=32 time=46ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=49ms TTL=56
Reply from 212.159.8.2: bytes=32 time=48ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=44ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=47ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=46ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=47ms TTL=56
Reply from 212.159.8.2: bytes=32 time=57ms TTL=56
Reply from 212.159.8.2: bytes=32 time=44ms TTL=56
Reply from 212.159.8.2: bytes=32 time=44ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=53ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=49ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=49ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=47ms TTL=56
Reply from 212.159.8.2: bytes=32 time=47ms TTL=56
Reply from 212.159.8.2: bytes=32 time=52ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=46ms TTL=56
Reply from 212.159.8.2: bytes=32 time=49ms TTL=56
Reply from 212.159.8.2: bytes=32 time=46ms TTL=56
Reply from 212.159.8.2: bytes=32 time=49ms TTL=56
Reply from 212.159.8.2: bytes=32 time=48ms TTL=56
Reply from 212.159.8.2: bytes=32 time=50ms TTL=56
Reply from 212.159.8.2: bytes=32 time=55ms TTL=56
Reply from 212.159.8.2: bytes=32 time=46ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=47ms TTL=56
Reply from 212.159.8.2: bytes=32 time=51ms TTL=56
Reply from 212.159.8.2: bytes=32 time=45ms TTL=56
Reply from 212.159.8.2: bytes=32 time=44ms TTL=56
Reply from 212.159.8.2: bytes=32 time=48ms TTL=56
Reply from 212.159.8.2: bytes=32 time=44ms TTL=56
Reply from 212.159.8.2: bytes=32 time=44ms TTL=56
Reply from 212.159.8.2: bytes=32 time=47ms TTL=56
Reply from 212.159.8.2: bytes=32 time=48ms TTL=56

bbc.co.uk.pngbt.co.uk.pngplus.net.png

markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Re: Interleaving request to be turned ON

Its also worth mentioning when i perform a ping or traceroute to my IP using tools such as mxtools or thinkbroadband i'm also seeing the latency vary so this would also suggest there is a problem.

# Host Sent Recvd Best Avg Worst
1 thinkbroadband-gw2.core-rs2.thdo.ncuk.net 15 15 0ms 4ms 29ms
2 po4-31.bdr-rt3.thdo.ncuk.net 15 15 0ms 0ms 0ms
3 lonap-gw2.plus.net 15 15 0ms 0ms 0ms
4 ae2.ptw-cr01.plus.net 15 15 0ms 1ms 7ms
5 ae1.pcl-cr01.plus.net 15 15 0ms 2ms 29ms
6 te8-1.pcl-gw01.plus.net 15 15 1ms 1ms 7ms
7 link-a-central10.pcl-ag01.plus.net 15 15 1ms 5ms 42ms
8 myplusnetip.plus.com 15 15 33ms 35ms 47ms
markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Re: Interleaving request to be turned ON

I have gathered more results over the week, testing against various destinations i am getting pings of 20-120ms and varying every few seconds. Again all tests are done at idle to no load--only the pc running the tracert or pings commands are connected and using less than 300kbits and obviously i am wired directly to the router.

I have extensive pingplotter graphs at the ready if anyone needs to see them but i think the graphs and ping command output i have already posted shows the problem.

I would also like to point out that my TTBQM also shows the issue-- FYI this is with my router prioritising ICMP and the TBB IP address pool is also prioritised at my router so no this is not a result of pings being (de)prioritised. I have also purposely limited my connection to 200kbits(up) and 2000kbits(down) for the purpose of showing this live graph. I will be lifting this speed limit every evening at 10pm-3am after which it would go back to being limited so you can disregard any results from 10pm-3am.

My live TBBQM graph:

My Broadband Ping - My home broadband

This is how it should look at idle, notice how my average and max latency varies with each ping where this one does not.

Good BQM graph

And finally below is an example of a normal working 20CN connection (live graph) whilst under normal use e.g. web browsing. Mine is far from this..

With that said i would now like to raise this as a broadband fault. I see i can raise a fault but the troubleshooter doesnt list my problem. Could a moderator help me raise a ticket with the appropriate info please?

markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Re: Interleaving request to be turned ON

Well despite having no help i opened a ticket last weekend simply selecting the broadband was slow and i went on to mention in the notes that it wasnt a speed issue but latency related. I got an automatic response stating i would receive a status update in 24 hours, its now 120 hours (5 days) later and still no response?

Strangely though my pings have come down since opening the ticket and are more in line with what i would consider acceptable, not perfect as there is still around 10ms jitter at idle but its more acceptable to the 100+ms i was getting.

Is it normal for support tickets to remain unanswered but the issue gets resolved without notifying the customer? I was under the impression PN support was very good but i'm not sure what to think now since my 2 year long issue appears to have been fixed after opening a ticket but i never received any form of notification to say it was fixed let alone the line stats they are supposed to send.

Should i close the ticket or leave it open in hope they will eventually tell me what they fixed?

markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Re: Interleaving request to be turned ON

Not sure if anyone is reading this but as above my issue appears resolved after opening a ticket although i never received a reply from support my 2 year long issue is suddenly fixed. It would be nice to get some sort of answer from support about what changes they have made to resolve it?

For reference updated ping output shows average of 37-38ms with the occassional blip which is presumably just the server delaying pings but otherwise this is perfect and what i would expect.

Pinging bbc.co.uk [212.58.244.23] with 32 bytes of data:
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=38ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=47ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=36ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=54
Reply from 212.58.244.23: bytes=32 time=37ms TTL=5
Pinging thinkbroadband.co.uk [80.249.99.130] with 32 bytes of data:
Reply from 80.249.99.130: bytes=32 time=38ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=42ms TTL=56
Reply from 80.249.99.130: bytes=32 time=42ms TTL=56
Reply from 80.249.99.130: bytes=32 time=42ms TTL=56
Reply from 80.249.99.130: bytes=32 time=39ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=109ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=39ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56
Reply from 80.249.99.130: bytes=32 time=38ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56

As it appears fixed could i have interleaving turned off again please and i will see how my latency fairs now.

Thanks

markb5000
Grafter
Posts: 68
Thanks: 4
Registered: 13-10-2015

Re: Interleaving request to be turned ON

Update - Finally received a response to my ticket showing my line stats and a second response saying they have cleared a fault on my line. No reason given or any indication as to what they have cleared though but hey atleast they responded (eventually).

Now that my issue is confirmed fixed if a mod could please turn interleaving off again that would be greatly appreciated.

Thanks

Moderator
Moderator
Posts: 17,085
Thanks: 2,063
Fixes: 142
Registered: 06-04-2007

Re: Interleaving request to be turned ON

Mods are customers just like yourself and have no access to your accounts.

 

I am sure a member of staff will pick this up on Monday.

Forum Moderator and Customer
Courage is resistance to fear, mastery of fear, not absence of fear - Mark Twain
He who feared he would not succeed sat still