forums.overclockers.co.uk slow response ?

jpaul · 16 Oct 2016 at 22:11

Has anyone else commented that access to the site has been very slow over past 3 days or so

I had not seen this response from tracert/ping before ?

>tracert forums.overclockers.co.uk

Tracing route to forums.overclockers.co.uk [185.103.4.11]
over a maximum of 30 hops:

4 16 ms 16 ms 16 ms xe-10-3-0.pcl-cr02.plus.net [212.159.0.214]
5 17 ms 17 ms 16 ms 195.99.126.98
6 17 ms 17 ms 17 ms core3-te0-10-0-21.faraday.ukcore.bt.net [109.159.249.141]
7 17 ms 17 ms 17 ms peer1-xe0-0-2.faraday.ukcore.bt.net [213.121.193.185]
8 16 ms 16 ms 17 ms t2c4-et-3-3-0-0.uk-lon1.eu.bt.net [166.49.211.246]
9 17 ms 17 ms 17 ms hu0-1-0-0.ccr22.lon01.atlas.cogentco.com [130.117.14.229]
10 17 ms 24 ms 23 ms 149.11.143.94
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 17 ms 17 ms 18 ms ve933.er11.ldx.as50056.net [31.28.68.47]
15 22 ms 17 ms 22 ms ve933.er8.vta.as50056.net [31.28.68.46]
16 forums.overclockers.co.uk [185.103.4.11] reports: Destination protocol unreachable.

>ping forums.overclockers.co.uk

Pinging forums.overclockers.co.uk [185.103.4.11] with 32 bytes of data:
Reply from 185.103.4.11: Destination port unreachable.
Reply from 185.103.4.11: Destination port unreachable.
Reply from 185.103.4.11: Destination port unreachable.
Reply from 185.103.4.11: Destination port unreachable.

Rroff · 16 Oct 2016 at 22:15

Not noticed much in the way of slow down myself.

asim18 · 16 Oct 2016 at 22:31

Destination unreachable is normal because OcUK's servers are set to ignore ICMP/ping requests.

Code:

C:\Users\Asim>tracert forums.overclockers.co.uk

Tracing route to forums.overclockers.co.uk [185.103.4.11]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    16 ms    16 ms    15 ms  popl-core-2a-xe-323-0.network.virginmedia.net [62.255.65.177]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    17 ms    40 ms    20 ms  brhm-bb-1c-ae0-0.network.virginmedia.net [62.254.42.110]
  7    27 ms    40 ms    38 ms  tcl5-ic-2-ae0-0.network.virginmedia.net [212.250.15.210]
  8    40 ms    34 ms    32 ms  e1-3.er1.thn.as50056.net [195.66.225.217]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    38 ms    33 ms    45 ms  ve161.er2.thn.as50056.net [178.18.119.97]
 14     *        *        *     Request timed out.
 15    31 ms    27 ms    29 ms  ve933.er8.vta.as50056.net [31.28.68.46]
 16  forums.overclockers.co.uk [185.103.4.11]  reports: Destination protocol unreachable.

Trace complete.

I'm not having any issues with speed. There were issues about a year ago but it's been snappy ever since.

Why are so many hops timing out though? It never used to be like this. Just last year having a "request timed out" was very rare, now I'm getting it on pretty much all routes to all websites.

muon · 16 Oct 2016 at 23:06

Try a different DNS server.

https://developers.google.com/speed/public-dns/

jpaul · 16 Oct 2016 at 23:48

Thanks for the idea: I have set dns server to an openDNS server after re-running namebench tool to identify a preferred dns server,
however after doing this, it still seems slow to access OC's versus other sites.

(I am not sure namebench includes OC's in its list of sites to benchmark though

)