cancel
Showing results for 
Search instead for 
Did you mean: 
dell12
Newbie
339 Views
Message 1 of 5

Possible routing issues

Go to solution

Fior the past few days I have been having issues with some web pages loading slowly or not at all on my Infinity 2 connection.

 

I am connected on CAT6 direct to the Hub 5

Some are fine, others not.

The fiirst 2 hops after the Hub look to be the issue.

 

I have tried restarting and getting a new ip etc, but the issue remains the same.

 

www.pdc.tv

 

ping www.pdc.tv

Pinging a1095.g2.akamai.net [217.32.28.176] with 32 bytes of data:
Reply from 217.32.28.176: bytes=32 time=15ms TTL=56
Reply from 217.32.28.176: bytes=32 time=11ms TTL=56
Reply from 217.32.28.176: bytes=32 time=13ms TTL=56
Reply from 217.32.28.176: bytes=32 time=12ms TTL=56

Ping statistics for 217.32.28.176:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 15ms, Average = 12ms

 

Tracing route to a1095.g2.akamai.net [217.32.28.232]
over a maximum of 30 hops:

  1    25 ms     2 ms     2 ms  BThomehub.home [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    10 ms     8 ms     8 ms  217.41.217.125
  5    12 ms    13 ms    12 ms  212.140.235.194
  6    12 ms    13 ms    13 ms  213.120.180.165
  7    14 ms    13 ms    12 ms  213.120.179.81
  8    12 ms    13 ms    12 ms  31.55.163.73
  9    13 ms    12 ms    12 ms  217.32.28.232

www.autotrader.co.uk


ping www.autotrader.co.uk

Pinging uk.cache.tradermedia.net [193.243.130.87] with 32 bytes of data:
Reply from 193.243.130.87: bytes=32 time=49ms TTL=237
Reply from 193.243.130.87: bytes=32 time=25ms TTL=237
Reply from 193.243.130.87: bytes=32 time=26ms TTL=237
Reply from 193.243.130.87: bytes=32 time=26ms TTL=237

Ping statistics for 193.243.130.87:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 49ms, Average = 31ms

tracert www.autotrader.co.uk

Tracing route to uk.cache.tradermedia.net [193.243.130.87]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  BThomehub.home [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     9 ms     8 ms     8 ms  217.41.217.125
  5    12 ms    11 ms    11 ms  212.140.235.122
  6    13 ms    12 ms    13 ms  213.120.180.165
  7    13 ms    13 ms    14 ms  213.120.179.81
  8    11 ms    13 ms    11 ms  acc1-10GigE-2-1-3.sf.21cn-ipp.bt.net [109.159.25
5.163]
  9    19 ms    23 ms    24 ms  core1-te-0-0-0-17.ilford.ukcore.bt.net [109.159.
251.189]
 10    19 ms    18 ms    17 ms  peer6-te0-9-0-12.telehouse.ukcore.bt.net [109.15
9.254.165]
 11    18 ms    19 ms    20 ms  166-49-211-236.eu.bt.net [166.49.211.236]
 12    20 ms    21 ms    19 ms  166-49-211-254.eu.bt.net [166.49.211.254]
 13    25 ms    25 ms    27 ms  ae9-xcr1.lsh.cw.net [195.2.25.169]
 14    28 ms    29 ms    40 ms  ae18-xcr1.bkl.cw.net [195.2.24.145]
 15    28 ms    29 ms    28 ms  ae0-xcr1.mry.cw.net [195.2.30.137]
 16    25 ms    25 ms    26 ms  ae0-ucr1.mcr.cw.net [195.2.28.70]
 17    29 ms    29 ms    29 ms  195.59.241.14
 18    27 ms    29 ms    31 ms  193.243.130.1
 19    26 ms    24 ms    26 ms  193.243.130.87

Trace complete.

 

www.google.co.uk


ping www.google.co.uk

Pinging www.google.co.uk [216.58.210.67] with 32 bytes of data:
Reply from 216.58.210.67: bytes=32 time=40ms TTL=51
Reply from 216.58.210.67: bytes=32 time=18ms TTL=51
Reply from 216.58.210.67: bytes=32 time=25ms TTL=51
Reply from 216.58.210.67: bytes=32 time=20ms TTL=51

Ping statistics for 216.58.210.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 40ms, Average = 25ms

tracert www.google.co.uk

Tracing route to www.google.co.uk [216.58.210.67]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  BThomehub.home [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     9 ms     8 ms     8 ms  217.41.217.125
  5    12 ms    13 ms    13 ms  212.140.235.218
  6    13 ms    13 ms    13 ms  213.120.180.165
  7    13 ms    14 ms    14 ms  213.120.179.81
  8    13 ms    12 ms    11 ms  acc1-xe-5-1-2.sf.21cn-ipp.bt.net [109.159.251.11
5]
  9    23 ms    22 ms    23 ms  core2-te-0-3-0-3.ilford.ukcore.bt.net [109.159.2
51.45]
 10    21 ms    20 ms    20 ms  peer5-te0-9-0-17.telehouse.ukcore.bt.net [62.172
.102.13]
 11    18 ms    18 ms    19 ms  109.159.253.67
 12    19 ms    20 ms    18 ms  209.85.243.43
 13    20 ms    21 ms    21 ms  72.14.238.185
 14    18 ms    19 ms    18 ms  lhr14s24-in-f67.1e100.net [216.58.210.67]

Trace complete

 

0 Ratings
Reply
4 REPLIES 4
Sage
Sage
325 Views
Message 2 of 5

Re: Possible routing issues

Go to solution
No apparent routing issue shown there.
Have you tried Google DN
0 Ratings
Reply
Sage
Sage
324 Views
Message 3 of 5

Re: Possible routing issues

Go to solution
DNS
0 Ratings
Reply
Jonkarra
Expert
279 Views
Message 4 of 5

Re: Possible routing issues

Go to solution
All that indicates is that the devices in question are set not to respond to ICMP. Something thats becoming more and more common.
0 Ratings
Reply
dell12
Newbie
263 Views
Message 5 of 5

Re: Possible routing issues

Go to solution
School boy error by me here chaps.
I tried a different browser and everything was fine.

It was Firefox causing issues, I disabled the health report and crash reporter in the options and the same websites now load fine.

This thread can be closed off as resolved.

Thanks for your help
0 Ratings
Reply