Cant reach my site from subnet 91.230.25.0/24

My website URL is:
andriiyakovyshyn.com

What I’m seeing is:
This site can’t be reached

andriiyakovyshyn.com took too long to respond.

Try:

ERR_CONNECTION_TIMED_OUT

I’m using this software:

Google Chrome

Google Chrome is up to date

Version 75.0.3770.80 (Official Build) (64-bit)

Additional information:

Hi and welcome to the forum

TEST (click me)

But sometimes I get error: nginx 502 bad gateway

https://infinityfree.net/support/why-doesnt-my-domain-work/

I can’t reach it only when i use my internet provider http://kvant.if.ua/ . Same issue have my friends who use the same internet provider. In other cases my site works fine. How to fix it?

Please run this command tracert andriiyakovyshyn.com
In PowerShell or CMD and then copy the result and paste it here

Just to note, we normally don’t block any IP addresses or IP ranges from accessing websites on our servers. However, I have seen in the past that certain internet providers or network administrators block access to us.

So if you haven’t done so yet, you should also ask this question to your internet provider. Without more information, there is no way to tell who is blocking who, and it’s virtually impossible to fully determine that from our end.

I’ve already asked my internet provider. They said that hosting is blocking access from subnet 91.230.25.0/24 . Interesting situation.

Can domain registrar block something?

C:\Windows\system32>tracert andriiyakovyshyn.com

Tracing route to andriiyakovyshyn.com [185.27.134.141]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms my.router [192.168.1.1]
2 1 ms 1 ms 2 ms 172.30.12.1
3 3 ms 2 ms 1 ms inferno.kvant.if.ua [91.230.25.1]
4 * * * Request timed out.
5 15 ms 16 ms 14 ms 213.133.177.105
6 43 ms 47 ms 41 ms ae1-114.franco71.fra.seabone.net [89.221.34.12]
7 42 ms 42 ms 42 ms racc.franco52.fra.seabone.net [195.22.211.207]
8 40 ms 40 ms 39 ms ae-5.r04.frnkge08.de.bb.gin.ntt.net [129.250.66.17]
9 40 ms 41 ms 42 ms ae-24.r24.frnkge08.de.bb.gin.ntt.net [129.250.3.217]
10 53 ms 53 ms 55 ms ae-5.r24.londen12.uk.bb.gin.ntt.net [129.250.3.12]
11 72 ms 56 ms 62 ms ae-1.r04.londen05.uk.bb.gin.ntt.net [129.250.4.141]
12 58 ms 57 ms 57 ms 213.130.47.90
13 63 ms 64 ms 62 ms 31.22.6.21
14 66 ms 66 ms 65 ms cust.te3-1.cr-4.rel.ncl.wildcard.net.uk [31.22.6.126]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Thank you for that information. The tracert shows that you can connect to our servers, which at least tells us that our IP address has not been blocked on your end.

Hi, in my experience.
you may change your DNS address of your computer. just ask your friend what DNS on use.

1 Like

I had iFastNet look at the issue again, and they said that your IP range was blocked because of a large number of failed WordPress login attempts. In order to protect the websites hosted with us, the IP range was blocked to prevent attackers from breaking into a site.

I’m not sure if you were responsible for this suspicious activity or someone else on your network was. But note that any kind of hacking activity on or against our systems is strictly forbidden.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.