Can't connect to my own website through Cloudflare

Hello,
I have a problem since a couple of hours - I can’t connect to my own website because when I do

❯ host -t a emby.red
emby.red has address 104.21.55.110
emby.red has address 172.67.171.28

However…

❯ ping 172.67.171.28
PING 172.67.171.28 (172.67.171.28) 56(84) bytes of data.
^C
--- 172.67.171.28 ping statistics ---
129 packets transmitted, 0 received, 100% packet loss, time 133080ms

I checked other websites and I don’t seem to have a general problem connecting to cloudflare protected sites, everything except mine works fine. Can anyone assist me?

That looks like an ISP issue. Can you do a traceroute?

How about to the 104 address?

If you try a cellphone over the cellular network, does it work?

Both addresses have the same problem, traceroute seems to only confirm the packets are not going very far

❯ traceroute 104.21.55.110
traceroute to 104.21.55.110 (104.21.55.110), 30 hops max, 60 byte packets
 1  DESKTOP-EM1VB27.mshome.net (172.20.112.1)  0.277 ms  0.260 ms  0.232 ms
 2  router.local (192.168.1.1)  0.578 ms  0.478 ms  0.499 ms
 3  net-176-97-24-gw.alfa-system.pl (176.97.24.1)  3.324 ms  1.549 ms  3.453 ms
 4  alfa-do-3s.alfa-system.pl (91.231.70.1)  2.839 ms  2.647 ms  3.509 ms
 5  host-85.14.102.213.static.3s.pl (85.14.102.213)  3.745 ms  3.621 ms  2.535 ms
 6  host-89.25.221.31.static.3s.pl (89.25.221.31)  13.263 ms host-89.25.221.33.static.3s.pl (89.25.221.33)  9.458 ms host-89.25.221.31.static.3s.pl (89.25.221.31)  12.446 ms
 7  fo-0-2-0-0.r01.kat-g.techn.3s.pl (89.25.220.19)  9.163 ms * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Can you try the same traceroute to a different Cloudflare website with a 104 address?

❯ traceroute 104.16.66.85
traceroute to 104.16.66.85 (104.16.66.85), 30 hops max, 60 byte packets
 1  DESKTOP-EM1VB27.mshome.net (172.20.112.1)  0.282 ms  0.262 ms  0.236 ms
 2  router.local (192.168.1.1)  0.652 ms  0.458 ms  0.524 ms
 3  net-176-97-24-gw.alfa-system.pl (176.97.24.1)  2.356 ms  2.354 ms  3.768 ms
 4  alfa-do-3s.alfa-system.pl (91.231.70.1)  3.440 ms  3.387 ms  3.868 ms
 5  host-85.14.102.213.static.3s.pl (85.14.102.213)  6.110 ms  3.980 ms  4.556 ms
 6  host-89.25.221.33.static.3s.pl (89.25.221.33)  10.867 ms host-89.25.221.31.static.3s.pl (89.25.221.31)  13.213 ms host-89.25.221.33.static.3s.pl (89.25.221.33)  10.168 ms
 7  host-89.25.221.26.static.3s.pl (89.25.221.26)  12.923 ms * fo-0-2-0-0.r01.kat-g.techn.3s.pl (89.25.220.19)  8.428 ms
 8  ae-3-9.edge3.warsaw1.level3.net (4.69.167.122)  8.504 ms  11.025 ms  11.057 ms
 9  213.242.112.78 (213.242.112.78)  12.128 ms  15.999 ms  12.041 ms
10  104.16.66.85 (104.16.66.85)  15.557 ms  15.439 ms  16.232 ms

Both make it through alfa-system and 3s, but yours does not make the hop to the level3 network. This isn’t something that Cloudflare can fix. You’ll have to ask your ISP.

Can I request cloudflare to change the servers through which traffic to my website is routed? Would be easier to build my own optic fiber network than get something done through my ISP…

No, because an ISP can just block the next address. This is a common occurrence in some countries. As this isn’t a problem with Cloudflare’s configuration, why should Cloudflare fix it? There’s a possibility that if you upgrade to a higher plan, Cloudflare will move you to a different IP address with better neighbors who are less likely to get that IP address blocked, but that’s not a guarantee. Not until you get to Business and Enterprise plans do they give you much more exclusive IP addresses.

The problem is fixed now, I guess the ISP noticed problems with traffic to cloudflare on their own because I didn’t report anything. Thanks for the help!

It’s possible it was the event below, or maybe just coincidence:

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