Well the spike has been and gone.

All pings to my server was 17ms at all times which is normal.

However I trace routed to here, hope you didn't mind and I have some of the results below:

tracert -4 thinkbroadband.com

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  YAZOOROUTER [192.168.2.253]
  2     3 ms     2 ms     2 ms  217.32.146.68
  3     5 ms     3 ms     3 ms  217.32.146.94
  4     3 ms     3 ms     3 ms  213.120.156.210
  5     3 ms     3 ms     3 ms  217.41.168.49
  6     4 ms     3 ms     3 ms  217.41.168.107
  7     4 ms     3 ms     3 ms  109.159.249.104
  8     3 ms     3 ms     3 ms  core3-te0-10-0-19.faraday.ukcore.bt.net [109.159.249.23]
  9     4 ms     4 ms     4 ms  213.121.193.191
 10     4 ms     3 ms     3 ms  linx-gw1.thn.ncuk.net [195.66.224.240]
 11     3 ms     4 ms     3 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
 12     *        *        *     Request timed out.
 13     4 ms     3 ms     4 ms  www.thinkbroadband.com [80.249.99.130]

Trace complete.

tracert -4 thinkbroadband.com

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  YAZOOROUTER [192.168.2.253]
  2     3 ms     2 ms     2 ms  217.32.146.68
  3    22 ms     5 ms     8 ms  217.32.146.94
  4     3 ms     3 ms     3 ms  213.120.156.210
  5     3 ms     3 ms     3 ms  217.41.168.49
  6     4 ms     3 ms     3 ms  217.41.168.107
  7     3 ms     3 ms     3 ms  109.159.249.104
  8     4 ms     3 ms     3 ms  core3-te0-10-0-19.faraday.ukcore.bt.net [109.159.249.23]
  9     4 ms     4 ms     4 ms  213.121.193.191
 10   166 ms   213 ms     *     linx-gw1.thn.ncuk.net [195.66.224.240]
 11     *        *        *     Request timed out.
 12     4 ms     3 ms     4 ms  www.thinkbroadband.com [80.249.99.130]

Trace complete.

tracert -4 thinkbroadband.com

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  YAZOOROUTER [192.168.2.253]
  2     3 ms     2 ms     2 ms  217.32.146.68
  3     3 ms     3 ms     2 ms  217.32.146.94
  4     4 ms     3 ms     3 ms  213.120.156.210
  5     3 ms     3 ms     3 ms  217.41.168.49
  6     3 ms     3 ms     3 ms  217.41.168.107
  7     4 ms     3 ms     3 ms  109.159.249.104
  8     4 ms     3 ms     3 ms  core3-te0-10-0-19.faraday.ukcore.bt.net [109.159.249.23]
  9     4 ms     4 ms     4 ms  213.121.193.191
 10     4 ms     4 ms     4 ms  linx-gw1.thn.ncuk.net [195.66.224.240]
 11     4 ms     4 ms     4 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
 12     *        *        4 ms  www.thinkbroadband.com [80.249.99.130]

Trace complete.

tracert -4 thinkbroadband.com

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  YAZOOROUTER [192.168.2.253]
  2     3 ms     2 ms     2 ms  217.32.146.68
  3     3 ms     2 ms     2 ms  217.32.146.94
  4     4 ms     3 ms     3 ms  213.120.156.210
  5     3 ms     3 ms     3 ms  217.41.168.49
  6     3 ms     3 ms     3 ms  217.41.168.107
  7     3 ms     3 ms     3 ms  109.159.249.104
  8     3 ms     3 ms     3 ms  core3-te0-10-0-19.faraday.ukcore.bt.net [109.159.249.23]
  9     4 ms     4 ms     3 ms  213.121.193.191
 10   124 ms   216 ms     4 ms  linx-gw1.thn.ncuk.net [195.66.224.240]
 11     *        *        4 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
 12     4 ms     3 ms     4 ms  www.thinkbroadband.com [80.249.99.130]

Trace complete.

I am not really a network routing guy, so the above odd * is fine but the "Request timed out" isn't.

I am still no closer to knowing if its a router issue or connection.

I just re did some trace routing to here where there is no spikes and its all fine again:

tracert -4 thinkbroadband.com

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  YAZOOROUTER [192.168.2.253]
  2     3 ms     2 ms     2 ms  217.32.146.68
  3     3 ms     2 ms     2 ms  217.32.146.94
  4     4 ms     3 ms     3 ms  213.120.156.210
  5     3 ms     3 ms     3 ms  217.41.168.49
  6     3 ms     3 ms     3 ms  217.41.168.107
  7     3 ms     3 ms     3 ms  109.159.249.104
  8     3 ms     3 ms     3 ms  core3-te0-10-0-19.faraday.ukcore.bt.net [109.159.249.23]
  9     3 ms     4 ms     4 ms  213.121.193.191
 10     4 ms     4 ms     4 ms  linx-gw1.thn.ncuk.net [195.66.224.240]
 11     4 ms     4 ms     4 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
 12     4 ms     3 ms     3 ms  www.thinkbroadband.com [80.249.99.130]

Trace complete.

tracert -4 thinkbroadband.com

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  YAZOOROUTER [192.168.2.253]
  2     3 ms     2 ms     2 ms  217.32.146.68
  3     3 ms     2 ms     2 ms  217.32.146.94
  4     4 ms     3 ms     3 ms  213.120.156.210
  5     3 ms     3 ms     3 ms  217.41.168.49
  6     3 ms     4 ms     3 ms  217.41.168.107
  7     3 ms     3 ms     3 ms  109.159.249.104
  8     4 ms     3 ms     3 ms  core3-te0-10-0-19.faraday.ukcore.bt.net [109.159.249.23]
  9     4 ms     4 ms     4 ms  213.121.193.191
 10     4 ms     4 ms     4 ms  linx-gw1.thn.ncuk.net [195.66.224.240]
 11     4 ms     3 ms     4 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
 12     3 ms     4 ms     4 ms  www.thinkbroadband.com [80.249.99.130]

Trace complete.

Very strange.

Paul

Not strange at all, devices prioritise processing through traffic rather than processing ping/icmp requests, only if subsequent hops are higher would you need to worry.

We also monitor interfaces and if latency exceeds normal limits for a period of time will get alarms notifying us and there was none, and if it was those nodes everyone coming across that link would also be affected.

Ah, ok, so any clue what could be causing those spikes ?

I am hoping its the router due to its easily replaceable, getting BT to do something is harder to do LOL.

Paul

I wonder if it is calling home and waiting for a response with a CPU loop running? (Serious, not a joke this time). Don't forget, the dropped packets are not a measurement by your router, they are BQM not getting replies from it.

The router busy doing something else is a possibility, in software terms garbage collection i.e. recycling memory is a possible reason for the delays.

The traceroutes seem to show outbound packets and responses are not affected, supporting hypothesis that this may be a firmware issue in the broadband router

Ok, well the new Linksys WRT3200ACM-UK is down to arrive sometime tomorrow.

Then it will be a waiting game for another several days to see if it happens on this one, which I am hoping it doesn't.

Paul

Well the Linksys WRT3200ACM arrived, all set up.

Wi-Fi is great.

Sadly my 300Mbit connection is now a 4Mbit connection if I am lucky

Linksys Speed Test

Its setup as PPPoE, also set the usernsame to [email protected] same as what it was on my Fritz!Box 4040

Oh and IPv6 isn't working.

Right I am swapping back to the Fritzbox to see if that connection is better.

Paul

http://community.linksys.com/t5/Wireless-Routers/WRT...

Suggests may not have been just you, routers unfortunately don't always ship with the latest firmware, so its worth trawling Linksys site to see what updates and fixes are resolved

In reply to a post by MrSaffron:

http://community.linksys.com/t5/Wireless-Routers/WRT...

Suggests may not have been just you, routers unfortunately don't always ship with the latest firmware, so its worth trawling Linksys site to see what updates and fixes are resolved

Well that's a different model number, but reading the page

As for the speed, it was Windows 10 at fault once again.
It seems that Windows 10 seems to have issues when IP's change on the router, even after I release and renew everything.

A full reboot of my PC resolved the speed issue shown here (Flash Version) and here (HTML5) taking into account its the weekend when everyone is using the internet.

Sadly still no IPv6 which really was a must for me for the software I am writing.

And the latency has doubled compared to when it was on the Fritz, but I will leave it for a few days to see how it goes.

As for the BQM, there is no point setting that up yet due to I am still changing stuff on the new router and most stuff requires a reboot of it.

Paul

Ok I am done with fiddling with this router, so I have now just added the BQM to it, so it will need at least 24 hours before we see how clean it is and then another several days to see if those spikes appear.

Hopefully it will be fine.

Paul