on 08-06-2012 15:55
I've been with 02 (the works) only a couple of months. It was rock solid, but has degenerated to this.The above is a 24hr graph, red lines are 100% packet loss which typically last for a few minutes then revert to normal service.
Absolutely nothing has changed here, the O2 Box 4 was dropped into an existing wired LAN. I monitored it for a week initially and there were no drop-outs at all. I am not sure when this began, perhaps 1-2 weeks ago is when I first noticed on streaming Radio4. Intermittent connections to websites are now such a problem that I've been running Pingplotter continuously on a number of sites.
It appears to me, from watching how routing fails, to be an O2/Be network problem, with a remote router getting its knickers round its neck. As routing changes the problem tends to get better or worse. However a conversation with O2 support yesterday was unresponsive to this suspicion. All he wanted me to do was reboot the box - which does nothing useful. He did tweak something (gain, perhaps - he didn't say) which has made a marginal difference - the outage periods are now less regular and more chaotic, but not any better.
I asked for a diagnostic trace to be recorded, but was told that because the box is not on a master socket this isn't possible. Nor was it worth sending an engineer if the box was on a secondary.
Well, that's because the master socket is in a cupboard under the stairs with no mains and no CAT5. The secondary has worked absolutely fine for weeks. And I'll bet my 10 years experience of DSL that this is a network problem so sending an engineer would be pointless anyway.
So right now I have a degraded DSL connection and O2 only appear interested in fixing a problem I don't have, which will take me a fair bit of rewiring to prove I don't have so an engineer can come and find that there isn't a problem. Is this pattern of periodic packet loss familiar to anyone?
on 10-06-2012 21:57
Pingplotter could be showing a problem at the remote IP ( ie the remote end set to a low priority for ping replies) or a problem with wireless at your end ( if using wireless).
To give more confidence the issue is with the O2 network I would test using the TBB Quality Monitor.
To use this you'll need to set the O2 box to "enable reply to pings from WAN".
Instructions here: http://npr.me.uk/telnet.html
on 19-06-2012 02:14
Thanks, but no - I was running Pingplotter against several IP's that I've used for monitoring for many years, and results were consistent.
However the problem vanished completely, whilst I was composing the OP, and has not returned. Best guess:a network problem that got fixed.