1.4k speed on plusnet extra for over 2 days straight now....

[#1]

Hi All
Been getting les than 56k speeds for 2 days now. Nothing has changed at my house nor with my setup. Last thing I was doing with speed was watching some streaming football on bet365 on tuesday night.
Wednesday afternoon my girlfriend at home tells me the internets unusable..... and were still here tonight.

Download speed achieved during the test was - 180 Kbps
For your connection, the acceptable range of speeds is 2000-7150 Kbps.

Additional Information:
Your DSL Connection Rate :9607 Kbps(DOWN-STREAM), 443 Kbps(UP-STREAM)
IP Profile for your line is - 7000 Kbps
The throughput of Best Efforts (BE) classes achieved during the test is - 33.56:21.73:45.03 (SBE:NBE:PBE)
These figures represent the ratio while sententiously passing Sub BE, Normal BE and Priority BE marked traffic.
The results of this test will vary depending on the way your ISP has decided to use these traffic classes.
Upload speed achieved during the test was - 0 Kbps
Additional Information:
Upstream Rate IP profile on your line is - 443 Kbps

[#2]

Just noticed this on my logs
Thu, 2011-04-07 10:38:43 - Router start up
Thu, 2011-04-07 11:36:44 - <NTP> Receive NTP Reply from 64.94.70.147
Thu, 2011-04-07 12:26:35 - <NTP> Local NTP clock is now synced
Thu, 2011-04-07 15:00:47 - <NTP> Receive NTP Reply from 64.94.70.147
Thu, 2011-04-07 16:59:02 - <NTP> Receive NTP Reply from 64.94.70.147
Thu, 2011-04-07 18:40:09 - <NTP> Receive NTP Reply from 64.94.70.147
Thu, 2011-04-07 19:02:36 - <HTTP> Administrator login successful - IP:192.168.0.4
Thu, 2011-04-07 19:44:08 - LCP down.
Thu, 2011-04-07 19:44:21 - Initialize LCP.
Thu, 2011-04-07 19:44:21 - LCP is allowed to come up.
Thu, 2011-04-07 19:44:22 - CHAP authentication success
Thu, 2011-04-07 19:52:16 - <HTTP> Administrator login successful

Thing was slow as a dog when that NTP entry was there. LCP went down and back up again minus any NTP and its fast again.
Guess the question is what is that NTP entry about?  Lease?

[#3]

Thu, 2011-04-07 19:55:39 - Receive NTP Reply from 64.94.70.147
Disconnect from internet & when it came back up it was Painfully Slow Again

So it is clear it is this NTP thing (whatever it is) which is causing this problem.

[#4]

C:\Users\Meh>tracert 69.94.70.147
Tracing route to wealthwithbenefits.net [69.94.70.147]
over a maximum of 30 hops:
  1  121 ms    92 ms  179 ms  ***EDITED***
  2    *      123 ms    85 ms  lo0-central2.ptn-ag01.plus.net [195.166.128.203]
  3  316 ms  111 ms    *    gi2-11-121.ptn-gw01.plus.net [84.92.3.145]
  4    *      461 ms  347 ms  po6.thn-gw1.plus.net [212.159.1.136]
  5  184 ms    *      63 ms  po4.thn-gw2.plus.net [212.159.1.135]
  6    91 ms  809 ms  407 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  7    19 ms  313 ms    65 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
  8  461 ms  302 ms  111 ms  ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]
  9  191 ms  874 ms  300 ms  ae-5-5.car1.Stamford1.Level3.net [4.69.142.85]
10  161 ms  272 ms    *    OLM-LLC.car1.Stamford1.Level3.net [63.208.150.6]
11  715 ms    *      148 ms  vl551.corea.trum.fastdns.net [69.94.3.37]
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.

[#5]

Full Log so far....... this is really annoying me now, Starting to wonder if i have some sort of virus here
Switched over my DNS to googles (8.8.8.8)
Thu, 2011-04-07 19:44:08 - LCP down.
Thu, 2011-04-07 19:44:21 - Initialize LCP.
Thu, 2011-04-07 19:44:21 - LCP is allowed to come up.
Thu, 2011-04-07 19:44:22 - CHAP authentication success
Thu, 2011-04-07 19:55:39 - <NTP> Receive NTP Reply from 64.94.70.147
Thu, 2011-04-07 19:57:42 - LCP down.
Thu, 2011-04-07 19:57:58 - Initialize LCP.
Thu, 2011-04-07 19:57:58 - LCP is allowed to come up.
Thu, 2011-04-07 19:57:59 - CHAP authentication success
Thu, 2011-04-07 19:58:24 - <NTP> Receive NTP Reply from 12.7.210.177
Thu, 2011-04-07 20:36:01 - <NTP> Local NTP clock is now synced


Tracing route to 12.7.210.177 over a maximum of 30 hops
  1    1 ms    1 ms    3 ms  192.168.0.1
  2    17 ms    19 ms    20 ms  lo0-central2.ptn-ag01.plus.net [195.166.128.203]
  3  106 ms    92 ms  110 ms  gi2-11-121.ptn-gw01.plus.net [84.92.3.145]
  4    *      205 ms    53 ms  po6.thn-gw1.plus.net [212.159.1.136]
  5  116 ms  314 ms  117 ms  po4.thn-gw2.plus.net [212.159.1.135]
  6  217 ms  537 ms    60 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  7  219 ms    82 ms  549 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
  8  131 ms  145 ms  381 ms  ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
  9  544 ms  197 ms  409 ms  ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
10  203 ms    *      98 ms  ae-3-89.edge3.NewYork1.Level3.net [4.68.16.145]
11  813 ms  279 ms  989 ms  mci-level3-xe.Washington4.Level3.net [4.68.63.14
2]
12  378 ms  501 ms  420 ms  cr1.n54ny.ip.att.net [12.122.81.126]
13  196 ms    *      264 ms  cr2.cgcil.ip.att.net [12.122.1.2]
14  271 ms  498 ms  262 ms  cr1.cgcil.ip.att.net [12.122.2.53]
15  693 ms    *      818 ms  cr1.sffca.ip.att.net [12.122.4.121]
16  2623 ms  3043 ms    *    cr81.sj2ca.ip.att.net [12.122.1.118]
17  2678 ms  1638 ms    *    gar20.sffca.ip.att.net [12.122.110.41]
18  2789 ms  1705 ms  3752 ms  12.118.124.130
19  1011 ms  2177 ms  392 ms  12.7.210.177
20    *        *        *    Request timed out.
21    *        *        *    Request timed out.
22    *        *        *    Request timed out.
23    *        *        *    Request timed out.
24    *        *        *    Request timed out.
25    *        *        *    Request timed out.
26    *        *        *    Request timed out.

[#6]

Your connection is dropping.  The NTP replies are because your connection is subsequently reconnecting again.
Please plug your router into the BT Test socket, and report the Attenuation, SNR and Sync figures from your router.
B.

[#7]

Here is the stats after plugging it direct into the master socket.... have to say ive never seen this NTP [Censored] for months in the logs. Where has it suddenly come from?
Sat, 2000-01-01 00:01:08 - Initialize LCP.
Sat, 2000-01-01 00:01:08 - LCP is allowed to come up.
Sat, 2000-01-01 00:01:09 - CHAP authentication success
Sat, 2000-01-01 00:01:11 - <HTTP> Administrator login successful - IP:**EDIT**
Thu, 2011-04-07 22:49:33 - <NTP> Receive NTP Reply from 64.94.70.147
adie:quote

[#8]

hmmmmm
after 12 midnight now and the internet is flying again.............  what the hell is going on?

[#9]

have you gone over your package usage amount? you can check in the portal

[#10]

NTP = Network Time Protocol
64.94.70.147 = time-c.netgear.com
The router is using NTP to synchronize its clock with a server out on the network.
The time server looks to be owned by Netgear, so it looks to be a genuine request. NTP isn't likely to be an indication of a virus, and it won't be causing a high load on your internet connection. It certainly won't be slowing things down.

[#11]

we use a netgear router too and allways had the NTP message once router was started-up, never had a problem with speed

[#12]

Quote from: WWWombat

NTP = Network Time Protocol 64.94.70.147 = time-c.netgear.com The router is using NTP to synchronize its clock with a server out on the network. The time server looks to be owned by Netgear, so it looks to be a genuine request. NTP isn't likely to be an indication of a virus, and it won't be causing a high load on your internet connection. It certainly won't be slowing things down.

What if the router cant sync the time with that IP address (which is what happens on that tracert), would that not slow it down somehow?  I heard people talk about 12 hour leases or something.

[#13]

If NTP fails to synchronise, then the router will stay on whatever time it has stored internally.
If the router has some form of battery-back RTC (real time clock), then the router will continue to use that time as the basis, and "tick" onwards from that time. If it doesn't have an RTC, it will probably default to a time of 0 relative to the "Unix epoch" - which would be Jan 1st 1970.
You'll probably be able to see which when you look at the timestamps of the log messages in the web GUI.
And to be honest - that is probably the extend of the impact to most users. If you have set firewall rules based on time-of-day, then the rules would go awry, but I can't think of anything else.
DHCP lease times will be based on a duration, rather than an absolute time, and the router will still continue to "tick" at a very-close-to-proper rate.