Internetr Disconnects 7 million times a day. yet again

[#1]

Event Logging
This page summarizes the last events that have been recorded on your Technicolor Gateway. Choose a display filter...


Category:
Recorded Events

Time Message

Warning Nov 8 17:56:30 PPP link up (Internet) [91.125.126.186]

Info Nov 8 17:56:30 FIREWALL event (1 of 1): modified rules

Info Nov 8 17:56:30 FIREWALL event (1 of 1): created rules

Info Nov 8 17:56:30 FIREWALL event (1 of 22): deleted rules

Info Nov 8 17:56:30 PPP CHAP Receive success (Internet)

Info Nov 8 17:56:29 PPP CHAP Receive challenge from rhost PTN-AG01 (Internet)

Info Nov 8 17:56:29 PPP CHAP Receive challenge from rhost ERX21.Edinburgh4 (Internet)

Info Nov 8 17:55:16 FIREWALL event (1 of 1): modified rules

Info Nov 8 17:55:16 FIREWALL event (1 of 1): created rules

Warning Nov 8 17:55:16 PPP link down (Internet) [87.115.84.44]

Error Nov 8 17:49:40 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 58.42.194.142 Dst ip: 87.115.84.44 Type: Destination Unreachable Code: Port Unreacheable

Info Nov 8 17:49:17 CONFIGURATION mbus igd sync successfull

Info Nov 8 17:49:14 CONFIGURATION mbus atomic sync successful

Error Nov 8 17:48:09 UPnP framework enabled

Info Nov 8 17:48:09 FIREWALL event (1 of 33): modified rules

Info Nov 8 17:48:09 FIREWALL event (1 of 53): created rules

Info Nov 8 17:42:38 LOGIN User admin logged in on [HTTP] (from 192.168.1.65)

Info Nov 8 17:41:47 SNTP Synchronised to server: 212.159.13.49

Error Nov 8 17:41:47 SNTP Systemtime update: time setting 00:05:56 > new time setting: 17:41:47

Error Jan 1 00:04:44 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 71.49.105.37 Dst ip: 87.115.84.44 Type: Destination Unreachable Code: Port Unreacheable

Error Jan 1 00:00:57 [ANTI_SPOOFD] (err) llist_getobject_at for ENV.ANTI_SPOOFD's value failed

Warning Jan 1 00:00:56 PPP link up (Internet) [87.115.84.44]

Info Jan 1 00:00:56 PPP CHAP Receive success (Internet)

Info Jan 1 00:00:56 PPP CHAP Receive challenge from rhost PTW-AG04 (Internet)

Info Jan 1 00:00:55 PPP CHAP Receive challenge from rhost ERX21.Edinburgh4 (Internet)

Info Jan 1 00:00:50 xDSL linestate up (ITU-T G.992.1; downstream: 8128 kbit/s, upstream: 448 kbit/s; output Power Down: 13.9 dBm, Up: 12.3 dBm; line Attenuation Down: 8.0 dB, Up: 4.0 dB; snr Margin Down: 13.4 dB, Up: 22.0 dB)

Warning Jan 1 00:00:42 DHCS server up

Info Jan 1 00:00:42 FIREWALL event (1 of 1): deleted rules

Info Jan 1 00:00:42 FIREWALL level changed to Standard.

Error Jan 1 00:00:37 UPnP framework enabled

Error Jan 1 00:00:36 UPnP framework disabled

Error Jan 1 00:00:34 UPnP framework disabled

Info Jan 1 00:00:32 FIREWALL has been enabled

Error Jan 1 00:00:32 UPnP framework disabled

Info Jan 1 00:00:24 FIREWALL event (1 of 1): modified rules

Info Jan 1 00:00:24 FIREWALL event (1 of 1): created rules

Warning Jan 1 00:00:16 KERNEL Warm restart

Thats what it says on the Router logs..
don't know what else i can do, absolutely pathetic in my opinion. literally disconnects for around 30 seconds reconeccts for 4-5 minutes then disconnects again. same olf piece of doggy doo.
Info Jan 1 00:00:08 FIREWALL has been enabled

[#2]

Hi,
If you haven't already then I'd suggest going through the fault checker at https://faults.plus.net
We saw a few disconnections on Saturday, prior to this post being made, but not many since then. How's the line performing now?

[#3]

connection is absolute remel dingy. look at the state of my connection, cant even play a gb without lagging! please fix it xxxxx

C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=1899ms TTL=55
Reply from 74.125.230.105: bytes=32 time=1920ms TTL=55
Reply from 74.125.230.105: bytes=32 time=2043ms TTL=55
Reply from 74.125.230.105: bytes=32 time=1943ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1899ms, Maximum = 2043ms, Average = 1951ms
C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=310ms TTL=55
Reply from 74.125.230.105: bytes=32 time=116ms TTL=55
Reply from 74.125.230.105: bytes=32 time=62ms TTL=55
Reply from 74.125.230.105: bytes=32 time=44ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 310ms, Average = 133ms
C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=1284ms TTL=55
Reply from 74.125.230.105: bytes=32 time=1426ms TTL=55
Reply from 74.125.230.105: bytes=32 time=1411ms TTL=55
Reply from 74.125.230.105: bytes=32 time=1562ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1284ms, Maximum = 1562ms, Average = 1420ms
C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=552ms TTL=55
Reply from 74.125.230.105: bytes=32 time=447ms TTL=55
Reply from 74.125.230.105: bytes=32 time=424ms TTL=55
Reply from 74.125.230.105: bytes=32 time=422ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 422ms, Maximum = 552ms, Average = 461ms
C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=465ms TTL=55
Reply from 74.125.230.105: bytes=32 time=514ms TTL=55
Reply from 74.125.230.105: bytes=32 time=505ms TTL=55
Reply from 74.125.230.105: bytes=32 time=373ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 373ms, Maximum = 514ms, Average = 464ms
C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=413ms TTL=55
Reply from 74.125.230.105: bytes=32 time=414ms TTL=55
Reply from 74.125.230.105: bytes=32 time=331ms TTL=55
Reply from 74.125.230.105: bytes=32 time=376ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 331ms, Maximum = 414ms, Average = 383ms
C:\Users\Michael>ping google.com#
Ping request could not find host google.com#. Please check the name an
n.
C:\Users\Michael>ping google.com#
Ping request could not find host google.com#. Please check the name an
n.
C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=27ms TTL=55
Reply from 74.125.230.105: bytes=32 time=175ms TTL=55
Reply from 74.125.230.105: bytes=32 time=31ms TTL=55
Reply from 74.125.230.105: bytes=32 time=26ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 26ms, Maximum = 175ms, Average = 64ms
C:\Users\Michael>ping google.com
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=91ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=93ms TTL=55
Reply from 74.125.230.105: bytes=32 time=29ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 93ms, Average = 59ms
C:\Users\Michael>ping google.com -n 75
Pinging google.com [74.125.230.105] with 32 bytes of data:
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=100ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=93ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=94ms TTL=55
Reply from 74.125.230.105: bytes=32 time=27ms TTL=55
Reply from 74.125.230.105: bytes=32 time=105ms TTL=55
Reply from 74.125.230.105: bytes=32 time=99ms TTL=55
Reply from 74.125.230.105: bytes=32 time=78ms TTL=55
Reply from 74.125.230.105: bytes=32 time=32ms TTL=55
Reply from 74.125.230.105: bytes=32 time=75ms TTL=55
Reply from 74.125.230.105: bytes=32 time=26ms TTL=55
Reply from 74.125.230.105: bytes=32 time=68ms TTL=55
Reply from 74.125.230.105: bytes=32 time=24ms TTL=55
Reply from 74.125.230.105: bytes=32 time=62ms TTL=55
Reply from 74.125.230.105: bytes=32 time=24ms TTL=55
Reply from 74.125.230.105: bytes=32 time=60ms TTL=55
Reply from 74.125.230.105: bytes=32 time=26ms TTL=55
Reply from 74.125.230.105: bytes=32 time=58ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=48ms TTL=55
Reply from 74.125.230.105: bytes=32 time=26ms TTL=55
Reply from 74.125.230.105: bytes=32 time=48ms TTL=55
Reply from 74.125.230.105: bytes=32 time=31ms TTL=55
Reply from 74.125.230.105: bytes=32 time=57ms TTL=55
Reply from 74.125.230.105: bytes=32 time=270ms TTL=55
Reply from 74.125.230.105: bytes=32 time=329ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=31ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=22ms TTL=55
Reply from 74.125.230.105: bytes=32 time=32ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=106ms TTL=55
Reply from 74.125.230.105: bytes=32 time=46ms TTL=55
Reply from 74.125.230.105: bytes=32 time=156ms TTL=55
Reply from 74.125.230.105: bytes=32 time=27ms TTL=55
Reply from 74.125.230.105: bytes=32 time=102ms TTL=55
Reply from 74.125.230.105: bytes=32 time=484ms TTL=55
Reply from 74.125.230.105: bytes=32 time=575ms TTL=55
Reply from 74.125.230.105: bytes=32 time=587ms TTL=55
Reply from 74.125.230.105: bytes=32 time=702ms TTL=55
Reply from 74.125.230.105: bytes=32 time=775ms TTL=55
Reply from 74.125.230.105: bytes=32 time=778ms TTL=55
Reply from 74.125.230.105: bytes=32 time=382ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=23ms TTL=55
Reply from 74.125.230.105: bytes=32 time=47ms TTL=55
Reply from 74.125.230.105: bytes=32 time=30ms TTL=55
Reply from 74.125.230.105: bytes=32 time=45ms TTL=55
Reply from 74.125.230.105: bytes=32 time=27ms TTL=55
Reply from 74.125.230.105: bytes=32 time=39ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=36ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=28ms TTL=55
Reply from 74.125.230.105: bytes=32 time=27ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=80ms TTL=55
Reply from 74.125.230.105: bytes=32 time=25ms TTL=55
Reply from 74.125.230.105: bytes=32 time=106ms TTL=55
Reply from 74.125.230.105: bytes=32 time=31ms TTL=55
Reply from 74.125.230.105: bytes=32 time=104ms TTL=55
Reply from 74.125.230.105: bytes=32 time=231ms TTL=55
Reply from 74.125.230.105: bytes=32 time=97ms TTL=55
Reply from 74.125.230.105: bytes=32 time=23ms TTL=55
Reply from 74.125.230.105: bytes=32 time=92ms TTL=55
Reply from 74.125.230.105: bytes=32 time=26ms TTL=55
Reply from 74.125.230.105: bytes=32 time=200ms TTL=55
Reply from 74.125.230.105: bytes=32 time=195ms TTL=55
Reply from 74.125.230.105: bytes=32 time=177ms TTL=55
Reply from 74.125.230.105: bytes=32 time=131ms TTL=55
Reply from 74.125.230.105: bytes=32 time=86ms TTL=55
Reply from 74.125.230.105: bytes=32 time=28ms TTL=55
Ping statistics for 74.125.230.105:
    Packets: Sent = 75, Received = 75, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 778ms, Average = 118ms
C:\Users\Michael>ping google.com -n 75#
Pinging google.com [74.125.230.133] with 32 bytes of data:
Reply from 74.125.230.133: bytes=32 time=24ms TTL=56
Reply from 74.125.230.133: bytes=32 time=89ms TTL=56
Reply from 74.125.230.133: bytes=32 time=23ms TTL=56
Reply from 74.125.230.133: bytes=32 time=82ms TTL=56
Reply from 74.125.230.133: bytes=32 time=23ms TTL=56
Reply from 74.125.230.133: bytes=32 time=79ms TTL=56
Reply from 74.125.230.133: bytes=32 time=576ms TTL=56
Reply from 74.125.230.133: bytes=32 time=423ms TTL=56
Reply from 74.125.230.133: bytes=32 time=30ms TTL=56
Reply from 74.125.230.133: bytes=32 time=74ms TTL=56
Reply from 74.125.230.133: bytes=32 time=32ms TTL=56
Reply from 74.125.230.133: bytes=32 time=75ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=57ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=50ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=81ms TTL=56
Reply from 74.125.230.133: bytes=32 time=47ms TTL=56
Reply from 74.125.230.133: bytes=32 time=43ms TTL=56
Reply from 74.125.230.133: bytes=32 time=25ms TTL=56
Reply from 74.125.230.133: bytes=32 time=38ms TTL=56
Reply from 74.125.230.133: bytes=32 time=29ms TTL=56
Reply from 74.125.230.133: bytes=32 time=41ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=31ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=111ms TTL=56
Reply from 74.125.230.133: bytes=32 time=28ms TTL=56
Reply from 74.125.230.133: bytes=32 time=117ms TTL=56
Reply from 74.125.230.133: bytes=32 time=108ms TTL=56
Reply from 74.125.230.133: bytes=32 time=302ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=96ms TTL=56
Reply from 74.125.230.133: bytes=32 time=31ms TTL=56
Reply from 74.125.230.133: bytes=32 time=90ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=89ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=83ms TTL=56
Reply from 74.125.230.133: bytes=32 time=34ms TTL=56
Reply from 74.125.230.133: bytes=32 time=80ms TTL=56
Reply from 74.125.230.133: bytes=32 time=29ms TTL=56
Reply from 74.125.230.133: bytes=32 time=70ms TTL=56
Reply from 74.125.230.133: bytes=32 time=28ms TTL=56
Reply from 74.125.230.133: bytes=32 time=63ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=61ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=57ms TTL=56
Reply from 74.125.230.133: bytes=32 time=34ms TTL=56
Reply from 74.125.230.133: bytes=32 time=53ms TTL=56
Reply from 74.125.230.133: bytes=32 time=30ms TTL=56
Reply from 74.125.230.133: bytes=32 time=49ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=39ms TTL=56
Reply from 74.125.230.133: bytes=32 time=24ms TTL=56
Reply from 74.125.230.133: bytes=32 time=32ms TTL=56
Reply from 74.125.230.133: bytes=32 time=25ms TTL=56
Reply from 74.125.230.133: bytes=32 time=32ms TTL=56
Reply from 74.125.230.133: bytes=32 time=29ms TTL=56
Reply from 74.125.230.133: bytes=32 time=27ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=108ms TTL=56
Reply from 74.125.230.133: bytes=32 time=26ms TTL=56
Reply from 74.125.230.133: bytes=32 time=886ms TTL=56
Reply from 74.125.230.133: bytes=32 time=930ms TTL=56
Reply from 74.125.230.133: bytes=32 time=960ms TTL=56
Reply from 74.125.230.133: bytes=32 time=1038ms TTL=56
Reply from 74.125.230.133: bytes=32 time=1026ms TTL=56
Reply from 74.125.230.133: bytes=32 time=1070ms TTL=56
Reply from 74.125.230.133: bytes=32 time=505ms TTL=56
Reply from 74.125.230.133: bytes=32 time=30ms TTL=56
Ping statistics for 74.125.230.133:
    Packets: Sent = 75, Received = 75, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 1070ms, Average = 143ms
C:\Users\Michael>

[#4]

did the faults checker and the best it came up with was restart the router and replace the microfilter, which has been done around a milllion times. also changed from the default plusnet router to the dgn netgear. which when i was on virgin media was on constant 7.2 mbps and 19 ping.

[#5]

Hello Mick, that's not looking at all good. Can you try a ping to ntp.plus.net a few times?
If you still have the 582n on line can you post the TG582n Full DSL stats?
If it's the Netgear, wherever you get it's stats from.
The constant 7.2Mbps you mentioned was that download speed or sync speed? I'm assuming you meant download speed.

[#6]

C:\Users\Michael>ping ntp.plus.net -n 25
Pinging ntp.plus.net [212.159.13.50] with 32 bytes of data:
Reply from 212.159.13.50: bytes=32 time=22ms TTL=59
Reply from 212.159.13.50: bytes=32 time=34ms TTL=59
Reply from 212.159.13.50: bytes=32 time=25ms TTL=59
Reply from 212.159.13.50: bytes=32 time=32ms TTL=59
Reply from 212.159.13.50: bytes=32 time=23ms TTL=59
Reply from 212.159.13.50: bytes=32 time=23ms TTL=59
Reply from 212.159.13.50: bytes=32 time=23ms TTL=59
Reply from 212.159.13.50: bytes=32 time=23ms TTL=59
Reply from 212.159.13.50: bytes=32 time=167ms TTL=59
Reply from 212.159.13.50: bytes=32 time=22ms TTL=59
Reply from 212.159.13.50: bytes=32 time=100ms TTL=59
Reply from 212.159.13.50: bytes=32 time=65ms TTL=59
Reply from 212.159.13.50: bytes=32 time=108ms TTL=59
Reply from 212.159.13.50: bytes=32 time=24ms TTL=59
Reply from 212.159.13.50: bytes=32 time=87ms TTL=59
Reply from 212.159.13.50: bytes=32 time=24ms TTL=59
Reply from 212.159.13.50: bytes=32 time=83ms TTL=59
Reply from 212.159.13.50: bytes=32 time=30ms TTL=59
Reply from 212.159.13.50: bytes=32 time=77ms TTL=59
Reply from 212.159.13.50: bytes=32 time=22ms TTL=59
Reply from 212.159.13.50: bytes=32 time=67ms TTL=59
Reply from 212.159.13.50: bytes=32 time=22ms TTL=59
Reply from 212.159.13.50: bytes=32 time=75ms TTL=59
Reply from 212.159.13.50: bytes=32 time=145ms TTL=59
Reply from 212.159.13.50: bytes=32 time=70ms TTL=59
Ping statistics for 212.159.13.50:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 167ms, Average = 55ms

Still lagging hard as hell on games!
and my stats are  Modem
ADSL Firmware Version 3.4.4.1.0.1
Modem Status Connected
DownStream Connection Speed 8128 Kbps
UpStream Connection Speed 448 Kbps
VPI 0
VCI 38

[#7]

Well at least your sync speed is OK. The shortest of the ping times would suggest Interleaving is Off, but the pings are extremely variable which to me suggests congestion.
When you had the TG582n on line, was that the one that had the firmware update?
Is the modem/router positioned so that it get's plenty of ventilation - eg. it's not sat on a carpet? And hopefully not sat where there's a lot of heat?

[#8]

Router was on tob of a glass table. on its own. interleaving is off. but its been fine for like the last 2 months. i still have the disconnects but. i literally cant even play 1 game of call of duty without lagging half of the game. its getting endless.

[#9]

If you are getting the same with two different modem/routers it suggests the problem is probably at the exchange, but can we be clear about what you mean by disconnects. Is it disconnects from your game, ie you are getting kicked off, or are the disconnects such that you can't browse either?
Has the Netgear got a log you can look at?

[#10]

Hi Mick,
Can you make sure you complete the questions in the faults troubleshooter? It's not fully submitted through to us yet.

[#11]

i did, under the username jillywilly, and im on 2.4 mbps 150 ping atm, literally astounded. taking me 3 minutes to load a webpage.,

[#12]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael>ping ftp.plus.net
Pinging ftp.plus.net [212.159.9.91] with 32 bytes of data:
Reply from 212.159.9.91: bytes=32 time=1086ms TTL=249
Reply from 212.159.9.91: bytes=32 time=1027ms TTL=249
Reply from 212.159.9.91: bytes=32 time=1121ms TTL=249
Reply from 212.159.9.91: bytes=32 time=1266ms TTL=249
Ping statistics for 212.159.9.91:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1027ms, Maximum = 1266ms, Average = 1125ms
C:\Users\Michael>ping ftp.plus.net
Pinging ftp.plus.net [212.159.9.91] with 32 bytes of data:
Reply from 212.159.9.91: bytes=32 time=1351ms TTL=249
Reply from 212.159.9.91: bytes=32 time=1402ms TTL=249
Reply from 212.159.9.91: bytes=32 time=1407ms TTL=249
Reply from 212.159.9.91: bytes=32 time=1462ms TTL=249
Ping statistics for 212.159.9.91:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1351ms, Maximum = 1462ms, Average = 1405ms
C:\Users\Michael>tracert ftp.plus.net
Tracing route to ftp.plus.net [212.159.9.91]
over a maximum of 30 hops:
  1    <1 ms    1 ms    <1 ms  192.168.0.1
  2  695 ms  795 ms  802 ms  lo0-central10.pcl-ag04.plus.net [195.166.128.185
]
  3  539 ms  540 ms  602 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.17
2]
  4  612 ms  619 ms  608 ms  xe-0-2-0.pcl-cr01.plus.net [212.159.0.204]
  5  738 ms  750 ms  628 ms  po2.pcl-gw01.plus.net [195.166.129.41]
  6  628 ms  638 ms  692 ms  gi5-8.ptp-cr01.plus.net [84.93.224.48]
  7  833 ms  884 ms  939 ms  vlan2657.ptp-elb01.plus.net [84.93.224.36]
  8  720 ms  753 ms  840 ms  homepages.plus.net [212.159.9.91]
Trace complete.

[#13]

Are these tests wired or wireless?
The line seems to be more stable over the last day or so, with only 1 disconnection that we can see since 7pm on the 11th November.
Taking a look at your exchange, it is showing as AMBER for capacity, so that won't be helping at all. As the threshold on the exchange has been exceeded an upgrade should already be in planning, these normally take around 2 weeks based on the work involved at the exchange. So hopefully you won't have this issue much longer.

[#14]

As Chris said about wireless, is the xbox connected by ethernet?

[#15]

For the last few days, until this morning at least, the connection has looked fine. Is the router switched off now, or have you lost connection altogether?
Tony