Slow internet

Started by Westy, Jul 12, 2011, 21:28:36

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Westy

This has been a regular occurrence over the last couple of days.



Only computer on router, wireless turned off. Using TBB monitor to make sure nothing on my computer is download/uploading.

So what else can I check for to make sure the problem is not my end before I send in another complaint about poor service?

.Griff.

My first port of call would be to find out what IP Profile you're on - http://speedtester.bt.com/

Westy

Download speedachieved during the test was - 1824 Kbps
For your connection, the acceptable range of speeds is 400-2000 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 2000 Kbps



Also did some tracert's

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

C:\Users\Westy>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   393 ms   354 ms   326 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3   293 ms   234 ms   213 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4   198 ms   205 ms   192 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5   217 ms   160 ms   166 ms  212.58.238.153
  6   229 ms   252 ms   269 ms  te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
  7   265 ms   186 ms   227 ms  212.58.255.12
  8   162 ms   137 ms   149 ms  bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]

Trace complete.

C:\Users\Westy>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2   144 ms   167 ms   240 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3   197 ms   206 ms   181 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4   118 ms    98 ms    77 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    54 ms    59 ms    44 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    69 ms    75 ms    54 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Westy>tracert www.google.co.uk

Tracing route to www.l.google.com [209.85.146.104]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  192.168.0.1
  2    81 ms    87 ms    90 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3   185 ms   184 ms   204 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4   155 ms   166 ms   160 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   161 ms   199 ms   147 ms  google1.lonap.net [193.203.5.136]
  6   121 ms   135 ms   134 ms  209.85.255.76
  7   102 ms    98 ms    86 ms  209.85.253.88
  8   241 ms   270 ms   286 ms  66.249.95.173
  9   171 ms   170 ms   177 ms  209.85.249.31
10   116 ms   116 ms    83 ms  216.239.46.73
11   238 ms   200 ms   199 ms  bru01s01-in-f104.1e100.net [209.85.146.104]

Trace complete.

C:\Users\Westy>



Steve

It's very similar to what happened earlier this year isn't. You've had some instability and your profile's taken a dive but your sync has already recovered. I don't recall you ever found a reason for the issue earlier this year. It surely has to be a local issue i.e between your router and the local exchange. I think I would pass those figures on to support.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

jameshurrell

A profile of 2000 could suggest that the profile is "stuck"....

In anycase, with a sync of 8128, if the IP profile hasn't increased by now (nearly two days later) I would suggest a call to support.