中国移动网络访问api和dash

api.cloudflare.com and dash.cloudflare.com 通过中国移动网络访问超时。

你备案了没有?

@xnephila 你也在成都吗?

在成都、四川省其他城市以及重庆的中国移动和电信用户都遇到过大多数Cloudflare的网站有DNS解析问题,且长达大约7个月。

cloudflare.com, api.cloudflare.com, dash.cloudflare.com 等其他 *cloudflare.com 网站已经收到了127.0.0.1的相应,但是Cloudflare却无法有效解决这个问题。

这个问题原本可以通过与权威机构、运营商进行沟通,在几天内得到解决方案,但是Cloudflare的员工们似乎并不知道该怎么处理。

是的,就是成都移动

没错,基本上都是超时。ipv6 访问没有任何问题,DNS 解析到的地址都是正确的,但是一直超时

你有什么Cloudflare IPv4? 104.x在中国的许多地方有网络超时。

@MoreHelp

1 Like

workers在重庆电信超时😂

1 Like

How about :search:? Cloudflare would never redirect to the localhost IP

https://community.cloudflare.com/search?expanded=true&q=127.%20order:latest

Where did you quote that from? it doesn’t make sense.

Nobody said that Cloudflare is redirecting 127.0.0.1

The search results you’ve linked are not relevant to this issue.

Sorry, relying on the translator here, it sounded like pages are resolving to the 127 address, is that not the case?

Not really, the IP can be resolved 104.* .
But the connection always timeout.

Some of Cloudflare domains are getting a 127.0.0.1 DNS response, sometimes 0.0.0.0, and sometimes an ISP reserved IP. The issue emitting itself at DNS level.

There is another issue here, assuming you get an actual Cloudflare IP, the connection is extremely slow and timeout.

1 Like

It’s possible to solve the issue per domain by switching off :orange: and setting other Cloudflare IP manually. For example 104.x is affected by horrible performance and connection issues so instead you would set another Cloudflare IP on your domain.

Although individuals can fix for their own domains, ultimately Cloudflare need to attent to the main issue.

Can anyone share a trace from an affected machine? And, is there a ticket with Support that I can reference?

I have mentioned it in this ticket back in January, but the ticket was originally opened for another issue but related. Ticket number 2343985

1 Like

Thank you, I see there is active conversation on that ticket and related internal tickets. I’ll keep an eye on them as the team continues to investigate that issue. You may want to update 2343985 with any additional details you have or if there has. been any change in behaviour.

There hasn’t been any response on the ticket since March. I’ve been asking for an update on the matter but no response.

Please unmark this thread as solved. It’s not solved.

1 Like