cancel
Showing results for 
Search instead for 
Did you mean: 
themightyninja
Aspiring Contributor
231 Views
Message 1 of 2

Intermittent issues - HomeHub5 - Ping timeouts

Hi,

 

for a long time I've experienced an unreliable connection. When working the connection is fast (around 50mb/s) but when there's issues it's terrible. I've called BT support and they sent a BT engineer who tested the line and found it to be very good. He tested it extensively so I'm confident the line to the property is good.

 

When experience poor browsing (on all devices in the house... wired and wireless) a ping test confirms timeouts...

 

64 bytes from 216.58.210.35: icmp_seq=668 ttl=51 time=16.792 ms

64 bytes from 216.58.210.35: icmp_seq=669 ttl=51 time=753.675 ms

64 bytes from 216.58.210.35: icmp_seq=670 ttl=51 time=14.526 ms

64 bytes from 216.58.210.35: icmp_seq=671 ttl=51 time=15.353 ms

<snipped>

64 bytes from 216.58.210.35: icmp_seq=678 ttl=51 time=68.198 ms

64 bytes from 216.58.210.35: icmp_seq=679 ttl=51 time=18.199 ms

64 bytes from 216.58.210.35: icmp_seq=680 ttl=51 time=197.508 ms

64 bytes from 216.58.210.35: icmp_seq=681 ttl=51 time=14.883 ms

Request timeout for icmp_seq 683

64 bytes from 216.58.210.35: icmp_seq=684 ttl=51 time=14.141 ms

64 bytes from 216.58.210.35: icmp_seq=685 ttl=51 time=13.878 ms

64 bytes from 216.58.210.35: icmp_seq=686 ttl=51 time=13.923 ms

Request timeout for icmp_seq 687

64 bytes from 216.58.210.35: icmp_seq=688 ttl=51 time=22.678 ms

64 bytes from 216.58.210.35: icmp_seq=689 ttl=51 time=32.006 ms

Request timeout for icmp_seq 690

Request timeout for icmp_seq 691

Request timeout for icmp_seq 692

Request timeout for icmp_seq 693

64 bytes from 216.58.210.35: icmp_seq=690 ttl=51 time=4074.204 ms

Request timeout for icmp_seq 695

Request timeout for icmp_seq 696

<snipped>

Request timeout for icmp_seq 717

ping: sendto: No route to host

Request timeout for icmp_seq 718

<snipped>

Request timeout for icmp_seq 736

ping: sendto: No route to host

Request timeout for icmp_seq 737

Request timeout for icmp_seq 738

Request timeout for icmp_seq 739

Request timeout for icmp_seq 740

64 bytes from 216.58.210.35: icmp_seq=741 ttl=51 time=14.727 ms

Request timeout for icmp_seq 742

64 bytes from 216.58.210.35: icmp_seq=742 ttl=51 time=1837.320 ms

64 bytes from 216.58.210.35: icmp_seq=744 ttl=51 time=13.427 ms

64 bytes from 216.58.210.35: icmp_seq=745 ttl=51 time=16.301 ms

64 bytes from 216.58.210.35: icmp_seq=746 ttl=51 time=14.165 ms

Request timeout for icmp_seq 747

64 bytes from 216.58.210.35: icmp_seq=747 ttl=51 time=1007.145 ms

64 bytes from 216.58.210.35: icmp_seq=749 ttl=51 time=16.657 ms

64 bytes from 216.58.210.35: icmp_seq=750 ttl=51 time=14.702 ms

64 bytes from 216.58.210.35: icmp_seq=751 ttl=51 time=14.721 ms

^C

--- www.google.co.uk ping statistics ---

752 packets transmitted, 683 packets received, 9.2% packet loss

round-trip min/avg/max/stddev = 12.526/78.335/4074.204/294.699 ms

 

Powering my homehub off and on seems to fix the issue for a while. The issue often occurs every few minutes and typically lasts for a couple of minutes.

 

BT support have already got me to reset back to factory defaults. I've got a homehub5 and most of the equipment has been checked by the engineer. The equipment I think there's still doubt around in the hub.

 

BTW I'm not using 5Ghz and the issue persists with a wired connection so that really rules out issues with the wireless functionality.

 

Any ideas would be most welcome as I'm about to go with another ISP as the issue is driving everyone to distraction!

 

Thanks,

 

John

0 Ratings
Reply
1 REPLY 1
Moderator
Moderator
195 Views
Message 2 of 2

Re: Intermittent issues - HomeHub5 - Ping timeouts

Hi John,

 

I'll be able to take a look at your connection. Please can you send me in your details using the "Contact The Mods" link found in my profile.

 

Thanks

 

PaddyB

0 Ratings
Reply