cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Aspiring Contributor
522 Views
Message 11 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

Still having massive problems, internet has been unavailable most of this morning, webpages just time out. Google.co.uk takes around 10 seconds to load the page and logo!!

 

I have run a quick ping test to google.co.uk and it shows a lot of timeouts and around 30% packet loss! :-

 

PING google.co.uk (216.58.210.67): 56 data bytes
64 bytes from 216.58.210.67: icmp_seq=0 ttl=52 time=42.338 ms
64 bytes from 216.58.210.67: icmp_seq=1 ttl=52 time=217.243 ms
64 bytes from 216.58.210.67: icmp_seq=2 ttl=52 time=69.913 ms
64 bytes from 216.58.210.67: icmp_seq=3 ttl=52 time=61.644 ms
64 bytes from 216.58.210.67: icmp_seq=4 ttl=52 time=48.962 ms
64 bytes from 216.58.210.67: icmp_seq=5 ttl=52 time=55.834 ms
64 bytes from 216.58.210.67: icmp_seq=6 ttl=52 time=52.227 ms
64 bytes from 216.58.210.67: icmp_seq=7 ttl=52 time=184.507 ms
64 bytes from 216.58.210.67: icmp_seq=8 ttl=52 time=80.134 ms
64 bytes from 216.58.210.67: icmp_seq=9 ttl=52 time=195.405 ms
64 bytes from 216.58.210.67: icmp_seq=10 ttl=52 time=43.520 ms
64 bytes from 216.58.210.67: icmp_seq=11 ttl=52 time=158.093 ms
64 bytes from 216.58.210.67: icmp_seq=12 ttl=52 time=68.954 ms
64 bytes from 216.58.210.67: icmp_seq=13 ttl=52 time=52.801 ms
64 bytes from 216.58.210.67: icmp_seq=14 ttl=52 time=157.563 ms
64 bytes from 216.58.210.67: icmp_seq=15 ttl=52 time=50.713 ms
64 bytes from 216.58.210.67: icmp_seq=16 ttl=52 time=190.257 ms
64 bytes from 216.58.210.67: icmp_seq=17 ttl=52 time=46.936 ms
64 bytes from 216.58.210.67: icmp_seq=18 ttl=52 time=165.949 ms
64 bytes from 216.58.210.67: icmp_seq=19 ttl=52 time=40.755 ms
64 bytes from 216.58.210.67: icmp_seq=20 ttl=52 time=123.062 ms
64 bytes from 216.58.210.67: icmp_seq=21 ttl=52 time=45.367 ms
64 bytes from 216.58.210.67: icmp_seq=22 ttl=52 time=194.179 ms
64 bytes from 216.58.210.67: icmp_seq=23 ttl=52 time=67.463 ms
64 bytes from 216.58.210.67: icmp_seq=24 ttl=52 time=209.658 ms
64 bytes from 216.58.210.67: icmp_seq=25 ttl=52 time=55.176 ms
64 bytes from 216.58.210.67: icmp_seq=26 ttl=52 time=102.869 ms
64 bytes from 216.58.210.67: icmp_seq=27 ttl=52 time=47.568 ms
64 bytes from 216.58.210.67: icmp_seq=28 ttl=52 time=83.570 ms
64 bytes from 216.58.210.67: icmp_seq=29 ttl=52 time=108.742 ms
64 bytes from 216.58.210.67: icmp_seq=30 ttl=52 time=185.255 ms
64 bytes from 216.58.210.67: icmp_seq=31 ttl=52 time=91.964 ms
64 bytes from 216.58.210.67: icmp_seq=32 ttl=52 time=130.355 ms
64 bytes from 216.58.210.67: icmp_seq=33 ttl=52 time=49.927 ms
64 bytes from 216.58.210.67: icmp_seq=34 ttl=52 time=166.602 ms
64 bytes from 216.58.210.67: icmp_seq=35 ttl=52 time=91.761 ms
Request timeout for icmp_seq 36
64 bytes from 216.58.210.67: icmp_seq=37 ttl=52 time=594.681 ms
Request timeout for icmp_seq 38
64 bytes from 216.58.210.67: icmp_seq=39 ttl=52 time=178.878 ms
64 bytes from 216.58.210.67: icmp_seq=40 ttl=52 time=63.465 ms
64 bytes from 216.58.210.67: icmp_seq=41 ttl=52 time=42.091 ms
64 bytes from 216.58.210.67: icmp_seq=42 ttl=52 time=43.738 ms
64 bytes from 216.58.210.67: icmp_seq=43 ttl=52 time=47.738 ms
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
64 bytes from 216.58.210.67: icmp_seq=47 ttl=52 time=47.078 ms
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 48
ping: sendto: No route to host
Request timeout for icmp_seq 49
ping: sendto: No route to host
Request timeout for icmp_seq 50
ping: sendto: No route to host
Request timeout for icmp_seq 51
ping: sendto: No route to host
Request timeout for icmp_seq 52
ping: sendto: No route to host
Request timeout for icmp_seq 53
ping: sendto: No route to host
Request timeout for icmp_seq 54
ping: sendto: No route to host
Request timeout for icmp_seq 55
ping: sendto: No route to host
Request timeout for icmp_seq 56
ping: sendto: No route to host
Request timeout for icmp_seq 57
ping: sendto: No route to host
Request timeout for icmp_seq 58
ping: sendto: No route to host
Request timeout for icmp_seq 59
ping: sendto: No route to host
Request timeout for icmp_seq 60
ping: sendto: No route to host
Request timeout for icmp_seq 61
ping: sendto: No route to host
Request timeout for icmp_seq 62
ping: sendto: No route to host
Request timeout for icmp_seq 63
ping: sendto: No route to host
Request timeout for icmp_seq 64
ping: sendto: No route to host
Request timeout for icmp_seq 65
ping: sendto: No route to host
Request timeout for icmp_seq 66
ping: sendto: No route to host
Request timeout for icmp_seq 67
ping: sendto: No route to host
Request timeout for icmp_seq 68
ping: sendto: No route to host
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
64 bytes from 216.58.210.67: icmp_seq=71 ttl=52 time=44.940 ms
64 bytes from 216.58.210.67: icmp_seq=72 ttl=52 time=48.309 ms
64 bytes from 216.58.210.67: icmp_seq=73 ttl=52 time=40.376 ms
64 bytes from 216.58.210.67: icmp_seq=74 ttl=52 time=56.510 ms
64 bytes from 216.58.210.67: icmp_seq=75 ttl=52 time=39.627 ms
64 bytes from 216.58.210.67: icmp_seq=76 ttl=52 time=41.440 ms
64 bytes from 216.58.210.67: icmp_seq=77 ttl=52 time=141.622 ms
64 bytes from 216.58.210.67: icmp_seq=78 ttl=52 time=757.369 ms
64 bytes from 216.58.210.67: icmp_seq=79 ttl=52 time=467.240 ms
64 bytes from 216.58.210.67: icmp_seq=80 ttl=52 time=786.234 ms
64 bytes from 216.58.210.67: icmp_seq=81 ttl=52 time=119.974 ms
64 bytes from 216.58.210.67: icmp_seq=82 ttl=52 time=429.594 ms
64 bytes from 216.58.210.67: icmp_seq=83 ttl=52 time=143.156 ms
64 bytes from 216.58.210.67: icmp_seq=84 ttl=52 time=335.309 ms
64 bytes from 216.58.210.67: icmp_seq=85 ttl=52 time=66.862 ms
64 bytes from 216.58.210.67: icmp_seq=86 ttl=52 time=44.386 ms
64 bytes from 216.58.210.67: icmp_seq=87 ttl=52 time=42.381 ms
64 bytes from 216.58.210.67: icmp_seq=88 ttl=52 time=123.589 ms
64 bytes from 216.58.210.67: icmp_seq=89 ttl=52 time=60.092 ms
64 bytes from 216.58.210.67: icmp_seq=90 ttl=52 time=54.840 ms
64 bytes from 216.58.210.67: icmp_seq=91 ttl=52 time=221.970 ms
64 bytes from 216.58.210.67: icmp_seq=92 ttl=52 time=139.384 ms
Request timeout for icmp_seq 93
64 bytes from 216.58.210.67: icmp_seq=94 ttl=52 time=128.352 ms
^C
--- google.co.uk ping statistics ---
95 packets transmitted, 66 packets received, 30.5% packet loss
round-trip min/avg/max/stddev = 39.627/137.704/786.234/153.082 ms

0 Ratings
Highlighted
Distinguished Sage
516 Views
Message 12 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

without seeing the results of the further diagnostics test it is hard to help further
0 Ratings
Highlighted
Distinguished Sage
515 Views
Message 13 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

looks like a flash error on the speedtest
0 Ratings
Highlighted
Aspiring Contributor
513 Views
Message 14 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

The error with the speedtest, says "upload error" looking at the poor latency and the packet loss that I have been experiencing, I would think that the speed test actually lost connection with the servers. Flash runs locally apart from data transfer.

Bare in mind that the problem is affecting all internet connectivity, on every server. Which again makes me wonder if this is a physical connectivity/line problem, it is not normal for latency to fluctuate in this manner.

0 Ratings
Highlighted
Community Manager
Community Manager
500 Views
Message 15 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

Hi Unix_Guy,

 

Thanks for the posts and welcome to the forum.  Wow, there is definitely something not right here, 4129.204MS, I don't think i have seen it as high.  I am very sorry about this as no doubt it will be having an awful effect on your connection and your sanity.

 

Best bet would be to get your details off to us.  I would like to run some tests from my end to figure out where the issue lies.  You will find the 'Mods contact link' under the 'About me' section of my profile, just click on my username (SeanD).

 

Cheers

Sean

Highlighted
Aspiring Contributor
477 Views
Message 16 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

Hi Sean,

 

Your right it is getting a bit beyond a joke, and very frustrating!! It has just taken this webpage 20+ seconds to load!! My neighbour has also been complaining about similar problems so maybe the two are related? I have sent a message to the Mods I hope this can be resolved otherwise we might as well cancel and revert to 2.8k dialup..... Hmmmm.... even better I'm sure i've got an old 2400 Baud modem somwhere Smiley Wink Smiley LOL

 

2400baudmodem.jpg

0 Ratings
Highlighted
Aspiring Contributor
450 Views
Message 17 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

Unfortunately I've had no response at all from tech support, and we are still experiencing high >1000ms latency and dropouts :-

PING bbc.co.uk (212.58.244.20): 56 data bytes
64 bytes from 212.58.244.20: icmp_seq=0 ttl=50 time=38.694 ms
64 bytes from 212.58.244.20: icmp_seq=1 ttl=50 time=132.997 ms
64 bytes from 212.58.244.20: icmp_seq=2 ttl=50 time=56.319 ms
64 bytes from 212.58.244.20: icmp_seq=3 ttl=50 time=39.322 ms
64 bytes from 212.58.244.20: icmp_seq=4 ttl=50 time=98.239 ms
64 bytes from 212.58.244.20: icmp_seq=5 ttl=50 time=39.322 ms
64 bytes from 212.58.244.20: icmp_seq=6 ttl=50 time=146.656 ms
64 bytes from 212.58.244.20: icmp_seq=7 ttl=50 time=60.280 ms
64 bytes from 212.58.244.20: icmp_seq=8 ttl=50 time=39.119 ms
64 bytes from 212.58.244.20: icmp_seq=9 ttl=50 time=106.595 ms
64 bytes from 212.58.244.20: icmp_seq=10 ttl=50 time=38.725 ms
64 bytes from 212.58.244.20: icmp_seq=11 ttl=50 time=160.119 ms
64 bytes from 212.58.244.20: icmp_seq=12 ttl=50 time=66.584 ms
64 bytes from 212.58.244.20: icmp_seq=13 ttl=50 time=38.896 ms
64 bytes from 212.58.244.20: icmp_seq=14 ttl=50 time=40.034 ms
64 bytes from 212.58.244.20: icmp_seq=15 ttl=50 time=39.590 ms
64 bytes from 212.58.244.20: icmp_seq=16 ttl=50 time=39.448 ms
64 bytes from 212.58.244.20: icmp_seq=17 ttl=50 time=40.528 ms
64 bytes from 212.58.244.20: icmp_seq=18 ttl=50 time=39.469 ms
64 bytes from 212.58.244.20: icmp_seq=19 ttl=50 time=39.466 ms
64 bytes from 212.58.244.20: icmp_seq=20 ttl=50 time=39.605 ms
64 bytes from 212.58.244.20: icmp_seq=21 ttl=50 time=39.089 ms
64 bytes from 212.58.244.20: icmp_seq=22 ttl=50 time=39.690 ms
64 bytes from 212.58.244.20: icmp_seq=23 ttl=50 time=913.896 ms
Request timeout for icmp_seq 24
64 bytes from 212.58.244.20: icmp_seq=24 ttl=50 time=1067.717 ms
Request timeout for icmp_seq 24
Request timeout for icmp_seq 24
64 bytes from 212.58.244.20: icmp_seq=25 ttl=50 time=1050.245 ms
64 bytes from 212.58.244.20: icmp_seq=26 ttl=50 time=1061.146 ms
64 bytes from 212.58.244.20: icmp_seq=27 ttl=50 time=1047.874 ms
64 bytes from 212.58.244.20: icmp_seq=28 ttl=50 time=1031.961 ms
64 bytes from 212.58.244.20: icmp_seq=29 ttl=50 time=1043.609 ms
64 bytes from 212.58.244.20: icmp_seq=30 ttl=50 time=1056.173 ms
64 bytes from 212.58.244.20: icmp_seq=31 ttl=50 time=1045.805 ms
64 bytes from 212.58.244.20: icmp_seq=32 ttl=50 time=1037.519 ms
64 bytes from 212.58.244.20: icmp_seq=33 ttl=50 time=1050.001 ms
64 bytes from 212.58.244.20: icmp_seq=34 ttl=50 time=48.412 ms
64 bytes from 212.58.244.20: icmp_seq=35 ttl=50 time=39.253 ms
64 bytes from 212.58.244.20: icmp_seq=36 ttl=50 time=38.999 ms
64 bytes from 212.58.244.20: icmp_seq=37 ttl=50 time=38.631 ms
64 bytes from 212.58.244.20: icmp_seq=38 ttl=50 time=39.456 ms
64 bytes from 212.58.244.20: icmp_seq=39 ttl=50 time=39.300 ms
64 bytes from 212.58.244.20: icmp_seq=40 ttl=50 time=39.670 ms

This is becoming very frustrating, I needed to D/L Oracle Enterprise linux for work this morning but have given up until things improve.

Is it ok if we only pay half of our bill as we are only getting half a broadband service? 😉

0 Ratings
Distinguished Sage
445 Views
Message 18 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

the forum mod team will contact you personally by email or phone normally within 3 / 5 working days and provide you with a single UK based point of contact and they take personal ownership of problems until resolved
0 Ratings
Highlighted
Aspiring Contributor
429 Views
Message 19 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

Good morning all, latency and bandwidth seem slower than before! Some lovely high ping results from this morning,

average of 1125.611ms! Wow, impressive stuff.

 

PING bbc.co.uk (212.58.246.103): 56 data bytes

Request timeout for icmp_seq 0

64 bytes from 212.58.246.103: icmp_seq=0 ttl=51 time=1372.278 ms

64 bytes from 212.58.246.103: icmp_seq=1 ttl=51 time=786.292 ms

64 bytes from 212.58.246.103: icmp_seq=2 ttl=51 time=547.133 ms

64 bytes from 212.58.246.103: icmp_seq=3 ttl=51 time=987.554 ms

64 bytes from 212.58.246.103: icmp_seq=4 ttl=51 time=1172.762 ms

64 bytes from 212.58.246.103: icmp_seq=5 ttl=51 time=1424.106 ms

64 bytes from 212.58.246.103: icmp_seq=6 ttl=51 time=1463.793 ms

64 bytes from 212.58.246.103: icmp_seq=7 ttl=51 time=760.159 ms

64 bytes from 212.58.246.103: icmp_seq=8 ttl=51 time=586.181 ms

64 bytes from 212.58.246.103: icmp_seq=9 ttl=51 time=1071.634 ms

64 bytes from 212.58.246.103: icmp_seq=10 ttl=51 time=1147.053 ms

64 bytes from 212.58.246.103: icmp_seq=11 ttl=51 time=1210.393 ms

64 bytes from 212.58.246.103: icmp_seq=12 ttl=51 time=1473.141 ms

64 bytes from 212.58.246.103: icmp_seq=13 ttl=51 time=1337.205 ms

64 bytes from 212.58.246.103: icmp_seq=14 ttl=51 time=1473.345 ms

64 bytes from 212.58.246.103: icmp_seq=15 ttl=51 time=1352.586 ms

64 bytes from 212.58.246.103: icmp_seq=16 ttl=51 time=821.757 ms

64 bytes from 212.58.246.103: icmp_seq=17 ttl=51 time=792.082 ms

Request timeout for icmp_seq 19

64 bytes from 212.58.246.103: icmp_seq=19 ttl=51 time=1440.162 ms

64 bytes from 212.58.246.103: icmp_seq=20 ttl=51 time=1318.190 ms

64 bytes from 212.58.246.103: icmp_seq=21 ttl=51 time=737.928 ms

64 bytes from 212.58.246.103: icmp_seq=22 ttl=51 time=908.504 ms

64 bytes from 212.58.246.103: icmp_seq=23 ttl=51 time=1432.588 ms

64 bytes from 212.58.246.103: icmp_seq=24 ttl=51 time=1699.118 ms

64 bytes from 212.58.246.103: icmp_seq=25 ttl=51 time=1684.350 ms

64 bytes from 212.58.246.103: icmp_seq=26 ttl=51 time=1557.269 ms

64 bytes from 212.58.246.103: icmp_seq=27 ttl=51 time=1328.117 ms

64 bytes from 212.58.246.103: icmp_seq=28 ttl=51 time=1503.032 ms

64 bytes from 212.58.246.103: icmp_seq=29 ttl=51 time=1367.063 ms

64 bytes from 212.58.246.103: icmp_seq=30 ttl=51 time=1055.311 ms

64 bytes from 212.58.246.103: icmp_seq=31 ttl=51 time=1195.895 ms

64 bytes from 212.58.246.103: icmp_seq=32 ttl=51 time=1759.237 ms

64 bytes from 212.58.246.103: icmp_seq=33 ttl=51 time=1337.740 ms

64 bytes from 212.58.246.103: icmp_seq=34 ttl=51 time=1313.715 ms

64 bytes from 212.58.246.103: icmp_seq=35 ttl=51 time=645.645 ms

64 bytes from 212.58.246.103: icmp_seq=36 ttl=51 time=307.734 ms

64 bytes from 212.58.246.103: icmp_seq=37 ttl=51 time=651.611 ms

64 bytes from 212.58.246.103: icmp_seq=38 ttl=51 time=1115.298 ms

64 bytes from 212.58.246.103: icmp_seq=39 ttl=51 time=975.817 ms

64 bytes from 212.58.246.103: icmp_seq=40 ttl=51 time=363.101 ms

64 bytes from 212.58.246.103: icmp_seq=41 ttl=51 time=673.158 ms

^C

--- bbc.co.uk ping statistics ---

43 packets transmitted, 41 packets received, 4.7% packet loss

round-trip min/avg/max/stddev = 307.734/1125.611/1759.237/370.672 ms

0 Ratings
Highlighted
Distinguished Sage
424 Views
Message 20 of 26

Re: Extremely high ping times (> 3000ms) and unusable speeds (< 0.5 Mbps) with BT Broadband. L

all you can do is wait for the mods to contact you
0 Ratings