Crazy slow internet tonight

Started by klipp, Mar 27, 2010, 23:58:54

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

klipp


zappaDPJ

That's not good at all. I've had no problems (in London) tonight so it might be a local issue.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

adamr8965

Wow that is slow!!! No problems up here in yorkshire.

Gary

All ok here too. This is over WIFI, not hard wired.

Damned, if you do damned if you don't

Rik

OK here too - it sounds like exchange congestion to me, check again at different times of day.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Mar 28, 2010, 10:21:32
OK here too - it sounds like exchange congestion to me, check again at different times of day.

Not altogether sure Rik.  My exchange is not listed as being congested but the internet was dog slow last night.  I also had some disconnections during the day, but since we had torrential rain that's nothing unusual.


Rik

Not being listed and not being congested are, sadly, two different things, Tac. BT can be unforthcoming when it comes to the information, or it can be a backhaul capacity issue which they don't publicise at all. Did the disconnections affect your profile by any chance?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Mar 28, 2010, 10:35:56
Not being listed and not being congested are, sadly, two different things, Tac. BT can be unforthcoming when it comes to the information, or it can be a backhaul capacity issue which they don't publicise at all. Did the disconnections affect your profile by any chance?
Not sure whether that incident did or it has just got pushed down gradually.  Last time I looked it was 1750 - it's now down to 1500.  Noise margin is now 15dB after another disconnect a couple of hours ago although I seem to have a higher range of tones.

Download speed achieved during the test was - 1379 Kbps
Your DSL Connection Rate :2048 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 1500 Kbps

Love how the acceptable minimum is 400.  IE they'll only accept it as a fault if it stops working altogether...

Note also the download speed compared to the profile.  It's about as good as it gets and, is probably the reason why despite the profile going down, it doesn't 'feel' much slower that when I was on Demon with a profile of 2500.


Rik

The DLM has clearly done its job on the noise margin, and that's potentially costing you about 2M in sync speed. How often does the router re-sync?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Mar 28, 2010, 10:56:50
The DLM has clearly done its job on the noise margin, and that's potentially costing you about 2M in sync speed. How often does the router re-sync?

It's been stable recently connecting around the 1950/2150 mark.  It's difficult to tell exactly what is happening on my router, but yesterday it had a couple of disconnects following the heavy rain, with another one this morning.  I think it's the ducts that get flooded combined with old cables; the village centre is low lying with a high water table.  Over the summer it will go down and things will improve slightly.  Come the winter and it will all start again, next time pushing it even lower.

At one time all the phones in the village simply failed to work after heavy rain so I guess it's an improvement.


Rik

You'd think BT would fix it if voicelines are affected. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Mar 28, 2010, 11:07:19
You'd think BT would fix it if voicelines are affected. :(

They fixed the voice part a while back, but I imagine it was another patch job rather than complete renewal.  Now you do get some noise on the line following rain, but the phones work which is 'good enough' for BT.


Rik

They really should be forced to work to reasonable standards, Ofcom lets them get away with too much. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

klipp



Speed is better today but the ping is still epic.

Rik

Have you done a direct ping, eg assuming Windows, Start > Run > CMD, then ping www.idnet.net? Are there any background processes operating on your machine, eg P2P?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

klipp

Packets: Sent = 4, Received = 4, Lost = 0
Minimum = 20ms, Maximum = 554ms, Average = 259ms

It seems to have improved (speed wise) over night so I'm hoping the ping will also drop soon.

Rik

Do you have any background processes running? That's a huge difference between minimum and maximum.

By comparison:

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

This post reflects my own views, opinions and experience, not those of IDNet.

Gary

Here are my ping stats for another comparison

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.768 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=31.734 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=30.997 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=31.737 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=31.400 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=31.673 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=31.695 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=30.612 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=31.421 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=36.654 ms

--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 30.612/31.969/36.654/1.602 ms
Damned, if you do damned if you don't

trophymick

I usually get 6.5 meg, but today it's a bit dire. :bawl:
Is it something to do with the clocks being messed with? :dunno:

Mick

Rik

No, Mick.

Can you tell me your downstream sync speed, noise margin and attenuation and, preferably, run a BT speetest.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

klipp

Nothing else running, Rik.  TBH I'm not really that worried now that my general speed is back up to 3.3mb (that's my regular speed).

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

trophymick

Is this what you need Rik?


BT Test:

Download speedachieved during the test was - 83 Kbps
For your connection, the acceptable range of speeds is 50-250 Kbps.
Additional Information:
Your DSL Connection Rate :1024 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 135 Kbps


Ping test:


Pinging idnet.com [212.69.36.10] with 32 bytes of da

Reply from 212.69.36.10: bytes=32 time=74ms TTL=59
Reply from 212.69.36.10: bytes=32 time=48ms TTL=59
Reply from 212.69.36.10: bytes=32 time=48ms TTL=59
Reply from 212.69.36.10: bytes=32 time=49ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 74ms, Average = 54ms

Mick

Steve

If you can manage the downstream noise margin as well it would be very helpful. It looks like you've had multiple disconnections on the broadband side. Have you been through the checklist for sources of internal noise-faulty filters,sky boxes,bell wires and faulty router. The BT quiet line test is useful if noise is on the voice side as well. A detuned AM radio scanned around the path of the incoming phone line is useful for detecting noise coming from other electrical appliances.

Have you tried the router into the BT test socket and do the router connection stats improve. If you've exhausted all possibilities for internal noise I suggest contact support tomorrow.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

What Steve says, Mick. You've had a low speed sync event, <287k, which has hit the profile. It will take up to five days to recover, providing you can maintain this current connection.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.