Website in proxied mode not reachable in Leipzig/Germany

Ticket number: #2540913

1 Like

it’s not ISP related. we have many customers with A1 and Drei who have problems as well, so not only magenta.

2 Likes

As I am writing this, it seems my traceroute call goes through - seems to be working again?

188.114.96.12 and 188.114.97.12 are still timing out for me.

You are right, I get 188.114.96.7 now which seems to work, funny as I didn’t change anything…

We still have the same problem with these IP addresses

188.114.97.3
188.114.96.3

They are apparently blocked in Austria by the provider Magenta (HOT).

188.114.96.3 and 188.114.97.3 are currently working on Magenta fiber Internet here.

~$ ping -c 4 188.114.96.3
PING 188.114.96.3 (188.114.96.3) 56(84) bytes of data.
64 bytes from 188.114.96.3: icmp_seq=1 ttl=57 time=24.7 ms
64 bytes from 188.114.96.3: icmp_seq=2 ttl=57 time=11.4 ms
64 bytes from 188.114.96.3: icmp_seq=3 ttl=57 time=18.8 ms
64 bytes from 188.114.96.3: icmp_seq=4 ttl=57 time=13.6 ms
--- 188.114.96.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 11.442/17.105/24.651/5.103 ms

~$ ping -c 4 188.114.97.3
PING 188.114.97.3 (188.114.97.3) 56(84) bytes of data.
64 bytes from 188.114.97.3: icmp_seq=1 ttl=57 time=16.7 ms
64 bytes from 188.114.97.3: icmp_seq=2 ttl=57 time=20.0 ms
64 bytes from 188.114.97.3: icmp_seq=3 ttl=57 time=10.6 ms
64 bytes from 188.114.97.3: icmp_seq=4 ttl=57 time=16.8 ms
--- 188.114.97.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 10.553/15.999/19.966/3.409 ms

188.114.96.12 and 188.114.97.12 on the other hand on the same connection are currently working:

~$ ping -c 4 188.114.96.12
PING 188.114.96.12 (188.114.96.12) 56(84) bytes of data.

--- 188.114.96.12 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3002ms

~$ ping -c 4 188.114.97.12
PING 188.114.97.12 (188.114.97.12) 56(84) bytes of data.

--- 188.114.97.12 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3002ms

I find it really hard to believe that this is an ISP problem.
Reason for that is that I had this problem shift to different hosts (see post number 2 & 4)
and people are reporting this issue from different countries, ISPs and AS.
(even if the latter doesn’t need to mean anything)
I even had this problem with 2 different connections from 2 different ISPs myself.

Still unreachable from “Austria->Upper Austria->Wels” Area.

My domain on 188.114.96.12 and 188.114.97.12 also doesn’t work from Graz, Austria (Magenta Cable)
It does work from HoT mobile but not from A1 mobile (both Austrian providers)

This IP is banned by court order in Austria.
See netzsperre.liwest.at

4 Likes

Good to know…
Still Cloudflare should be able to resolve this issue then.

You may have the court order number handy?

Yeah, funny enough there are some (13) domains that have been blocked at the same day as these Cloudflare IPs and a few of these 13 domains use Cloudflare. But they stupidly just blocked one Cloudflare IP these domains resolve to… not something that speaks for, that they understand what they are doing.

Anyway IPs shall never be banned… but anyway just use a VPN and use other DNS by default. Maybe even 1.1.1.1 I think they will not block their own IPs :slight_smile:

You are free to wait :slight_smile: But this problem is not originated at Cloudflare. They may be able to fix it, but just if someone can do something, it does not mean that they have to.

4 Likes

Same here in Portugal, using MEO isp can’t reach website using Cloudflare, just pinged it and is ip is 188.114.96.5

Anyway IPs shall never be banned… but anyway just use a VPN and use other DNS by default. Maybe even 1.1.1.1 I think they will not block their own IPs :slight_smile:

1.1.1.1 returns a IP which is blocked in .at, 8.8.8.8 does not (at the moment): IP connection issue

You are free to wait :slight_smile: But this problem is not originated at Cloudflare. They may be able to fix it, but just if someone can do something, it does not mean that they have to.

But it means CF is unusable in .at (maybe .de and other) because you cannot be sure customers can reach your site via CF (depending which IP you get assigned from whatever DNS).

That might be true, but yet it does not invalidate my argument.

I have read your thread here: IP connection issue but since you did not post your domain I could not verify/confirm that. That probably also is the reason no one really responded there.

Such things (that we can not reproduce because of lack of information) shall be reported as a ticket. This public and free community can just work with what you guys give us.

Other than that I think it already is forwarded to some people within Cloudflare, but I do not have any info if they are working on an ATM and also no info about with what priority that will be threatened. That can also depend on who is responsible for this and what the root-cause is.

1 Like

I searched the official system and I cannot find any court decision on this. So my guess is, the ISP blindly followed a cease and desist without checking if they even are legally obliged to do so.

It looks like the changes were reverted.
netzsperre DOT liwest DOT at doesn’t list the IPs anymore and some pages, which were broken or didn’t load at all yesterday are reachable now.

after some media reported, they reverted the change i think
derstandardDOTAT/story/2000138619757/ueberzogene-netzsperre-sorgt-fuer-probleme-im-oesterreichischen-internet

Another Report in German

1 Like

This is the response I got from Cloudflare Support:

Cloudflare’s engineers are already aware of this issue, and we may issue a fix. The root problem though is that a couple Cloudflare IPs on free/pro plans have been banned by Austrian ISPs. If you upgrade to Business, you will not have this problem, as different plans use different prefixes.

There was an Austrian Court order that ISPs were obligated to obey, and this is an example of blocks implemented by LIWEST: http://netzsperre.liwest.at/
It may be useless to ask your users to contact their ISPs because they are obeying a court order and are legally obligated to follow them.

In the interim, please ask your users to elect representatives that understand how the internet works, and who can pass laws that reflect that.