After enabling Cloudflare’s proxy service, we noticed a significant increase in request latency—from the original 20ms to over 500ms. Upon investigation, our team found that the DNS resolves to an IP located in the United States. Additionally, using cdn-cgi/trace, we confirmed that the LAX (Los Angeles) node is being used. Both our users and our origin server are located in Asia (Taiwan), leading us to suspect that this high latency is caused by requests traveling back and forth between Taiwan and the US multiple times. According to Cloudflare’s documentation, there are CDN nodes globally, including in Taiwan. Could you please advise on how we can ensure that users are routed to the local CDN node in Taiwan? Are there specific settings we need to modify, or is there a particular paid plan that would resolve this issue?
Can you provide us with the domain name? Due to the way routing in the country works, some requests are sent to data center locations (colo) that are not necessarily the closest geographically. For example, if we do not have a peering relationship with your network provider or if that cache location is under heavier load, we may manually route our self-service plans to other datacenters.
Most of the requests are sent to the physically closest cache location, but some requests are sent to nearby ones that are under a lower capacity. If you would like your zone to always be served by the closest geographic colo and the highest priority of traffic, please consider upgrading to the enterprise plan by filling out an Enterprise Request Form.