Internet is at crawl.

[zappaDPJ]

I've been in and out of the house all day and only on-line for a couple of hours but I've not caught any problems yet. Perhaps we are sharing a gremlin with a bus pass 

[zappaDPJ]

OK, here we go. I'd been talking to people on comms for around 45 minutes with no apparent problems and then got voice lag. I ran my batch test immediately and got the following results. It was started at 02:09 am 02:05:10.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>ping google.co.uk

Pinging google.co.uk [209.85.227.103] with 32 bytes of data:
Reply from 209.85.227.103: bytes=32 time=19ms TTL=56
Reply from 209.85.227.103: bytes=32 time=24ms TTL=56
Reply from 209.85.227.103: bytes=32 time=19ms TTL=56
Reply from 209.85.227.103: bytes=32 time=19ms TTL=56

Ping statistics for 209.85.227.103:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 19ms, Maximum = 24ms, Average = 20ms

C:\Users\zappaDPJ>tracert google.com

Tracing route to google.com [209.85.227.105]
over a maximum of 30 hops:

C:\Users\zappaDPJ>tracert google.co.uk

Tracing route to google.co.uk [209.85.227.99]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    13 ms    12 ms    12 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    12 ms    12 ms    12 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    12 ms    11 ms    14 ms  195.66.224.125
 5    13 ms    13 ms    13 ms  64.233.175.25
 6    18 ms    20 ms    18 ms  72.14.232.134
 7    18 ms    19 ms    18 ms  216.239.49.45
 8     *       27 ms     *     209.85.243.97
 9    18 ms    19 ms    18 ms  wy-in-f99.1e100.net [209.85.227.99]

Trace complete.

C:\Users\zappaDPJ>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=179ms TTL=122
Reply from 212.58.224.138: bytes=32 time=188ms TTL=122
Reply from 212.58.224.138: bytes=32 time=217ms TTL=122
Reply from 212.58.224.138: bytes=32 time=14ms TTL=122

Ping statistics for 212.58.224.138:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 14ms, Maximum = 217ms, Average = 149ms

C:\Users\zappaDPJ>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

 1     1 ms     1 ms    <1 ms  192.168.0.1
 2   161 ms   365 ms   375 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3   390 ms   338 ms   365 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   275 ms   402 ms   360 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
 5   402 ms   398 ms   469 ms  212.58.238.153
 6   240 ms   398 ms   440 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

C:\Users\zappaDPJ>ping idnet.co.uk

Pinging idnet.co.uk [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=195ms TTL=59
Reply from 212.69.36.10: bytes=32 time=203ms TTL=59
Reply from 212.69.36.10: bytes=32 time=233ms TTL=59
Reply from 212.69.36.10: bytes=32 time=205ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 195ms, Maximum = 233ms, Average = 209ms

C:\Users\zappaDPJ>tracert idnet.co.uk

Tracing route to idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

 1     1 ms    13 ms     7 ms  192.168.0.1
 2   130 ms   143 ms   144 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3   152 ms   260 ms   164 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   162 ms   151 ms   176 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5   207 ms   199 ms   192 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6   207 ms   212 ms   232 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\zappaDPJ>ping etabetapi-guild.com

Pinging etabetapi-guild.com [195.62.28.79] with 32 bytes of data:
Reply from 195.62.28.79: bytes=32 time=12ms TTL=57
Reply from 195.62.28.79: bytes=32 time=12ms TTL=57
Reply from 195.62.28.79: bytes=32 time=12ms TTL=57
Reply from 195.62.28.79: bytes=32 time=13ms TTL=57

Ping statistics for 195.62.28.79:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 12ms, Maximum = 13ms, Average = 12ms

C:\Users\zappaDPJ>tracert etabetapi-guild.com

Tracing route to etabetapi-guild.com [195.62.28.79]
over a maximum of 30 hops:

 1     2 ms     8 ms    11 ms  192.168.0.1
 2    18 ms    12 ms    21 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    12 ms    20 ms    12 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   256 ms   346 ms   342 ms  lonap1.enta.net [193.203.5.134]
 5   259 ms   291 ms   295 ms  te5-3.telehouse-east2.core.enta.net [87.127.236.
37]
 6   303 ms   278 ms   327 ms  te4-4.telehouse-east.core.enta.net [87.127.236.9
7]
 7   366 ms   283 ms   275 ms  78-33-51-146.static.enta.net [78.33.51.146]
 8   308 ms   315 ms   199 ms  euroconnex-1.br1.core.misp.co.uk [217.112.86.107
]
 9   154 ms   176 ms    33 ms  ge-1-377.captain.core.misp.co.uk [91.198.165.5]

10    23 ms    14 ms    14 ms  kronos.servers.rbl-mer.misp.co.uk [195.62.28.79]


Trace complete.

C:\Users\zappaDPJ>ping vbulletin.com

Pinging vbulletin.com [67.201.17.239] with 32 bytes of data:
Reply from 67.201.17.239: bytes=32 time=162ms TTL=242
Reply from 67.201.17.239: bytes=32 time=173ms TTL=242
Reply from 67.201.17.239: bytes=32 time=180ms TTL=242
Reply from 67.201.17.239: bytes=32 time=164ms TTL=242

Ping statistics for 67.201.17.239:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 162ms, Maximum = 180ms, Average = 169ms

C:\Users\zappaDPJ>tracert vbulletin.com

Tracing route to vbulletin.com [67.201.17.239]
over a maximum of 30 hops:

 1     1 ms    <1 ms     1 ms  192.168.0.1
 2   334 ms   319 ms   327 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3   317 ms   350 ms   336 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   345 ms   334 ms   325 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5   439 ms   466 ms   222 ms  75-126-245-83.packetexchange.net [83.245.126.75]

 6    97 ms   106 ms   106 ms  te1-3.cr01.iad01.us.mzima.net [69.174.120.97]
 7   122 ms   108 ms   122 ms  te1-3.cr01.atl01.us.mzima.net [69.174.120.53]
 8   143 ms   137 ms   129 ms  te0-1.cr01.dfw01.us.mzima.net [69.174.120.49]
 9   161 ms   161 ms   164 ms  te1-1.cr01.phx01.us.mzima.net [69.174.120.37]
10   160 ms   161 ms   172 ms  te1-1.cr01.lax02.us.mzima.net [69.174.120.33]
11   162 ms   181 ms   172 ms  xe1-0.cr01.lax01.mzima.net [64.235.224.181]
12   172 ms   162 ms   162 ms  xe0-0.cr01.lax06.us.mzima.net [216.193.255.98]
13   161 ms   163 ms   164 ms  67.201.17.150
14   493 ms   489 ms   430 ms  www.vbulletin.com [67.201.17.239]

Trace complete.

Here are two speed tests conducted immediately afterwards in sequence.

Download speedachieved during the test was - 5705 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :7584 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 6500 Kbps

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

Here's the same group of tests run at 02:21 am 02:05:10 (12 minutes later)

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>ping google.co.uk

Pinging google.co.uk [209.85.227.99] with 32 bytes of data:
Reply from 209.85.227.99: bytes=32 time=17ms TTL=56
Reply from 209.85.227.99: bytes=32 time=17ms TTL=56
Reply from 209.85.227.99: bytes=32 time=18ms TTL=56
Reply from 209.85.227.99: bytes=32 time=18ms TTL=56

Ping statistics for 209.85.227.99:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 17ms, Maximum = 18ms, Average = 17ms

C:\Users\zappaDPJ>tracert google.co.uk

Tracing route to google.co.uk [209.85.227.99]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    12 ms    11 ms    12 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    12 ms    12 ms    11 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    17 ms    12 ms    12 ms  195.66.224.125
 5    12 ms    13 ms    12 ms  64.233.175.25
 6    18 ms    19 ms    18 ms  72.14.232.134
 7    18 ms    18 ms    18 ms  209.85.252.83
 8     *       28 ms     *     209.85.243.101
 9    18 ms    19 ms    19 ms  wy-in-f99.1e100.net [209.85.227.99]

Trace complete.

C:\Users\zappaDPJ>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=11ms TTL=122
Reply from 212.58.224.138: bytes=32 time=11ms TTL=122
Reply from 212.58.224.138: bytes=32 time=10ms TTL=122
Reply from 212.58.224.138: bytes=32 time=11ms TTL=122

Ping statistics for 212.58.224.138:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 10ms, Maximum = 11ms, Average = 10ms

C:\Users\zappaDPJ>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    12 ms    12 ms    12 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    11 ms    15 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    12 ms    12 ms    12 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
 5    81 ms    12 ms    12 ms  212.58.238.153
 6    11 ms    12 ms    11 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

C:\Users\zappaDPJ>ping idnet.co.uk

Pinging idnet.co.uk [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 11ms, Maximum = 12ms, Average = 11ms

C:\Users\zappaDPJ>tracert idnet.co.uk

Tracing route to idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    14 ms    11 ms    12 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    12 ms    12 ms    12 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    12 ms    12 ms    13 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    13 ms    13 ms    12 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    11 ms    12 ms    12 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\zappaDPJ>ping etabetapi-guild.com

Pinging etabetapi-guild.com [195.62.28.79] with 32 bytes of data:
Reply from 195.62.28.79: bytes=32 time=12ms TTL=57
Reply from 195.62.28.79: bytes=32 time=12ms TTL=57
Reply from 195.62.28.79: bytes=32 time=12ms TTL=57
Reply from 195.62.28.79: bytes=32 time=12ms TTL=57

Ping statistics for 195.62.28.79:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 12ms, Maximum = 12ms, Average = 12ms

C:\Users\zappaDPJ>tracert etabetapi-guild.com

Tracing route to etabetapi-guild.com [195.62.28.79]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    12 ms    12 ms    38 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    12 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    12 ms    12 ms    12 ms  lonap1.enta.net [193.203.5.134]
 5    12 ms    13 ms    13 ms  te5-3.telehouse-east2.core.enta.net [87.127.236.
37]
 6    12 ms    12 ms    12 ms  te4-4.telehouse-east.core.enta.net [87.127.236.9
7]
 7    12 ms    13 ms    12 ms  78-33-51-146.static.enta.net [78.33.51.146]
 8    12 ms    13 ms    13 ms  euroconnex-1.br1.core.misp.co.uk [217.112.86.107
]
 9    14 ms    13 ms    14 ms  ge-1-377.captain.core.misp.co.uk [91.198.165.5]

10    13 ms    13 ms    13 ms  kronos.servers.rbl-mer.misp.co.uk [195.62.28.79]


Trace complete.

C:\Users\zappaDPJ>ping vbulletin.com

Pinging vbulletin.com [67.201.17.239] with 32 bytes of data:
Reply from 67.201.17.239: bytes=32 time=161ms TTL=242
Reply from 67.201.17.239: bytes=32 time=162ms TTL=242
Reply from 67.201.17.239: bytes=32 time=162ms TTL=242
Reply from 67.201.17.239: bytes=32 time=161ms TTL=242

Ping statistics for 67.201.17.239:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 161ms, Maximum = 162ms, Average = 161ms

C:\Users\zappaDPJ>tracert vbulletin.com

Tracing route to vbulletin.com [67.201.17.239]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    12 ms    12 ms    13 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    12 ms    12 ms    12 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    12 ms    13 ms    13 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    20 ms    17 ms    18 ms  75-126-245-83.packetexchange.net [83.245.126.75]

 6    99 ms   107 ms   109 ms  te1-3.cr01.iad01.us.mzima.net [69.174.120.97]
 7   109 ms   108 ms   108 ms  te1-3.cr01.atl01.us.mzima.net [69.174.120.53]
 8   140 ms   127 ms   141 ms  te0-1.cr01.dfw01.us.mzima.net [69.174.120.49]
 9   152 ms   158 ms   160 ms  te1-1.cr01.phx01.us.mzima.net [69.174.120.37]
10   168 ms   161 ms   162 ms  te1-1.cr01.lax02.us.mzima.net [69.174.120.33]
11   169 ms   162 ms   161 ms  xe1-0.cr01.lax01.mzima.net [64.235.224.181]
12   167 ms   161 ms   162 ms  xe0-0.cr01.lax06.us.mzima.net [216.193.255.98]
13   162 ms   163 ms   161 ms  67.201.17.150
14   163 ms   162 ms   162 ms  www.vbulletin.com [67.201.17.239]

Trace complete.

C:\Users\zappaDPJ>

It's far to late for me to really look at the data now but I can see quite a few points of note after a cursory glance. I did attempt to run a few other tests in the same sequence but they failed abysmally so I've hopefully edited out a lot of spurious data

[Niall]

After I posted on here last night I decided to test a couple of things with random downloads. I tried a normal http download which again showed my profile has dropped, but with torrents, no matter how well seeded (from legal torrents I might add!) I don't seem to get over 220 Kb/S. Webpages seem choppy at loading (even here) on occasion. There seems to be a pause as it gets to the last 20% loading a page.

If I get a chance later I'll try with IE too when I spot the problem happening again. The webpage loading, could just be an issue with a security problem. I'm not certain, but I think it may be related to Ad-Aware as the problems with web pages seem to have started around the same time I installed that. The trouble is, I've also updated NOD32 twice and Firefox has updated along with Anti-Spyware around the same time. It could easily be related to any of them, and if so I've no real way of testing that.

Ironically, after I posted this I checked my router and the profile has reset itself to 10459 again. When I posted this reply though, it took about 3 seconds to post. Again I've no way of knowing if that's the forum delay, security software or my connection.

[Niall]

I just reset the router, just out of curiosity and it's reset the profile slightly higher. Now pages load much faster, well instantly actually.



C:\Users\Niall>tracert www.idnetters.co.uk

Tracing route to www.idnetters.co.uk [212.69.36.28]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    17 ms    17 ms    16 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    17 ms    17 ms    17 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    17 ms    16 ms    17 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    17 ms    17 ms    18 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    17 ms    17 ms    17 ms  hosting2.idnet.net [212.69.36.28]

Trace complete.

C:\Users\Niall>ping www.idnetters.co.uk

Pinging www.idnetters.co.uk [212.69.36.28] with 32 bytes of data:
Reply from 212.69.36.28: bytes=32 time=17ms TTL=59
Reply from 212.69.36.28: bytes=32 time=16ms TTL=59
Reply from 212.69.36.28: bytes=32 time=17ms TTL=59
Reply from 212.69.36.28: bytes=32 time=16ms TTL=59

Ping statistics for 212.69.36.28:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 17ms, Average = 16ms

C:\Users\Niall>

That seems to have cleared what ever my problem was. I'll test some random torrents in a minute. I need a cuppa and some brekkie

[Steve]

Zap why is the first hop to the router variable? The rest I see what you mean someone' s stood on the line somewhere.

[Steve]

Niall, I am finding the forum software 'slow' to post at the present moment.

[Niall]

I've FINALLY got the BT Speed test site to work for me.

Download speedachieved during the test was - 9932 Kbps
For your connection, the acceptable range of speedsis 1000-99999 Kbps.
Additional Information:
Your DSL Connection Rate :10598 Kbps(DOWN-STREAM), 1083 Kbps(UP-STREAM)
IP Profile for your line is - 9000 Kbps
The throughput of Best Efforts (BE) classes achieved during the test is - 16.94:23.29:59.78 (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.

I've been trying that site for months and always got an error. It works now. It's not what my router is saying, and the BT site itself says that my line should get 14mb. Hey ho, it's working at the moment though

[zappaDPJ]

Zap why is the first hop to the router variable? The rest I see what you mean someone' s stood on the line somewhere.

I have absolutely no idea at all, until you pointed it out I hadn't even noticed it. How very strange. Perhaps someone with more knowledge than me can shed some light on it 

[zappaDPJ]

I've FINALLY got the BT Speed test site to work for me.

Same here, it stopped working for me when they last changed it and it's only quite recently I've been able to get it to give me a result again.

[Niall]

Normally when you see a varying ping to the router, it indicates a problem on the home side of your network. Cable or router issues, possibly the network card. The only time I've ever experienced it is when a PCI network card died on me, other than that the only thing I can think of is a busy network when you access the router, although I don't know if that effects your ping to the router (I wouldn't have thought so though).

I suppose it could also be network card drivers, thinking about it.

[pctech]

would echo Naill's advice Zap.

RTA (Round Trip Average) between your router and PC should be under 1 millisecond

Check your cable for damage and maybe try a factory reset of the router (be aware your profile may fall a bit when you reconnect as BT's DLM seems to work in mysterious ways)

[Steve]

Sometimes I get the odd blip if it's busy doing something else although when you want to demonstrate it I can't 

[pctech]

RTA on the second hop seems to increase quite a bit if you run a tracert while downloading or streaming (then again my connection runs at 1.6Mbps so not got a lot of bandwidth to play with)

[Steve]

If I am copying a large file to another local machine sometimes I can demonstrate an increase in the RTA of the first hop but not always.

[pctech]

I reckon Gizmoi has invaded Zap's router. 

[Gary]

These are mine, over WiFi.

Ping has started...

PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=31.427 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=31.849 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=30.502 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=32.406 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=31.881 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=31.598 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=31.781 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=29.899 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=31.346 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=31.706 ms

--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 29.899/31.440/32.406/0.691 ms

[Rik]

about 20 sec's a page now rik with every site, i have a 6.5 meg profile.

So whats the problem and how do we sort it?

I don't know, but the most likely explanation would be exchange congestion were it not for the speedtests. Do a tracert to the affected sites when there's a problem, then do a BT speed test, and let support have the results.

[adamr8965]

rite how do i do that??

Internet is working fine this morning, well it was after about 9pm downloads reamined fine. However on this morning all is ok apart from idnetters which is still running slow.

[Rik]

Tracert? Hit Start > Run > type CMD in the window and hit enter. That will bring you up a DOS-like window. In that, type tracert <url> and hit enter. The trace will start. When it's complete, right click on the title bar, select Edit > Select All, then hit enter to copy the text. Paste that into an email, or notepad if you want to build a group of them before sending.

[adamr8965]

doing it now rik, half on them are timing out doing it on ebay.

[adamr8965]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Y>tracert www.ebay.co.uk

Tracing route to hp-intl-uk.ebay.com [66.135.200.146]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.0.1
  2     *       37 ms    36 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    37 ms     *       36 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    37 ms    37 ms    36 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
  5    37 ms     *       37 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
  6    37 ms    37 ms    38 ms  te4-3.ccr01.lon01.atlas.cogentco.com [130.117.1.
217]
  7    45 ms     *       44 ms  te0-3-0-0.ccr21.ams03.atlas.cogentco.com [130.11
7.48.142]
  8    51 ms     *        *     te0-1-0-1.ccr21.fra03.atlas.cogentco.com [130.11
7.1.161]
  9     *        *       56 ms  dtag.fra03.atlas.cogentco.com [130.117.14.150]
10   197 ms   197 ms   197 ms  217.239.40.102
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
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.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

Trace complete.

C:\Users\Y>


this what happened just now.

[Rik]

Load instantly, but the tracert times out for me too. It probably just indicates that routers after hop 10 don't respond to ICMP traffic (pings)

tracert www.ebay.co.uk

Tracing route to hp-intl-uk.ebay.com [66.135.200.146]
over a maximum of 30 hops:

 1     1 ms    <1 ms     1 ms  192.168.1.254
 2    13 ms    14 ms    15 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    14 ms    13 ms    11 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
 4    14 ms    13 ms    15 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
 5    14 ms    15 ms    13 ms  te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
 6    13 ms    14 ms    15 ms  te4-2.ccr01.lon01.atlas.cogentco.com [130.117.1.201]
 7    21 ms    21 ms    21 ms  te0-2-0-0.ccr21.ams03.atlas.cogentco.com [154.54.28.157]
 8    28 ms    27 ms    27 ms  te0-0-0-1.ccr21.fra03.atlas.cogentco.com [130.117.0.146]
 9    28 ms    27 ms    29 ms  dtag.fra03.atlas.cogentco.com [130.117.14.106]
10   178 ms   177 ms   177 ms  217.239.40.102
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.

[pctech]

likely to be the result of firewalls at ebay's end I reckon.

[Rik]

Indeed, but the page is served quickly for me, but not, apparently, for Adam. 

[adamr8965]

i have just found my problem, its my ps3. Had it on last nite everything was slow when the little one was watching a film, internet ran fine when switched it off.
Same this morning ok before on, slow when switched on. Just switched it off now, internet pages running full speed again.

What the hell is going on?