cancel
Showing results for 
Search instead for 
Did you mean: 
Distinguished Sage
Distinguished Sage
280 Views
Message 41 of 57

Re: Random very long ping times for random lengths of time

You could try running Routerstats, as that will give you a better idea when the problem is.

 

http://www.vwlowen.co.uk/RouterStatsHub/Support/Getting%20Started.htm

ksaro1
Contributor
274 Views
Message 42 of 57

Re: Random very long ping times for random lengths of time

quick post.. street lights in village just came on [BTW there are Xmas lights attached to most light poles] here's the latest BT Hub status

 

BT Home Hub  Line Status with street lights just on.png

0 Ratings
Reply
Highlighted
ksaro1
Contributor
271 Views
Message 43 of 57

Re: Random very long ping times for random lengths of time

@Keith_Beddoe - thanks for the URL! That is a well handy app.

 

I've begun running the router status app monitoring. I'll leave it running over the evening and we can see what is logged. So far no SNR or error spikes.

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
268 Views
Message 44 of 57

Re: Random very long ping times for random lengths of time

Yes it is very useful, saves manual checking.

 

There have been versions for most routers, I occasionally use the version for the HH1, which has Telnet access, and can extract lots of ADSL data including bitloading.

 

0 Ratings
Reply
ksaro1
Contributor
244 Views
Message 45 of 57

Re: Random very long ping times for random lengths of time

@Keith_Beddoe @SuperSajuuk : OK my PC was set to go to sleep after 15 minutes inactivity... Sigh...this stopped the logging of router stats. I set the PC not to sleep and set it logging again... After 2-3 hours this evening it showed very little changes on the line. Then the app stopped running? I've restarted it and will leave it running over night.

 

This isn't unusual. I can have days of good connection speed. Then it will go bad for several hours. Then good ...etc.

 

So I'll just keep the logging running and hopefully I will capture data during a period of poor connection speed.

 

I have a neighbour who shares the same pole that contains our phone lines and he is a BT Broadband customer too. Oddly he never gets >3Mb speed. I can see if he can run the router status app on one of his PC's too. His line will connect to the same exchange by the same path as mine of course. He's having similar issues too but is not at all tecvh savvy, so he just pays for a very poor service and assumes that's the best he can get. At least my speeds are fine when it is working.

0 Ratings
Reply
ksaro1
Contributor
230 Views
Message 46 of 57

Re: Random very long ping times for random lengths of time

While downloadig updates to our iPad I noticed sluggish performance on our connection. I ran a traceroute which produced the following ping response times [my copy buffer is limited so I didn't get all of the ping stats, which showed up to 1500ms response times]

 


Sat Dec 12 13:57:18 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.481 ms 2.213 ms 2.199 ms
2 217.47.186.250 (217.47.186.250) 593.685 ms 612.426 ms 613.572 ms
3 217.47.187.145 (217.47.187.145) 613.498 ms 149.364 ms 87.146 ms
4 213.1.69.162 (213.1.69.162) 52.777 ms * 597.648 ms
Sat Dec 12 13:57:27 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.155 ms 2.317 ms 2.218 ms
2 217.47.186.250 (217.47.186.250) 842.163 ms 611.079 ms 613.773 ms
3 217.47.187.145 (217.47.187.145) 612.998 ms 612.599 ms 613.587 ms
4 213.1.69.162 (213.1.69.162) 614.476 ms 612.035 ms 614.631 ms
Sat Dec 12 13:57:32 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.640 ms 4.072 ms 2.230 ms
2 217.47.186.250 (217.47.186.250) 576.702 ms 610.355 ms 616.170 ms
3 217.47.187.145 (217.47.187.145) 610.873 ms 613.960 ms 611.995 ms
4 213.1.69.162 (213.1.69.162) 613.971 ms 612.096 ms 613.993 ms
Sat Dec 12 13:57:38 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.903 ms 3.024 ms 2.112 ms
2 217.47.186.250 (217.47.186.250) 589.842 ms 611.368 ms 922.686 ms
3 217.47.187.145 (217.47.187.145) 919.413 ms 920.277 ms 920.666 ms
4 * 213.1.69.162 (213.1.69.162) 218.496 ms *
Sat Dec 12 13:57:53 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 8.557 ms 2.266 ms 2.185 ms
2 217.47.186.250 (217.47.186.250) 482.368 ms 612.408 ms 614.091 ms
3 217.47.187.145 (217.47.187.145) 613.231 ms 612.304 ms 613.857 ms
4 213.1.69.162 (213.1.69.162) 614.689 ms 52.570 ms *
Sat Dec 12 13:58:02 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.498 ms 2.149 ms 4.902 ms
2 217.47.186.250 (217.47.186.250) 12.042 ms 11.590 ms 11.801 ms
3 217.47.187.145 (217.47.187.145) 12.000 ms 11.826 ms 11.056 ms
4 213.1.69.162 (213.1.69.162) 20.473 ms * 20.097 ms
Sat Dec 12 13:58:08 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.126 ms 2.171 ms 2.190 ms
2 217.47.186.250 (217.47.186.250) 12.746 ms 11.019 ms 12.938 ms
3 217.47.187.145 (217.47.187.145) 11.967 ms 10.770 ms 10.493 ms
4 * 213.1.69.162 (213.1.69.162) 28.054 ms *
Sat Dec 12 13:58:18 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 11.514 ms 1.961 ms 3.898 ms
2 217.47.186.250 (217.47.186.250) 13.411 ms 11.185 ms 13.032 ms
3 217.47.187.145 (217.47.187.145) 10.585 ms 13.698 ms 10.757 ms
4 213.1.69.162 (213.1.69.162) 20.449 ms

 

The routere status of my HH3 are shown below:

RSHub-HEC Errors-20151212-140233.jpgRSHub-NoiseMargin-20151212-140232.jpgRSHub-CRC Errors-20151212-140233.jpg

 

The above seems to show no change in my line in terms of CRC/HEC errors nor noise. So, why the sudden long ping times again? BTW the 'blips' in the error graphs occured well before the download was begun.

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
225 Views
Message 47 of 57

Re: Random very long ping times for random lengths of time

The problem is, connecting using a wireless connection is not a reliable way to measure timings.

0 Ratings
Reply
ksaro1
Contributor
222 Views
Message 48 of 57

Re: Random very long ping times for random lengths of time

I am now doing an upload and the below ping times are more in line with what I would expect.

 


Sat Dec 12 14:43:30 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.300 ms 2.620 ms 2.197 ms
2 217.47.186.250 (217.47.186.250) 70.392 ms 79.761 ms 68.740 ms
3 217.47.187.145 (217.47.187.145) 47.601 ms 78.424 ms 50.087 ms
4 213.1.69.162 (213.1.69.162) 78.484 ms * 94.125 ms
Sat Dec 12 14:43:36 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.224 ms 2.092 ms 2.089 ms
2 217.47.186.250 (217.47.186.250) 73.442 ms 59.198 ms 69.216 ms
3 217.47.187.145 (217.47.187.145) 59.443 ms 68.212 ms 70.704 ms
4 * 213.1.69.162 (213.1.69.162) 91.638 ms *
Sat Dec 12 14:43:47 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 9.487 ms 2.059 ms 2.098 ms
2 217.47.186.250 (217.47.186.250) 80.113 ms 65.998 ms 77.828 ms
3 217.47.187.145 (217.47.187.145) 420.975 ms 77.547 ms 60.069 ms
4 213.1.69.162 (213.1.69.162) 87.580 ms * 72.011 ms
Sat Dec 12 14:43:53 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.350 ms 2.071 ms 2.279 ms
2 217.47.186.250 (217.47.186.250) 44.394 ms 66.611 ms 66.529 ms
3 217.47.187.145 (217.47.187.145) 71.803 ms 66.880 ms 60.308 ms
4 * 213.1.69.162 (213.1.69.162) 94.632 ms *
Sat Dec 12 14:44:03 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 9.811 ms 2.423 ms 2.294 ms
2 217.47.186.250 (217.47.186.250) 74.265 ms 68.074 ms 69.703 ms
3 217.47.187.145 (217.47.187.145) 68.762 ms 75.588 ms 73.529 ms
4 213.1.69.162 (213.1.69.162) 79.093 ms * 62.685 ms
Sat Dec 12 14:44:09 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 1.982 ms 2.038 ms 2.039 ms
2 217.47.186.250 (217.47.186.250) 51.690 ms 73.242 ms 121.914 ms
3 217.47.187.145 (217.47.187.145) 58.187 ms 65.161 ms 66.676 ms
4 213.1.69.162 (213.1.69.162) 67.553 ms * 82.187 ms
Sat Dec 12 14:44:14 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.223 ms 2.152 ms 2.142 ms
2 217.47.186.250 (217.47.186.250) 73.934 ms 66.607 ms 69.102 ms
3 217.47.187.145 (217.47.187.145) 64.212 ms 66.711 ms 67.101 ms
4 213.1.69.162 (213.1.69.162) 106.349 ms * 58.824 ms
Sat Dec 12 14:44:20 GMT 2015
traceroute to 213.1.69.162 (213.1.69.162), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 2.500 ms 2.059 ms 2.253 ms
2 217.47.186.250 (217.47.186.250) 57.901 ms 78.989 ms 70.562 ms
3 217.47.187.145 (217.47.187.145) 59.313 ms 65.313 ms 69.294 ms

 

@Keith_Beddoe I found that the pings I see from my wireless device to external sites are identical to pings directly from the Netgear router to the same sites, which of course rules out any wireless issues. So I think it is reasonable to assume the same when using my wireless device via the HH3 router. Is there any function on the HH3 that allows it to ping sites? Perhaps these ping tests are not ideal, but so far I find that when the internet appears sluggish with slow downloads and pages taking a long time to load in browsers that the ping times inevitably show very long response times.

0 Ratings
Reply
ksaro1
Contributor
212 Views
Message 49 of 57

Re: Random very long ping times for random lengths of time

BTW Performance Test Slow Speed.png

RSHub-CRC Errors-20151212-165156.jpg

RSHub-NoiseMargin-20151212-165156.jpg

RSHub-HEC Errors-20151212-165157.jpg

 

 

Traceroute from LAN attached PC

 

12/12/2015_16:45:44.42

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 423 ms 433 ms 542 ms 217.47.186.250
3 362 ms 386 ms 401 ms 217.47.187.161
4 550 ms 460 ms 546 ms 213.1.69.162

Trace complete.
12/12/2015_16:46:08.80

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 599 ms 616 ms 737 ms 217.47.186.250
3 684 ms 684 ms * 217.47.187.161
4 354 ms 437 ms 360 ms 213.1.69.162

Trace complete.
12/12/2015_16:46:36.52

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 631 ms 656 ms 648 ms 217.47.186.250
3 596 ms 547 ms 558 ms 217.47.187.161
4 1013 ms 994 ms 1121 ms 213.1.69.162

Trace complete.
12/12/2015_16:47:03.25

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 540 ms 756 ms 682 ms 217.47.186.250
3 546 ms 518 ms 538 ms 217.47.187.161
4 553 ms 614 ms * 213.1.69.162
5 521 ms 470 ms 501 ms 213.1.69.162

Trace complete.
12/12/2015_16:47:37.76

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 484 ms 469 ms 481 ms 217.47.186.250
3 433 ms 455 ms 466 ms 217.47.187.161
4 509 ms 550 ms 544 ms 213.1.69.162

Trace complete.
12/12/2015_16:48:02.42

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 472 ms 503 ms 548 ms 217.47.186.250
3 508 ms 510 ms 473 ms 217.47.187.161
4 483 ms 515 ms 537 ms 213.1.69.162

Trace complete.
12/12/2015_16:48:27.15

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 448 ms 476 ms 507 ms 217.47.186.250
3 485 ms 504 ms * 217.47.187.161
4 616 ms 956 ms 705 ms 213.1.69.162

Trace complete.
12/12/2015_16:48:55.56

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 558 ms 602 ms 665 ms 217.47.186.250
3 537 ms 590 ms 636 ms 217.47.187.161
4 609 ms 669 ms * 213.1.69.162
5 591 ms 578 ms 436 ms 213.1.69.162

Trace complete.
12/12/2015_16:49:30.36

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 416 ms 337 ms 360 ms 217.47.186.250
3 464 ms 725 ms 124 ms 217.47.187.161
4 724 ms * 644 ms 213.1.69.162

Trace complete.
12/12/2015_16:49:58.90

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 2 ms 1 ms BThomehub.home [192.168.1.254]
2 304 ms 285 ms 407 ms 217.47.186.250
3 478 ms 477 ms 520 ms 217.47.187.161
4 501 ms 503 ms 490 ms 213.1.69.162

Trace complete.
12/12/2015_16:50:23.21

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 348 ms 363 ms 334 ms 217.47.186.250
3 368 ms 523 ms 542 ms 217.47.187.161
4 392 ms 347 ms 346 ms 213.1.69.162

Trace complete.
12/12/2015_16:50:47.13

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 498 ms 480 ms 419 ms 217.47.186.250
3 411 ms 408 ms 551 ms 217.47.187.161
4 473 ms 469 ms 468 ms 213.1.69.162

Trace complete.
12/12/2015_16:51:11.60

Tracing route to 213.1.69.162 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 635 ms 518 ms 614 ms 217.47.186.250
3 448 ms 430 ms 472 ms 217.47.187.161
4 891 ms 552 ms 594 ms 213.1.69.162

Trace complete.

0 Ratings
Reply
ksaro1
Contributor
201 Views
Message 50 of 57

Re: Random very long ping times for random lengths of time

RSHub-NoiseMargin-20151212-231124.jpg

 

RSHub-CRC Errors-20151212-231125.jpg

RSHub-HEC Errors-20151212-231125.jpg

0 Ratings
Reply