A while ago when I was still connected to WBC I had a ridiculously low ping. Sometime after I was connected to FTTC (I think) my ping more than doubled from 7ms to 17ms. This morning it dropped back down to 7ms.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>ping idnet.net
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=7ms TTL=59
Reply from 212.69.36.10: bytes=32 time=7ms TTL=59
Reply from 212.69.36.10: bytes=32 time=7ms TTL=59
Reply from 212.69.36.10: bytes=32 time=7ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 7ms, Average = 7ms
C:\Users\zappaDPJ>
(http://www.thinkbroadband.com/ping/share-thumb/bfd670313b30e389505e30e3b8e83025-12-06-2011.png) (http://www.thinkbroadband.com/ping/share/bfd670313b30e389505e30e3b8e83025-12-06-2011.html)
The question uppermost on my mind is why? What would cause this. At the time my latency dropped there was nobody using the net and there's nothing of any note in the router log.
I'm tempted to say don't worry, just enjoy!
I would imagine it's either a routing change beyond the exchange or maybe a piece of kit was replaced somewhere along the line.
Looks like interleaving coming off?
Quote from: Bill on Jun 12, 2011, 22:50:45
Looks like interleaving coming off?
Yup. You can see from the TBB QM that the connection definitely went down while DLM applied the change and resynced.
I didn't realise it was possible for Interleaving to be switch off without intervention from support. But then again I hadn't really considered it to be a factor. I guess that might be the answer though.
Quote from: Lance on Jun 12, 2011, 22:49:21
I'm tempted to say don't worry, just enjoy!
My thoughts entirely. A lot of what I do on the net is quite sensitive to latency so I'll be enjoying it to the full. To be honest 17ms is pretty low but 7ms is outstanding, I hope it lasts :)
Quote from: zappaDPJ on Jun 12, 2011, 22:58:55
I didn't realise it was possible for Interleaving to be switch off without intervention from support
The FTTC DLM is pretty much auatomaic afaik, I'm not even sure if CS
can do very much these days >:(
My interleave goes on and off like a stripper's bra.
Probably more off than on then. ;)
Regrettably not :bawl:
Quote from: Bill on Jun 12, 2011, 23:01:46
The FTTC DLM is pretty much auatomaic afaik, I'm not even sure if CS can do very much these days >:(
My interleave goes on and off like a stripper's bra.
Interesting, I didn't know that.
The info on interleaving was interesting as well :laugh:
Idnet CS have no control over FTTC DLM at all.
AFAIK they can put in a request to BTW but it's extremly rare they'll manually alter the DLM.
Quote from: .Griff. on Jun 12, 2011, 23:41:17
Idnet CS have no control over FTTC DLM at all.
AFAIK they can put in a request to BTW but it's extremly rare they'll manually alter the DLM.
Over on tbb someone (I think it was RobertoS but cba'd to find it) said that with FTTC, because the DLM is in the cabinet DSLAM it belongs to BT OpenReach and is different from the "usual" DLM which lives in the exchange MSANs and belongs to BT Wholesale...
Sounds highly plausible (and typical of BT), but I've got no other evidence for it.
Quote from: Bill on Jun 12, 2011, 23:01:46
My interleave goes on and off like a stripper's bra.
Does that include a shimmy, Bill? ;D