My ongoing problems

[klipp]

I feel like I'm becoming a nuisance around here, always something to complain about but my internet is so screwed compared with 2 months ago.

I've accepted what I've been told that my Line Attenuation has jumped from 53db to 59db because of line degradation and nothing can or will be done about this.  I've accepted that my typical 4000kbps sync rate has been slashed in half to 2000kbps and will never improve, even though things like iplayer and live streaming no longer work.

Here's the latest.

At around about 10pm every evening my internet explorer becomes even slower.  Pages take over a minute to load, if at all.  By 11pm my internet is pretty much unusable so I switch off and go to bed, to find it is fixed in the morning.  And so the cycle continues.  Even now trying to use this forum is slower than using a 56k modem but I'm hoping this will post.

I live in Boston, Lincolnshire.  I am connected to the Peterborough metro node.

I've scanned around google and am unable to find any information regarding there being a problem.

I tried pinging idnet.net a few times just now, here's the results:

Code Select Expand

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

C:\Users\win7>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Request timed out.
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 27ms, Average = 22ms

C:\Users\win7>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Request timed out.
Request timed out.

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

C:\Users\win7>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms 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 = 20ms, Maximum = 22ms, Average = 20ms

C:\Users\win7>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Request timed out.
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Request timed out.

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

C:\Users\win7>

It's reaching the stage where I'm now wondering if this is all worth the hassle.  I appreciate that the problem is with BT so I'm not having a moan at IDNet.  It's just depressing to think that 2 months ago I had enjoyed a steady 4000kbps sync rate for many years and now I'm dealing with something you'd expect from the 1990s.

I don't expect anyone to be able to help me here.  I'm just venting.

[sof2er]

There's some packet loss going on which is why your speed is lower / different every time, probably nothing to do with your line but something at BT's end.

[Simon]

Just a thought, but you say Internet Explorer slows down at a given time.  As a shot in the dark, have you tried another browser?

[Steve]

And in addition are you using Vista as the OS?

[klipp]

Hi.

No I've not tried using a different browser.  Would that make a difference?  I'd have thought the packet loss evident in the pings I posted would suggest the loss of service would exist no matter which browser I use.

I use Windows 7.

I forgot to post this last night, but here is a tracert I did shortly after those pings:

Code Select Expand

C:\Users\win7>tracert idnet.net

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

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    21 ms    21 ms    21 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    21 ms    23 ms    21 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    28 ms     *        *     redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    28 ms    21 ms    21 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6     *       22 ms     *     www.idnet.net [212.69.36.10]
  7    21 ms    21 ms    22 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\win7>

As expected the packet loss has now gone and should be fine until around 10pm this evening.

Thanks.

[Steve]

I wonder if you've got some heavy downloaders on your exchange as congestion normally lessens at this time