Really poor latency all of a sudden

[#1]

Hi, not had any problems before, been on for over a year.
But tonight, it's nearly unusable. Here are my router stats:

Quote

Downstream  Upstream Data Rate(Kbps)         18272                444 Noise margin (dB)         5.5                29.3 Output power (dBm)         0.0                12.2 Attenuation (dB)         16.0                6.1

A route trace to www.plus.net shows up very high latency:
C:\Users\Charlie>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:

Quote

1    2 ms    2 ms    2 ms  192.168.2.1   2  246 ms  231 ms  376 ms  lo0-central1.pcl-ag01.plus.net [195.166.128.232]   3  317 ms  411 ms  554 ms  gi1-8-112.pcl-gw02.plus.net [84.92.6.2]   4  230 ms    47 ms    49 ms  po4.pcl-gw01.plus.net [212.159.1.128]   5  456 ms  365 ms  238 ms  ae3.pcl-cr01.plus.net [195.166.129.40]   6  304 ms  476 ms  540 ms  ae1.ptw-cr01.plus.net [195.166.129.0]   7  574 ms  417 ms  479 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]   8  619 ms  765 ms  706 ms  gi3-0.pih-cr1.plus.net [212.159.1.177]   9  472 ms  497 ms  597 ms  if25.pih-lb04.plus.net [212.159.0.18] 10  572 ms  555 ms  411 ms  portal.plus.net [212.159.8.2]

And lastly, the security log from the router has gone nuts!... (this is just a snippet from the last minute!)

Quote

Feb 9 21:48:49 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 67.190.158.238 117 Feb 9 21:48:49 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 90.148.218.3 115 Feb 9 21:48:50 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 50.15.50.214 115 Feb 9 21:48:51 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 88.255.100.254 117 Feb 9 21:48:51 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 2.5.78.121 113 Feb 9 21:48:51 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 46.120.95.111 116 Feb 9 21:48:51 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 71.23.235.23 115 Feb 9 21:48:51 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 79.107.192.37 116 Feb 9 21:48:51 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 79.131.10.13 115 Feb 9 21:48:52 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 180.216.33.58 116 Feb 9 21:48:52 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 87.194.207.241 117 Feb 9 21:48:52 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 75.118.230.128 117 Feb 9 21:48:52 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 85.192.222.236 117 Feb 9 21:48:52 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 24.246.159.70 116 Feb 9 21:48:52 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 175.142.222.243 118 Feb 9 21:48:53 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 46.120.95.111 116 Feb 9 21:48:53 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 67.166.100.42 116 Feb 9 21:48:53 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 108.67.149.207 117 Feb 9 21:48:53 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 14.200.214.67 116

Any help would be greatly appreciated!
Charlie

[#2]

I suggest you try a disconnect/reconnect via the router interface.
Are you on a fixed or dynamic IP? If it's dynamic the reconnect should stop the attack.

[#3]

Excellent! Worked a charm, any idea how I can stop it happening again? Or is it just one of them things?

[#4]

Unfortunately it's just one of those things - some people will always be scanning large blocks of IP addresses looking for any kind of vulnerability, which is one of the things routers protect against. It's nothing to worry about and as Jelv says if you notice it happening again rebooting the router to get a different IP address will stop things.
Hope that reassures you.

[#5]

Thank you, glad to say, back to normal today