Re: Long delays experienced at times with Internet... - Page 2

pippincp · ‎03-10-2013

@ironman123 wrote:
NewtronStar,
I think that 1492 is the MTU used for PPPoE,as that is the max MTU used by that protacol.
1500 is use for cable connections like VM use.
I agree that 1500 is the MTU setting that most internet protacols use,but PPPoE is 1492.

You are correct ironman.

rik_rs · ‎03-10-2013

Same problem here in wn5!

Everything it's OK: speed, latency, no packet loss, but as Anpnw complains, yesterday and today, especially Google takes a long time to respond. If you try Yahoo there is no problem.

It looks like a DNS problem but it isn't.

I've changed some DNS (from a list of personally tested DNS cached/uncached and the problem remains). Some websites are OK, some other are painful.

To be sure is not the DNS, I've tried Google via IP and the problem is still there.

The problem has nothing to do with the ADSL line nor DNS nor PC problems. There is some node of the internet with a problem and depending on the zone the user is affected or not.

See you,

Riccardo

pippincp · ‎03-10-2013

If there is a problem with a node (router) then a pathping may reveal it.

This is only availabele on Windows M/C's

Try a pathping to bbc.co.uk, give it time to finish (about 6 mins) and post the full result.

anpnw · ‎03-10-2013

Not had the time to try anything else but problem is awkward as there does not seem to be a particular pattern to guarantee showing the issue. Tried other browsers with the same response. I was believing it to be a PC issue (but now not so sure) and as yet have not been able to try on my laptops - but will tonight.

In the meantime I have run pathping command for both bbc.co.uk and for google.co.uk:

Tracing route to www.bbc.net.uk [212.58.244.66]

over a maximum of 30 hops:

0 Home.home [192.168.1.64]

1 BTHUB3 [192.168.1.254]

2 217.32.142.3

3 217.32.142.46

4 213.120.163.6

5 31.55.165.219

6 31.55.165.109

7 acc2-10GigE-1-2-0.mr.21cn-ipp.bt.net [109.159.250.198]

8 * * *

Computing statistics for 175 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 Home.home [192.168.1.64]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% BThomehub.home [192.168.1.254]

0/ 100 = 0% |

2 6ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.3

0/ 100 = 0% |

3 8ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.46

0/ 100 = 0% |

4 6ms 0/ 100 = 0% 0/ 100 = 0% 213.120.163.6

0/ 100 = 0% |

5 6ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.219

0/ 100 = 0% |

6 6ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109

100/ 100 =100% |

7 --- 100/ 100 =100% 0/ 100 = 0% acc2-10GigE-1-2-0.mr.21cn-ipp.bt.n

et [109.159.250.198]

Trace complete.

Tracing route to www.google.co.uk [173.194.126.159]

over a maximum of 30 hops:

0 Home.home [192.168.1.64]

1 BTHUB3 [192.168.1.254]

2 217.32.142.3

3 217.32.142.46

4 213.120.163.6

5 31.55.165.219

6 31.55.165.109

7 core2-gig7-0-0.manchester.ukcore.bt.net [109.159.250.218]

8 core2-te0-0-0-16.ealing.ukcore.bt.net [109.159.250.156]

9 peer1-xe3-2-1.telehouse.ukcore.bt.net [109.159.254.209]

10 195.99.126.111

11 209.85.252.186

12 209.85.253.94

13 72.14.235.91

14 * * *

Computing statistics for 325 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 Home.home [192.168.1.64]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% BTHUB3 [192.168.1.254]

0/ 100 = 0% |

2 5ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.3

0/ 100 = 0% |

3 10ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.46

0/ 100 = 0% |

4 6ms 0/ 100 = 0% 0/ 100 = 0% 213.120.163.6

0/ 100 = 0% |

5 6ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.219

0/ 100 = 0% |

6 6ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109

0/ 100 = 0% |

7 --- 100/ 100 =100% 100/ 100 =100% core2-gig7-0-0.manchester.ukcore.b

t.net [109.159.250.218]

0/ 100 = 0% |

8 --- 100/ 100 =100% 100/ 100 =100% core2-te0-0-0-16.ealing.ukcore.bt.

net [109.159.250.156]

0/ 100 = 0% |

9 --- 100/ 100 =100% 100/ 100 =100% peer1-xe3-2-1.telehouse.ukcore.bt.

net [109.159.254.209]

0/ 100 = 0% |

10 --- 100/ 100 =100% 100/ 100 =100% 195.99.126.111

0/ 100 = 0% |

11 18ms 0/ 100 = 0% 0/ 100 = 0% 209.85.252.186

100/ 100 =100% |

12 --- 100/ 100 =100% 0/ 100 = 0% 209.85.253.94

0/ 100 = 0% |

13 --- 100/ 100 =100% 0/ 100 = 0% 72.14.235.91

Trace complete.

hodgeda1 · ‎03-10-2013

Hi, I have the same problem. I can confirm it's nothing to do with your PC, there are currently various ongoing issues that are causing pages not to fully load/time out.

See the broadband status pages for more details https://www.bt.com/consumerFaultTracking/public/faults/tracking.do?pageId=31

Best regards

Dave

pippincp · ‎03-10-2013

The 2 pathpings you have posted would appear to show a problem with the Google servers.

hodgeda1 · ‎03-10-2013

I have the same problem and I've narrowed it down to BT by confirming every thing works when going via my neighbours virgin media connection. The BT problem started yesterday (wednesday around 2pm in the afternoon). I called and got confirmation that the fault in my case is due to a major issue in the manchester area, other area's are also impacted.

Using BT infinity - based in Manchester - notice the timeouts.

Tracing route to

www.google.co.uk [173.194.66.94]

over a maximum of 30 hops:

1 4 ms 3 ms 2 ms BThomehub.home [192.168.1.254]

2 16 ms 16 ms 16 ms 217.32.142.0

3 17 ms 15 ms 15 ms 217.32.142.46

4 15 ms 15 ms 16 ms 212.140.206.150

5 19 ms 15 ms 15 ms 31.55.165.191

6 * * * Request timed out.

7 * * * Request timed out.

8 25 ms 24 ms 24 ms core1-te0-13-0-16.ilford.ukcore.bt.net [109.159.250.166]

9 23 ms 25 ms 23 ms peer1-xe3-1-0.telehouse.ukcore.bt.net [109.159.254.213]

10 28 ms 24 ms 25 ms 195.99.125.23

11 * * * Request timed out.

12 25 ms 25 ms 23 ms 209.85.253.94

13 43 ms 29 ms 29 ms 72.14.242.166

14 36 ms 29 ms 28 ms 216.239.49.45

15 * * * Request timed out.

16 29 ms 29 ms 29 ms we-in-f94.1e100.net [173.194.66.94]

Using virgin media - based in manchester. Notice no timeouts.

Tracing route to

www.google.co.uk [173.194.41.151]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1

2 4 ms 2 ms 2 ms 192.168.2.1

3 5 ms 2 ms 2 ms 192.168.2.2

4 17 ms 9 ms 11 ms manc-core-2b-ae3-788.network.virginmedia.net [213.104.83.165]

5 10 ms 10 ms 14 ms manc-bb-1c-ae18-0.network.virginmedia.net [82.15.206.249]

6 10 ms 13 ms 17 ms leed-bb-1b-et-000-0.network.virginmedia.net [62.253.175.18]

8 19 ms 22 ms 17 ms 233-14-250-212.static.virginmedia.com [212.250.14.233]

8 19 ms 22 ms 17 ms 233-14-250-213.static.virginmedia.com [212.250.14.236]

9 20 ms 17 ms 18 ms 209.85.255.78

10 18 ms 15 ms 27 ms 72.14.238.55

11 26 ms 20 ms 15 ms lhr08s03-in-f23.1e100.net [173.194.41.151]

hodgeda1 · ‎03-10-2013

Ping to same IP address (the one resolved using virgin media) but using BT - timeouts again.

Tracing route to lhr08s03-in-f23.1e100.net [173.194.41.151]

over a maximum of 30 hops:

1 4 ms 2 ms 2 ms BThomehub.home [192.168.1.254]

2 17 ms 15 ms 15 ms 217.32.142.0

3 16 ms 48 ms 55 ms 217.32.142.46

4 17 ms 16 ms 15 ms 213.120.163.86

5 17 ms 16 ms 16 ms 31.55.165.191

6 * * * Request timed out.

7 16 ms 19 ms 16 ms acc2-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.228]

8 27 ms 23 ms 23 ms 109.159.250.150

9 22 ms 22 ms 24 ms peer1-xe9-0-0.telehouse.ukcore.bt.net [109.159.254.120]

10 26 ms 78 ms 28 ms 195.99.126.105

11 * * * Request timed out.

12 * * * Request timed out.

13 24 ms 24 ms 23 ms lhr08s03-in-f23.1e100.net [173.194.41.151]

anpnw · ‎03-10-2013

Thanks for the information. I cannot see any status issues relating to Warrington as yet! But interesting that clicking on your link to google (173.194.66.94 and 173.194.41.151) I get the following message

An Unexpected Error has occurred.

Sorry, your request failed. A notification has been sent to the development team for investigation.

Exception ID: 52E82F70

I assume that this relates to your particular area

My IP address for google.co.uk 173.194.126.159 at the moment clicking on it is instant load. I have now reverted DNS settings to original (as this did not seem to help) and will try a little more experimentation on the PC and laptops.

EDIT: Ran pathping again with these results but once again had to wait 20+ seconds after clicking on this post to edit!

Tracing route to www.google.co.uk [173.194.41.95]
over a maximum of 30 hops:
0 Home.home [192.168.1.64]
1 BThomehub.home [192.168.1.254]
2 217.32.142.3
3 217.32.142.30
4 213.120.163.14
5 31.55.165.219
6 31.55.165.109
7     *        *        *
Computing statistics for 150 seconds...
            Source to Here   This Node/Link
Hop RTT    Lost/Sent = Pct Lost/Sent = Pct Address
0                                           Home.home [192.168.1.64]
                                0/ 100 = 0%   |
1    0ms     0/ 100 = 0%     0/ 100 = 0% BThomehub.home [192.168.1.254]
                                0/ 100 = 0%   |
2    5ms     0/ 100 = 0%     0/ 100 = 0% 217.32.142.3
                                0/ 100 = 0%   |
3    7ms     0/ 100 = 0%     0/ 100 = 0% 217.32.142.30
                                0/ 100 = 0%   |
4    6ms     0/ 100 = 0%     0/ 100 = 0% 213.120.163.14
                                0/ 100 = 0%   |
5    6ms     0/ 100 = 0%     0/ 100 = 0% 31.55.165.219
                                0/ 100 = 0%   |
6    6ms     0/ 100 = 0%     0/ 100 = 0% 31.55.165.109

Trace complete.

anpnw · ‎04-10-2013

Just a quick update - hope I am not speaking too soon but for the moment connection appears to be fine.

Checked a few things last night using both PC and a couple of laptops (TBH I did not expect any changes using laptop but just trying to rule out pos. PC issues).

MTU = 1500

Same result on laptops with page loading taking up to 30 seconds or showing timeout - when clicked again same url loaded quickly. The seemingly random nature of this most frustrating trying to troubleshoot.

Anyway this evening all web pages seem to load as they should within a couple of seconds and even nested searches using Google perform without fault - not the case prior. Have not tried any other testing as it would seem to be redundant at this time.

So as nothing has changed with my system I must assume that this was a BT issue, maybe relating to the outage in Manchester areas? I hope I am correct with this assumption and that all shoud run smoothly

Many thanks to all that have offered opinion and advice, your input much appreciated

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.

Re: Long delays experienced at times with Internet connection.