🐛 Cloudflare tunnels inoperative in Russia

### This issue is critical and impacts an entire product across an entire region.

Recently Tunnels became entirely inoprtative in Russia. I have a server there that I use Tunnels to access. I found a very small group of other people with the same issue on Russian censorship circumvention forums; presumably Tunnels are not that popular. This started happening at the beginning of the month, and slowly got worse and worse until it could simply not connect anymore.

**To reproduce**
1. Be in Russia
2. Attempt to use Cloudflare Tunnels normally (following the start tutorial will be enough)
Verified on Windows and Ubuntu 22.04 LTS
This happens on any config, with any tunnel, on any system, to any person.

**Environment and versions**
- OS: Windows, Linux
- Architecture: AMD64
- Version: 2025.4.0
- **Country/ISP region: Russia**

**Logs and errors**
Click here to expand logs

HTTP/2 Logs, Tunnel errors (1033), no further messages:

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF GOOS: linux, GOVersion: go1.22.10, GoArch: amd64

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF Settings: map[no-autoupdate:true p:http2 protocol:http2 token:*****]

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF Generated Connector ID: [snip]

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF Initial protocol http2

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF ICMP proxy will use 192.168.1.5 as source for IPv4

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF ICMP proxy will use [snip] in zone enp4s0 as source for IPv6

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF ICMP proxy will use 192.168.1.5 as source for IPv4

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF ICMP proxy will use [snip] in zone enp4s0 as source for IPv6

апр 25 10:42:11 server cloudflared[792469]: 2025-04-25T05:42:11Z INF Starting metrics server on 127.0.0.1:20241/metrics

~

QUIC Logs, 502s with the Cloudflare plug (although I also experienced timeouts and 1033s, it is inconsistent, presumably due to it restarting infinitely). Logs repeating cyclically:

апр 25 10:58:31 server cloudflared[798455]: 2025-04-25T05:58:31Z INF Registered tunnel connection connIndex=1 connection=[snip] event=0 ip=198.41.192.37 location=led01 protocol=quic

апр 25 10:58:32 server cloudflared[798455]: 2025-04-25T05:58:32Z INF Using [CurveID(4588) CurveID(25497) CurveP256] as curve preferences connIndex=2 event=0 ip=198.41.192.77

апр 25 10:58:33 server cloudflared[798455]: 2025-04-25T05:58:33Z INF Using [CurveID(4588) CurveID(25497) CurveP256] as curve preferences connIndex=3 event=0 ip=198.41.200.63

апр 25 10:58:36 server cloudflared[798455]: 2025-04-25T05:58:36Z WRN Failed to serve tunnel connection error="timeout: no recent network activity" connIndex=0 event=0 ip=198.41.200.73

апр 25 10:58:36 server cloudflared[798455]: 2025-04-25T05:58:36Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=0 event=0 ip=198.41.200.73

апр 25 10:58:37 server cloudflared[798455]: 2025-04-25T05:58:37Z ERR Failed to serve tunnel connection error="context canceled" connIndex=2 event=0 ip=198.41.192.77

**Additional context**
Russian ISPs interfere or block with Cloudflare IPs. According to one user, routing `198.41.128.0/17` through a VPN fixes the issue. I haven't tried since I can't configure my hosts like that. Potentially, the Russian government messes with [everything on here](https://www.cloudflare.com/ips-v4/)

Despite all of this, I am able to access the IP (even the exact one that fails in `cloudflared`) and receive a valid, expected error from Cloudflare, so there seems to be something fishy going on here.
```shell
igmn@server:~$ curl -v 198.41.192.37
* Trying 198.41.192.37:80...
* Connected to 198.41.192.37 (198.41.192.37) port 80 (#0)
> GET / HTTP/1.1
> Host: 198.41.192.37
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 403 Forbidden
< Date: Fri, 25 Apr 2025 23:02:32 GMT
< Content-Type: text/plain; charset=UTF-8
< Content-Length: 16
< Connection: close
< X-Frame-Options: SAMEORIGIN
< Referrer-Policy: same-origin
< Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Expires: Thu, 01 Jan 1970 00:00:01 GMT
< Server: cloudflare
< CF-RAY: [SNIP]-LED
<
* Closing connection 0
error code: 1003
igmn@server:~$
```

**Proposed solutions**
Switch IP ranges, some kind of proxying, some kind of censorship bypass tech. Potentially, use port 80 since that doesn't seem to be blocked?