Website is not accessible to all the netoworks

I am not able to access our website thevoiceoffashion.com from some networks. It was working fine earlier on same networks. Can some one please tell me what is the reason behind this

Which networks, which error message?

Loads fine here -> http://sitemeer.com/#https://thevoiceoffashion.com

On some networks, the website opens only on mobile devices and not on the laptops. The browser cache has been cleared and other measures taken. But the website shows same error

Following error message is showing on some network -

Please find attached the above error image for your reference.

This error is showing on Mumbai Jio, Delhi Airtel network.

Thank You!

Whats the output of these commands on these machines?

ping thevoiceoffashion.com
nslookup thevoiceoffashion.com
ping www.thevoiceoffashion.com
nslookup www.thevoiceoffashion.com

Hi

Out put of this command -

ping thevoiceoffashion.com
Pinging thevoiceoffashion.com [104.24.121.22] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

nslookup thevoiceoffashion.com
nslookup thevoiceoffashion.com
Server: SNDCD001.in.ril.com
Address: 10.128.16.138

Non-authoritative answer:
Name: thevoiceoffashion.com
Addresses: 2606:4700:30::6818:7916
2606:4700:30::6818:7816
104.24.120.22
104.24.121.22

ping www.thevoiceoffashion.com
Pinging www.thevoiceoffashion.com [104.24.120.22] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

nslookup www.thevoiceoffashion.com
Server: SNDCD001.in.ril.com
Address: 10.128.16.138

Non-authoritative answer:
Name: www.thevoiceoffashion.com
Addresses: 2606:4700:30::6818:7816
2606:4700:30::6818:7916
104.24.121.22
104.24.120.22

Thanks

All right, next in line would be

tracert thevoiceoffashion.com

DNS resolution seems to work, but it seems you cant reach Cloudflare’s servers.

tracert thevoiceoffashion.com

Tracing route to thevoiceoffashion.com [104.24.121.22]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

I somehow cant believe the address is hijacked at the first hop. I guess traceroute in generally wont work, which will make debugging that difficult.

Can you run these commands as well?

ping community.cloudflare.com
tracert community.cloudflare.com
ping sitemeer.com
tracert sitemeer.com
ping bbc.co.uk
tracert bbc.co.uk
ping example.com
tracert example.com

ping community.cloudflare.com

Pinging community.cloudflare.com [104.19.198.151] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

tracert community.cloudflare.com
Tracing route to community.cloudflare.com [104.19.198.151]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.

ping sitemeer.com
Pinging sitemeer.com [104.22.1.130] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

tracert sitemeer.com
Tracing route to sitemeer.com [104.22.1.130]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.

ping bbc.co.uk
Pinging bbc.co.uk [151.101.128.81] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

tracert bbc.co.uk

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.

Yes, ICMP generally does not seem to work on that connection. I am afraid in that case it will be a lot more difficult to debug the issue, but it seems it is specific to that particular ISP. You might want to contact them about the issue. The site itself is reachable.

But seem to be work before 1 week ago.

Your ISP likely has changed something. You can also try to debug the issue with http://www.tcptrace.org/windows.html. It is a local issue.

It does seem to be a general issue with that ISP -> PingTimeout - Can't Connect to Cloudflare network

Some days ago I was facing same problem. I think you are using cloudflare free services. I am from delhi and it was not working while opening from jio and hathway. I just simply deleted my account from cloudflare and problem resolved.

This topic was automatically closed after 14 days. New replies are no longer allowed.