# Traffic from Cloudflare's Seattle PoP enters Fly at NRT for an app in LAX **URL:** \ **Category:** Questions / Help\ **Created:** [October 18, 2026, 7:02pm UTC](https://community.fly.io/t/traffic-from-cloudflares-seattle-pop-enters-fly-at-nrt-for-an-app-in-lax/28859 "2026-10-18T19:02:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![trivgar](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/trivgar/32/51009_2.png) [@trivgar](https://community.fly.io/u/trivgar)\ **Post date:** [October 18, 2026, 7:02pm UTC](https://community.fly.io/t/traffic-from-cloudflares-seattle-pop-enters-fly-at-nrt-for-an-app-in-lax/28859/1 "2026-10-18T19:02:23Z")
Hi Fly team, Our API runs on one machine in lax and sits behind Cloudflare (proxied, with the certificate issued by Fly). Every request Cloudflare forwards from its Seattle PoP (cf-ray suffix SEA) enters Fly at the NRT edge: the fly-request-id suffix was -nrt on every request we sampled on 2026-10-18 between 17:10 and 18:45 UTC. The endpoint we timed answers in about 1 ms on the machine itself, and takes 220 to 285 ms through that path. A Seattle to Los Angeles trip should be closer to 30 to 40 ms. Some fly-request-id values from that window: - 01M58026H0S6CXB0RS1XMBEBXZ-nrt - - 01M581ER42Z0WKVR8BH10VC0G1-nrt - - 01M5802H2NHW2YBD583DY16G1C-nrt The app has a dedicated anycast IPv4 and a dedicated IPv6. Separately, from a home connection in Tacoma (AS14677), every Fly anycast address we tried, ours and shared ones like [debug.fly.dev](http://debug.fly.dev), lands on ORD rather than SEA. Is the SEA to NRT path something you can look at on your side? Happy to share the app name and addresses privately. Thanks! ---
**Author:** ![lillian](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lillian/32/49616_2.png) [@lillian](https://community.fly.io/u/lillian)\ **Post date:** [October 18, 2026, 7:36pm UTC](https://community.fly.io/t/traffic-from-cloudflares-seattle-pop-enters-fly-at-nrt-for-an-app-in-lax/28859/2 "2026-10-18T19:36:53Z")
This is an issue with Cloudflare. We have contacted them but have not yet received a response. If you are able, please contact them as well and ask for their NOC to reach out to us at [ops@fly.io](mailto:ops@fly.io).