TBB Latency Graph People

[#1]

Hi all,
We've just brought a new broadband network gateway online (PTW-BNG01). We've made some changes on the titanium queue on this gateway which we think might remove or reduce a bit of the peak time latency some people see on Thinkbroadband graphs. If anyone wants try and hop on to it (it may still show pte-ag01 in a traceroute as DNS changes are still being done) and show us your graphs over the weekend that would be appreciated.

[#2]

Will try and get on to it when I get home!

[#3]

Hi Dave
I have hopped across to the new gateway @ approx 16:40 on Friday.
richard@~ $ traceroute --resolve-hostnames www.plus.net
traceroute to portal.plus.net (212.159.9.2), 64 hops max
1  192.168.0.1 (192.168.0.1) 2.186ms 2.082ms 1.733ms
2  195.166.128.170 (lo0.10.central10.ptw-bng01.plus.net) 22.252ms 22.694ms 21.663ms
3  84.93.249.1 (irb.10.ptw-cr01.plus.net) 22.978ms 22.678ms 22.927ms
4  195.166.129.1 (ae1.pcl-cr01.plus.net) 22.317ms 22.477ms 36.802ms
5  195.166.129.41 (po2.pcl-gw01.plus.net) 22.265ms 24.349ms 22.635ms
6  84.93.224.48 (gi5-8.ptp-cr01.plus.net) 30.487ms 30.190ms 32.031ms
7  84.93.224.45 (vlan2658.ptp-elb02.plus.net) 31.991ms 31.645ms 31.008ms
8  212.159.9.2 (portal.plus.net) 30.338ms 30.488ms 31.730ms
TTB graph @ http://www.thinkbroadband.com/ping/share/bd5369f77cfa3aec137e749767fc2833.html
Richard

[#4]

Connected to it now.
"Which gateway" tool needs updating as well. It currently shows "Sorry, the tool currently could not identify your gateway; this does not mean that anything is wrong with your connection."

[#5]

Connected Now!
Live Monitor

Here's daily monitor snapshots:
28/03 (Changed to new gateway from the big packet drop spike)

[#6]

Managed to land on it after lots of attempts - graph here:

Traceroute to www.google.co.uk:
traceroute  www.google.co.uk
traceroute to www.google.co.uk (173.194.34.120), 30 hops max, 60 byte packets
1  lo0.10.central10.ptw-bng01.plus.net (195.166.128.170)  13.325 ms  13.389 ms  13.367 ms
2  irb.10.ptw-cr01.plus.net (84.93.249.1)  13.399 ms  13.317 ms  13.699 ms
3  72.14.222.97 (72.14.222.97)  13.441 ms 72.14.223.32 (72.14.223.32)  13.677 ms  13.667 ms
4  209.85.252.188 (209.85.252.188)  13.671 ms 209.85.246.242 (209.85.246.242)  13.839 ms  13.764 ms
5  209.85.253.47 (209.85.253.47)  13.858 ms  14.516 ms  13.978 ms
6  lhr14s20-in-f24.1e100.net (173.194.34.120)  13.559 ms  13.784 ms  13.710 ms
Will see how it goes over the weekend.

[#7]

A one hop less but a tad higher latency

Quote

Tracing route to bbc.co.uk [212.58.244.18] over a maximum of 30 hops:  1    23 ms    87 ms    97 ms  dsldevice.lan [192.168.1.254]  2   128 ms    25 ms    25 ms  lo0-central10.ptw-ag02.plus.net [195.166.128.196]  3   174 ms    26 ms    26 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.148]  4   252 ms    25 ms    25 ms  xe-0-2-0.ptw-cr01.plus.net [212.159.0.248]  5    25 ms    25 ms    26 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]  6     *        *        *     Request timed out.  7     *        *        *     Request timed out.  8    28 ms    26 ms    26 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]  9    26 ms    25 ms    26 ms  132.185.255.149 10    32 ms    24 ms    25 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18] Trace complete. Tracing route to bbc.co.uk [212.58.244.18] over a maximum of 30 hops:  1    87 ms    95 ms    97 ms  dsldevice.lan [192.168.1.254]  2    28 ms    27 ms    27 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128.170]  3    27 ms    29 ms    27 ms  irb.10.ptw-cr01.plus.net [84.93.249.1]  4    29 ms    29 ms    28 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]  5     *        *        *     Request timed out.  6     *        *        *     Request timed out.  7    31 ms    28 ms    28 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]  8    29 ms    29 ms    29 ms  132.185.255.149  9    28 ms    28 ms    28 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Update:
Got kicked off around 2:30pm Saturday. 

[#8]

I am on it now.
Initial performance seems very good - I can ping the pingbox1.thinkbroadband.com and get sub-8second pings, which is unheard of (especially this time of night). 

[#9]

So far so bad, hopped to it at 9.03pm and just had a lost PPP session at 9.45pm
edit: tried to get back on it and can't, will try again tomorrow as I need my connection stable for next few hours

[#10]

I've just reconnected on it, so will see how it goes. I was on ptw-ag02 before and the graph shows a drop in the minimum latency on the new one straight away.

[#11]

This graph was connected to the new gateway ptw-bng01 from midnight until 8.20am, then I disconnected and connected back to ptn-ag03, and then at around 12.45pm I reconnected to ptw-bng01. 
My observations would be:
Better:
Background latency jitter seems reduced - the blue and yellow lines are pretty much invisible unless there is some activity from my end on the line.
My best-case ping outs from my router to pingbox1.thinkbroadband.com have dropped down to just under 8ms.
Maximum throughput on speedtest.net marginally increased for downstream.
Worse:
Local activity seems to have a more detrimental effect on ping traffic.  At 8am on the ptw-bng01 I did a large couple of HTTP downloads - the effect of which can be seen.  That is why I reconnected to the older gateway ptn-ag03 and did another test (this time a debian CD image torrent - around 12.30pm).  Then at 12:45 downloaded some more debian torrent on the ptw-bng01 - you can see much taller spikes than with the old gateway.
Clearly different - don't know if it is better or not!

[#12]

Been trying for last 30mins and can't get this gateway again, any way to force the TG582n to a specific gateway?

[#13]

I got chucked off that gateway and on to pcl-ag04 around 3pm, can't get back on it.

[#14]

Also thrown off at just after 3pm and still have not managed to land on it after a bunch of attempts so will give it a rest for now - if others are hitting the same thing perhaps it has gone offline for some reason?
For the time I was connected didn't notice any issues.

[#15]

I also lost connectivity at the same time as andy265 & clearx.
Now on a pcl-ago3.