In reply to a post by WWWombat:

That's a good point... Most MSANs are (or should be) dual-parented, so there are 2 different routes back to the core network. And for some the difference is significant.

Would this also apply to FTTC though?

Here are a couple of examples from tonight, done approx 3 mins apart:
My ping has now increased to 34-35ms, since this morning, the village rush for fibre must still be on.
Sky called back tonight and said that my profile was fine, there were no errors on my line and interleaving was off.

Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 34 ms 32 ms 31 ms ip-84-38-37-16.easynet.co.uk [84.38.37.16]
4 41 ms 39 ms 38 ms 89.200.131.185
5 29 ms 29 ms 29 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.

6 * * * Request timed out.
7 * * * Request timed out.
8 30 ms 29 ms 29 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
9 31 ms 29 ms 29 ms 132.185.255.148
10 29 ms 29 ms 30 ms bbc-vip115.telhc.bbc.co.uk [212.58.244.70]



Tracing route to www.bbc.net.uk [212.58.246.92]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 35 ms 32 ms 31 ms ip-84-38-37-14.easynet.co.uk [84.38.37.14]
4 36 ms 31 ms 32 ms 89.200.131.187
5 29 ms 29 ms 29 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.

6 * * * Request timed out.
7 31 ms 30 ms 30 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
8 33 ms 31 ms 30 ms 132.185.255.165
9 29 ms 30 ms 29 ms bbc-vip013.cwwtf.bbc.co.uk [212.58.246.92]


Tracing route to www.bbc.net.uk [212.58.246.92]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 34 ms 30 ms 31 ms ip-84-38-37-14.easynet.co.uk [84.38.37.14]
4 30 ms 31 ms 30 ms 89.200.131.187
5 31 ms 37 ms 29 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.

6 * * * Request timed out.
7 31 ms 29 ms 29 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
8 34 ms 33 ms 33 ms 132.185.255.165
9 33 ms 31 ms 33 ms bbc-vip013.cwwtf.bbc.co.uk [212.58.246.92]

Edited by HiPing (Tue 18-Dec-12 20:15:27)

In reply to a post by Ignitionnet:

In reply to a post by WWWombat:

That's a good point... Most MSANs are (or should be) dual-parented, so there are 2 different routes back to the core network. And for some the difference is significant.

Would this also apply to FTTC though?

If the 21CN core has been built anything like it was originally planned to be, then yes - that part certainly is. That means the ISP's using WBC and WBMC should automatically get this.

Whether the FTTC cabinet is dual-parented (eg 2 different exchanges), or the head-end OLT is duplicated, or is dual-parented (multiple cable-links?), I don't know.

In reply to a post by HiPing:

My ping has now increased to 34-35ms, since this morning, the village rush for fibre must still be on.
Sky called back tonight and said that my profile was fine, there were no errors on my line and interleaving was off.

No interleaving means that either (a) Sky support don't know what they're saying about FTTC, or (b) the change in delay is purely down to delays within Sky's network.

How does your ping alter over the course of a day (or night)?

Ordinarily I'd mention a BQM here (see http://www.thinkbroadband.com/ping) but I don't think Sky has static IP, does it?

Just done a quick ping, and tracert to the Beeb from my BT connection, overall 18ms, tracert showing quite a few more hops than the OP's, one even shows 50+ ms.

I don't get the 'missing' 2nd hop he does, anyone else ?

To the OP, my cab has been live for over two years, and there is around 120 connections running from it, so maybe the issue isn't your nieghbours rush for speed ?

Whoops, you mean like these ones ahem!
The last one shows a disconnection, my son being over zealous with pulling plugs out after turning off his xbox.

My Broadband Ping 23 Nov 12

My Broadband Ping 29 Nov12

My Broadband Ping 30 Nov 12

My Broadband Ping 05 Dec 12

My Broadband Ping 18 Dec 12

What I find interesting is that it seems to have increased from just less than 20ms to about 25 (hard to tell exactly from a graph) in the early hours of 30/11, then from there back to 20ms, then jumped to about 30ms.
Assuming you didn't go an unplug/reboot the modem at midnight, 2am and 5am, that looks like something has been changing a few times in about 5 hours.
Where geographically are you? You are now getting higher pings than I get from Scotland on ADSL...

I'm an exiled Scotsman , living in the village of Barlby in North Yorkshire, connected to the Selby exchange. Maybe I reboot routers when I sleep walk, does seem weird though.

Edited by HiPing (Tue 18-Dec-12 21:55:34)

Interesting discussion generally. I've had FTTC through one of the small ISPs - who prides themselves on not "overselling" their network - for well over 12m at a consistent 16ms minimum latency (and average only just minimally higher except during my own heavy downloading) according to TBBQM monitoring. Average results in the same ball park from Trace Route to Google and JDast auto tester's daily tests at various times which uses BBC for ping testing by default. The only noticeable change was a doubling in the latency (to 16ms) after the first month when interleaving was turned on my connection, which was not unexpected. I use a Fritz!Box modem (which shows the latency as 8ms just to the Cab DSLAM) not the OR varieties though, but in fairness it looked stable on my connection anyway.

Interesting though that other FTTC users on the same ISP have recently (over the last month) started to report the same sort of variances as reported here but not to anything like the same extent. Just wondering though as I'm still on 40/10 (as due to distance from the cab as my attainable rate would struggle to get much higher) do these problems particularly afflict those pushing their connections up to 80/20, or whatever? EDIT: just out of interest looked up the JDast monitoring of pings on my fixed wireless connection - which takes the local loop out of the equation but uses Sky's backhaul network via Easynet - and is in the 12-20ms range consistently to bbc.co.uk.

Edited by deleted (Tue 18-Dec-12 22:33:42)

Actually, if you want to see a high ping try 202.80.32.65 - you are unlikely to get less than 800ms to that