Why Can't I login to ...

[#1]

Been trying to connect to www.valuedopinions.co.uk for over three weeks now, but keep getting 'site not available

Simple DOS Ping from Command line
ping www.valuedopinions.co.uk

Pinging www.valuedopinions.co.uk [63.241.211.24] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 63.241.211.24:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

TraceRT goes through 20 hops then just dies.

Complained to site via email and they insist they are live.

Today tried using my mobile phone (on Giffgaff-o2) as mobile hotspot and CAN connect to www.valuedopinions.co.uk

ping www.valuedopinions.co.uk

Pinging www.valuedopinions.co.uk [63.241.211.24] with 32 bytes of data:
Reply from 63.241.211.24: bytes=32 time=180ms TTL=226
Reply from 63.241.211.24: bytes=32 time=349ms TTL=226
Reply from 63.241.211.24: bytes=32 time=180ms TTL=226
Reply from 63.241.211.24: bytes=32 time=516ms TTL=226

Ping statistics for 63.241.211.24:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 516ms, Average = 306ms

HAve rebooted my router, (hub1) but no change

have tried manual DNS (Google & opendns) as well as the Plusnet provided dns

So why can't I connect to JUST this one site, I could until about 3 weeks ago

[#2]

I've just tried that link for you @dougjbarnes1, and I can get to the main page of a site that offers paid surveys on a Plusnet Fibre account.

[#3]

Thanks Mook

Could you run me a Tracert from DOS so I can see whether we follow the same set of hops. I suspect it's down to the other "146.199.xxx.xxx United States" issue I've had with my Fibre Connection, but why it suddenly happened three weeks ago, and why only this one company is weird

[#4]

I'm on an IP address of 146.200.xxx.xxx which is not a long way away from your IP address. The site times out for me in Firefox. Interestingly, it is blocked (apparently by one of my security/blocking extensions) in Chrome; pausing those extensions also gets the timeout in Chrome.

[#5]

@dougjbarnes1 - I've done the trace route and this is the result, giving up on the 32nd hop.

iMac:~ Mook$ traceroute www.valuedopinions.co.uk
traceroute to www.valuedopinions.co.uk (63.241.211.24), 64 hops max, 52 byte packets
 1  gateway (192.168.0.1)  0.568 ms  0.272 ms  0.220 ms
 2  410.xe-2-2-0.central10.pcn-bng04.plus.net (84.93.253.88)  16.884 ms  16.350 ms  17.084 ms
 3  411.be8.pcn-ir02.plus.net (84.93.253.95)  17.354 ms  17.239 ms
    411.be8.pcn-ir01.plus.net (84.93.253.91)  17.394 ms
 4  core1-be1.colindale.ukcore.bt.net (195.99.125.132)  17.419 ms
    195.99.125.140 (195.99.125.140)  17.479 ms
    core1-be1.colindale.ukcore.bt.net (195.99.125.132)  17.632 ms
 5  peer6-hu0-6-0-2.telehouse.ukcore.bt.net (62.172.103.13)  17.979 ms  17.629 ms  18.676 ms
 6  t2c3-et-7-3-0-0.uk-lon1.eu.bt.net (166.49.211.230)  17.241 ms
    t2c3-et-3-3-0-0.uk-lon1.eu.bt.net (166.49.211.238)  17.737 ms
    213.137.183.34 (213.137.183.34)  17.541 ms
 7  213.248.82.249 (213.248.82.249)  17.924 ms  17.679 ms  17.415 ms
 8  ash-b1-link.telia.net (80.91.248.157)  93.407 ms
    ldn-bb2-link.telia.net (213.155.137.118)  91.124 ms
    ldn-bb2-link.telia.net (62.115.138.154)  94.334 ms
 9  192.205.33.25 (192.205.33.25)  100.560 ms
    ash-bb3-link.telia.net (80.91.246.68)  96.409 ms
    192.205.33.25 (192.205.33.25)  97.340 ms
10  cr81.wshdc.ip.att.net (12.122.135.98)  131.482 ms
    ash-b1-link.telia.net (213.155.136.39)  93.707 ms
    cr81.wshdc.ip.att.net (12.122.135.98)  132.684 ms
11  cr2.wswdc.ip.att.net (12.122.134.94)  130.336 ms
    cr1.wswdc.ip.att.net (12.122.135.86)  138.508 ms  136.370 ms
12  cr2.sl9mo.ip.att.net (12.122.18.29)  130.784 ms
    cr82.wshdc.ip.att.net (12.122.135.102)  136.186 ms
    cr81.wshdc.ip.att.net (12.122.135.98)  131.069 ms
13  cr2.dlstx.ip.att.net (12.122.2.110)  129.205 ms  131.988 ms
    cr2.wswdc.ip.att.net (12.122.134.94)  133.732 ms
14  cr2.sl9mo.ip.att.net (12.122.18.29)  128.129 ms
    ggr1.dlstx.ip.att.net (12.122.138.1)  130.145 ms  129.211 ms
15  cr2.dlstx.ip.att.net (12.122.2.110)  135.844 ms  131.496 ms
    12.122.251.70 (12.122.251.70)  133.184 ms
16  mdf002c7613r0001.dal1.attens.net (63.241.192.238)  181.888 ms
    gbr3.n54ny.ip.att.net (12.122.2.1)  132.111 ms
    mdf002c7613r0001.dal1.attens.net (63.241.192.238)  214.908 ms
17  63.241.198.20 (63.241.198.20)  132.092 ms
    ggr1.dlstx.ip.att.net (12.122.138.1)  127.970 ms
    mdf002c7613r0001.dal1.attens.net (63.241.192.238)  132.400 ms
18  * mdf002c7613r0001.dal1.attens.net (63.241.192.238)  132.146 ms
    mdf002c7613r0002-tge-12-1.dal1.attens.net (63.241.193.26)  133.366 ms
19  * * 63.241.198.20 (63.241.198.20)  134.072 ms
20  * * 63.241.198.20 (63.241.198.20)  132.320 ms
21  * * *
21 to 31 Removed for brevity.
32  * *^C

[#6]

This is what I get by pinging from Win 10 command prompt. Needless to say I can access the web site:

[#7]

>ping valuedopinions.co.uk

Pinging valuedopinions.co.uk [63.241.211.24] with 32 bytes of data:
Reply from 63.241.211.24: bytes=32 time=120ms TTL=233
Reply from 63.241.211.24: bytes=32 time=120ms TTL=233
Reply from 63.241.211.24: bytes=32 time=120ms TTL=233
Reply from 63.241.211.24: bytes=32 time=120ms TTL=233

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

Tracing route to valuedopinions.co.uk [63.241.211.24]
over a maximum of 30 hops:

  1     3 ms    <1 ms    <1 ms  TP-SHARE [192.168.0.1]
  2   231 ms    10 ms     9 ms  410.xe-2-2-0.central10.psb-bng02.plus.net [84.93.253.104]
  3    11 ms    10 ms    13 ms  411.be6.psb-ir02.plus.net [84.93.253.111]
  4    10 ms    10 ms    10 ms  195.99.125.138
  5    11 ms    10 ms    10 ms  195.99.127.68
  6    11 ms    35 ms    10 ms  213.137.183.36
  7    11 ms    12 ms    10 ms  ldn-b3-link.telia.net [213.248.67.97]
  8    84 ms    83 ms    83 ms  ash-b1-link.telia.net [213.155.136.39]
  9    93 ms    91 ms    91 ms  192.205.33.25
 10   123 ms   124 ms   124 ms  cr82.wshdc.ip.att.net [12.122.135.102]
 11   122 ms   127 ms   119 ms  cr2.wswdc.ip.att.net [12.122.134.94]
 12   122 ms   118 ms   119 ms  cr1.attga.ip.att.net [12.122.2.29]
 13   123 ms   119 ms   127 ms  cr2.dlstx.ip.att.net [12.122.2.110]
 14   123 ms   125 ms   123 ms  ggr1.dlstx.ip.att.net [12.122.138.1]
 15   124 ms   125 ms   126 ms  12.122.251.66
 16   126 ms   124 ms   124 ms  mdf1-bi4k-1-eth-4-24.dal1.attens.net [63.241.192.238]
 17   121 ms   121 ms   124 ms  63.241.198.20
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   121 ms   120 ms   122 ms  ftp.e-miles.com [63.241.211.24]

Trace complete.

Seems to be working ok here too. Using Firefox as well here. One thing I have noticed is lately the browsers seem to be blocking more without any 3rd party add ons.. I used to think it was ABP over doing it on some sites e.g. Outlook.com always says I using an Adblocker and yet it is one site I have ABP disabled on.

Only thing I would say is the tracert took quite some time, longer than normal. Website itself loads very quickly.

[#8]

Thanks Chaps for the feedback

I've stuck you results in a table to show the divergent routes used, surprisingly there are also areas of common paths, I would have expected that once a common path point  was reached, ALL would continue on the same succession of hops but apparently NO

Also Mooks results show a couple of repeat router addresses which seems strange.

Also we ALL hit 63.241.198.20 before Valued Opinions Target site, but only IDOONO seems to continue through.

I always thought that international routers only carried the next forward address, but it seems that previous path history also has an influence on where to go next.

Possible Plusnet's (BT's) Techies could shed a little light here

Ive enclose screen capture of the Excel Spreadsheet of the hop maps to maintain the correct columnar structure