Cloudflare IP not accessible from my ISP

This happened a couple weeks ago, and resolved itself after several hours. Now it’s happening again. I’m unable to access my domain’s website through Cloudflare, but I’m able to access my server (using an alt-domain or forcing the IP address of my server modifying /etc/hosts)

No access means packets are completely lost, they don’t reach my server, and possibly Cloudflare.

The problem may be my ISP. However, my ISP is a large one and maybe Cloudflare can check their BGP to see if the problem comes from Cloudflare’s end. I can’t, however, ask for support directly since looks like free accounts don’t have support :slight_smile:

My website resolves to Cloudflare’s IP at 188.114.96.5

Doing a mtr, I can see this (running for a while now…)

 Host                                                                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. AS???    192.168.1.1                                                                  21.7%  4013    0.3   0.3   0.2  42.3   1.4
 2. AS3352   144.red-81-46-38.customer.static.ccgg.telefonica.net                          0.0%  4013    1.9   6.2   0.7 161.2  11.2
 3. AS3352   101.red-81-46-34.customer.static.ccgg.telefonica.net                          0.0%  4013    2.0   2.5   0.8  82.1   4.7
 4. AS3352   137.red-81-46-34.customer.static.ccgg.telefonica.net                          0.0%  4013    4.5   2.6   1.4  42.8   3.2
 5. AS3352   46.red-80-58-81.staticip.rima-tde.net                                         0.0%  4013    5.7   2.9   1.6  88.1   4.1
 6. AS3352   81.red-81-46-0.customer.static.ccgg.telefonica.net                            0.0%  4013    2.3   2.3   1.3  60.3   2.0
 7. (waiting for reply)

Or if I display the IP:

 Host                                                                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. AS???    192.168.1.1                                                                  21.3%  4089    0.4   0.3   0.2  42.3   1.4
 2. AS3352   81.46.38.144                                                                  0.0%  4089    9.7   6.1   0.7 161.2  11.1
 3. AS3352   81.46.34.101                                                                  0.0%  4089    8.7   2.4   0.8  82.1   4.6
 4. AS3352   81.46.34.137                                                                  0.0%  4089    2.6   2.6   1.4  42.8   3.2
 5. AS3352   80.58.81.46                                                                   0.0%  4089    2.8   2.9   1.6  88.1   4.1
 6. AS3352   81.46.0.81                                                                    0.0%  4089    2.6   2.3   1.3  60.3   2.0
 7. (waiting for reply)

Coincidentally, this affects common domains like Font Awesome hosted by Cloudflare. Visiting Cloudflare support page takes ages to load until it times-out when trying to download Font Awesome at use.fontawesome.com, which also resolves to 188.114.96.5

1 Like

This happened to me and a friend of mine too. We both live near the Barcelona area, so some Cloudflare sites resolved to 188.114.96.5 and 188.114.97.5 (including mine).

For whatever reason, Telefonica’s 50.red-81-46-0.customer.static.ccgg.telefonica.net (81.46.0.50) couldn’t route to it.

This has since been fixed, but as a successfull traceroute shows now, it is Telefonica’s fault, as that node isn’t Telefonica’s uplink to the internet or Cloudflare, it is an internal hop.
Pathetic.

This is not Cloudflare’s fault, but it’d be great if you guys could snap their wrists so that this doesn’t happen. They didn’t even fix it for hours yesterday. One would expect an ISP to monitor for unroutable packets.

1 Like

Yep, it has been now fixed. Just for the record, here’s the mtr now:

 Host                                                                                                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. AS???    192.168.1.1                                                                                                     2.4%  3835    0.3   0.3   0.2  24.2   0.8
 2. AS3352   81.46.38.144                                                                                                    0.0%  3834    1.9   6.5   0.7 139.7  11.2
 3. AS3352   81.46.34.101                                                                                                    0.0%  3834    1.9   2.4   0.7  56.8   4.7
 4. AS3352   81.46.34.137                                                                                                    0.0%  3834    2.5   2.5   1.3  66.2   3.4
 5. AS3352   80.58.81.46                                                                                                     0.0%  3834    2.5   3.0   1.6  90.7   4.3
 6. AS3352   81.46.0.81                                                                                                      0.0%  3834    2.7   2.4   1.3  76.0   3.9
 7. AS12956  216.184.113.228                                                                                                 0.0%  3834   11.0  10.4   9.5  53.6   1.5
 8. AS12956  176.52.248.251                                                                                                  0.0%  3834   10.9  12.4   9.6  96.5   5.7
 9. AS12956  81.173.106.39                                                                                                   0.0%  3834   11.2  14.3  10.1  49.4   6.5
10. AS13335  172.70.58.2                                                                                                     0.0%  3834   10.9  12.7   9.4 108.1   8.1
11. AS13335  188.114.96.5                                                                                                    0.0%  3834   10.7  10.5   9.6  42.2   1.3

It would be good if Cloudflare would offer a tool like https://bgp.he.net/ to allow traceroutes or pings between Cloudflare’s AS or edge servers to other IP’s, and help diagnose where pachets are droping.

Thanks @ricardbejarano for confirming you’re experiencing the same problem. too!

While a moderator restores my previous reply, I’d like to ask if enabling Argo would temporarily fix this problem, since most Cloudflare protected websites worked when the issue happened. I wonder if enabling Argo would force the change in the IP address that uses Cloudflare for those websites (188.114.96.5 / 188.114.97.5) to other more “efficient routes”, or would it have no effect at all?

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