Timeout on rapidgator.net?

[#1]

Hello all,
I am getting a persistent timeout when trying to log in to my rapidgator account at: https://rapidgator.net/auth/login
The rest of the site works fine, but I cannot log in and access my account, it times out in Firefox/Chrome/Safari, yet works fine on my 3g internet and is shown as not being blocked here: https://www.blocked.org.uk/results?url=https://rapidgator.net/auth/login
When I ping the homepage I get:

Ping has started…
PING www.rapidgator.net (195.211.221.116): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
--- www.rapidgator.net ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss

And when I try to ping the log in url I get:

Ping has started…
ping: cannot resolve https://rapidgator.net/auth/login: Unknown host

Any ideas please? Should I post the Traceroute for the homepage?

[#2]

IP 195.211.221.116 Doesn't appear to replay to icmp requests (ping) tracert may shine some light  my tracert gets to mp2-gw1-po28.msk.anders.ru , i ain't on plusnet BTW

[#3]

Quote from: deathtrap

IP 195.211.221.116 Doesn't appear to replay to icmp requests (ping) tracert may shine some light  my tracert gets to mp2-gw1-po28.msk.anders.ru , i ain't on plusnet BTW

Thanks for the reply!
Here is the traceroute for www.rapidgator.net

Traceroute has started…
traceroute to www.rapidgator.net (195.211.221.116), 64 hops max, 72 byte packets
 1  home.gateway.home.gateway (192.168.1.254)  3.447 ms  1.216 ms  1.913 ms
 2  lo0-central10.pcl-ag03.plus.net (195.166.128.184)  13.613 ms  15.824 ms  15.322 ms
 3  link-b-central10.pcl-gw02.plus.net (212.159.2.170)  14.196 ms  17.032 ms  14.745 ms
 4  xe-10-2-0.pcl-cr02.plus.net (212.159.0.202)  14.794 ms  23.996 ms  14.588 ms
 5  195.99.126.98 (195.99.126.98)  14.948 ms  16.066 ms  16.229 ms
 6  core3-te0-19-0-20.faraday.ukcore.bt.net (109.159.249.157)  16.111 ms  17.673 ms  14.055 ms
 7  213.121.193.26 (213.121.193.26)  17.095 ms  18.579 ms  15.568 ms
 8  transit2-xe1-3-0.ealing.ukcore.bt.net (213.121.193.230)  16.433 ms  14.603 ms  16.376 ms
 9  * 213.137.183.102 (213.137.183.102)  16.775 ms  15.180 ms
10  t2c4-xe-11-0-0-0.uk-lof.eu.bt.net (166.49.208.96)  33.042 ms  32.200 ms  31.853 ms
11  * * *
12  * * *
13  anders-gw.transtelecom.net (217.150.63.245)  91.113 ms  73.780 ms  77.037 ms
14  mp2-gw1-po28.msk.anders.ru (81.91.177.201)  74.719 ms  73.651 ms  77.328 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *

[#4]

# traceroute -q 1 -N 1 -T -p 443 rapidgator.net
traceroute to rapidgator.net (195.211.221.116), 30 hops max, 52 byte packets
 1  gateway (192.168.0.1)  1.256 ms
 2  lo0.10.Central10.ptw-bng02.plus.net (195.166.130.203)  21.995 ms
 3  irb.10.PTW-CR01.plus.net (84.93.249.1)  25.574 ms
 4  195.99.126.182 (195.99.126.182)  23.978 ms
 5  core4-hu0-3-0-0.faraday.ukcore.bt.net (213.121.193.164)  24.378 ms
 6  core1-Te0-0-0-0.ealing.ukcore.bt.net (213.121.193.20)  25.405 ms
 7  transit2-xe1-3-0.ealing.ukcore.bt.net (213.121.193.230)  24.120 ms
 8  213.137.183.96 (213.137.183.96)  23.165 ms
 9  t2c4-xe-0-0-1-0.de-fra.eu.bt.net (166.49.208.34)  41.570 ms
10  *
11  *
12  Anders-gw.transtelecom.net (217.150.63.245)  82.060 ms
13  mp2-gw1-po28.msk.anders.ru (81.91.177.201)  83.929 ms
14  195.211.221.116 (195.211.221.116)  81.594 ms

# traceroute -q 1 -N 1 -T -p 80 rapidgator.net
traceroute to rapidgator.net (195.211.221.116), 30 hops max, 52 byte packets
 1  gateway (192.168.0.1)  1.284 ms
 2  lo0.10.Central10.ptw-bng02.plus.net (195.166.130.203)  22.005 ms
 3  irb.10.PTW-CR01.plus.net (84.93.249.1)  22.210 ms
 4  195.99.126.138 (195.99.126.138)  22.710 ms
 5  core3-hu0-3-0-0.faraday.ukcore.bt.net (213.121.193.160)  22.504 ms
 6  core2-te0-0-0-13.ealing.ukcore.bt.net (213.121.193.62)  25.280 ms
 7  195.211.221.116 (195.211.221.116)  23.403 ms

A traceroute using TCP port 80 (http) looks suspiciously short, shorter than the traceroute using TCP port 443 (https). I can view the main rapidgator page and the login page, I don't have an account so can't test actually logging in. The unusually short traceroute suggests there's some sort of filtering web proxy involved.
What you could try, is log into your router, click a disconnect button for the PPP / WAN / Internet connection, and then after a few seconds click connect. You'll probably re-connect to a different Plusnet gateway, and then you might be able to access the website.

[#5]

Quote from: ejs

A traceroute using TCP port 80 (http) looks suspiciously short, shorter than the traceroute using TCP port 443 (https). I can view the main rapidgator page and the login page, I don't have an account so can't test actually logging in. The unusually short traceroute suggests there's some sort of filtering web proxy involved. What you could try, is log into your router, click a disconnect button for the PPP / WAN / Internet connection, and then after a few seconds click connect. You'll probably re-connect to a different Plusnet gateway, and then you might be able to access the website.

Thanks - I clicked disconnect here:

The IPv4 Address has now changed and the DNS addresses have swapped round. Did I do that properly?
The homepage still works, but the log in page still won't load, with Firefox telling me "The server at rapidgator.net is taking too long to respond."

[#6]

Well from my non plusnet /BT filtered connection the tracert is the same  when using tcp and port 443 as it is when using port 80 and ICMP and it resolves to the same IP , and there isn't any problem loading the log in page

[#7]

Ok, not sure I am knowledgeable enough to understand that, you're saying it works fine for you, and since our traceroute is the same it should be working fine for me? Any ideas on anything else I can try?
[Moderator's note by Mike (Mav):  Full quote of preceding post removed, as per Forum Rule]