IDNetters Forums

Technical News & Discussion => IDNet Help => Topic started by: Bill on Oct 17, 2023, 13:41:33

Title: Noisy BQM
Post by: Bill on Oct 17, 2023, 13:41:33
Somewhere around 4:30 this morning my BQM went mildly horrible, spikes of high latency at about half-hour intervals:

(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/a494a4cfa284ed2cb2a2a9b9416bc3a774cb1200-17-10-2023.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/a494a4cfa284ed2cb2a2a9b9416bc3a774cb1200-17-10-2023)

Ignore the red spike, that was me rebooting the router. I've tried everything I can think of, but can't get rid of it... but I'm still not entirely convinced it isn't something on my LAN, so I thought I'd check here before getting on to support.

Is anyone else seeing anything like it?


eta- 80/20 FTTC by the way.
Title: Re: Noisy BQM
Post by: zappaDPJ on Oct 17, 2023, 16:17:53
Unfortunately since I moved house I've failed miserably to get a new BMQ working but others I can see look normal.
Title: Re: Noisy BQM
Post by: Bill on Oct 17, 2023, 16:38:45
OK, thanks... I shall have to do some deep thinking (and hope it goes away on its own ;) )

Fortunately it doesn't seem to be actually affecting anything so, whatever it is, it's not really a problem (yet  :fingers: ), it just looks horrible compared to usual.
Title: Re: Noisy BQM
Post by: Bill on Oct 21, 2023, 10:15:07
Sorted it, after about 2 days of hair-tearing...

Going through all the details would be tl;dr, but Support couldn't see anything amiss, and whenever I changed something (and there were quite a few possible suspects) I had to wait for anything up to an hour to see if had worked. Then think of something else to try  :dunno:

Eventually I was led to resetting the router to factory defaults and reconfiguring it... a pita and I didn't expect it to work because I hadn't changed any settings for at least 6 months and I'd rebooted and power cycled it several times during testing, but bingo!

So I still don't really know exactly what the problem was, but I know what fixed it!