# Weird traceroute through Fly.io reverse NGINX proxy --- really slow... **URL:** \ **Category:** Questions / Help\ **Created:** [April 24, 2021, 2:52pm UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255 "2021-04-24T14:52:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mike1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mike1/32/421_2.png) [@mike1](https://community.fly.io/u/mike1)\ **Post date:** [April 24, 2021, 2:52pm UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/1 "2021-04-24T14:52:00Z")
Hey All, Looking for some help troubleshooting an issue with Fly. One of my client sites is using [Fly.io](http://Fly.io) as a reverse proxy to offer whitelabel domains for a Heroku app. This week I began seeing 500ms slower request speeds through the reverse proxy than directly through the Heroku site. I knew there would be some latency when using a reverse proxy, but I was thinking the latency would be much less. I’ve checked the stats on the Fly app, the Heroku app, everything and it all looks fine. The only thing that looks out of place is the `traceroute`. Here is an example site if you want to check out the traceroute: https://it.justtakesonecall.com/ Here are two traceoutes. The first goes directly to the Heroku app. The second goes through the [Fly.io](http://Fly.io) proxy. The latter takes over a minute to complete. ![Screen Shot 2021-04-24 at 9.38.10 AM](https://global.discourse-cdn.com/fly1/original/3X/e/0/e0989e6ebb42e85238c8d41572a01abaa5579836.png) ![Screen Shot 2021-04-24 at 9.37.52 AM](https://global.discourse-cdn.com/fly1/original/3X/0/3/0318715aeb7889579543e8be95f380ad8b22d73e.png) ---
**Author:** ![mike1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mike1/32/421_2.png) [@mike1](https://community.fly.io/u/mike1)\ **Post date:** [April 24, 2021, 3:45pm UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/2 "2021-04-24T15:45:06Z")
Hey everyone, I’ll delete this post. I did some additional digging and I realized that I also had DNSimple fronting the [Fly.io](http://Fly.io) proxy. I removed DNS simple and things got much faster! Sorry for the false alarm ---
**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\ **Post date:** [April 24, 2021, 4:13pm UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/3 "2021-04-24T16:13:06Z")
Oh good, I’m glad it was simple and not tough to track down. 🙂 Traceroutes are pretty finicky, if you run into issues with speed the first place to check is [https://debug.fly.dev](https://debug.fly.dev). That’ll show you which region you’re hitting, and you can use it as a baseline for latency tests too. ---
**Author:** ![mike1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mike1/32/421_2.png) [@mike1](https://community.fly.io/u/mike1)\ **Post date:** [April 25, 2021, 1:54am UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/4 "2021-04-25T01:54:27Z")
@kurt Thanks for the quick response on this on a Saturday! So… I didn’t actually fix the issue the issue this morning. Cutting out DNSimple as a CNAME front helped, but didn’t resolve the massive latency I have been seeing. BUT I have more clues on what is happening and would love your thoughts. My Heroku logs are showing these three forwarded ip addresses (excluding my own ip address) `2a09:8280:1:a5df:525:9645:7cb1:93a1` =\> Fly `2a00:dd80:20:2b:0:c499:8cf3:1` =\> NetActuate, Frankfurt Germany `162.158.89.15` =\> Cloudflare Here’s a screenshot of my [debug.fly.dev](http://debug.fly.dev) ![Screen Shot 2021-04-24 at 8.50.14 PM](https://global.discourse-cdn.com/fly1/original/3X/9/4/9448ef4baeda59c6e8cbbc61d540879c70e0d85a.png) `debug.fly.dev` It looks like all of my traffic on Fly is going through Germany. Since I’m coming from Chicago that would explain my 500ms latency on requests. ![Screen Shot 2021-04-24 at 8.44.24 PM](https://global.discourse-cdn.com/fly1/original/3X/d/d/dd487ab0024ea215a9411198c2bee867523f4a80.png) Do you have any ideas on what might be causing my traffic to go to Germany? ---
**Author:** ![jerome](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jerome/32/17_2.png) [@jerome](https://community.fly.io/u/jerome)\ **Post date:** [April 25, 2021, 1:00pm UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/5 "2021-04-25T13:00:58Z")
Outbound data transfer shows bandwidh metrics for where the instance is located. I looked up your app is and it’s only deployed in our Frankfurt region. That’s why all requests are routed there eventually. Looks like your regions are set to AMS,CDG and FRA. You probably need to add more regions and more instances if you want to cover more geos. Or you can change your regions entirely if you’d rather your app only ran close to you. ---
**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\ **Post date:** [April 25, 2021, 3:17pm UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/6 "2021-04-25T15:17:05Z")
To add to this: if you’re running on Heroku in the US, you should run the app in our `iad` region at first, then expand to more from there. If you’re in Heroku’s EU region, you should run it in `lhr`. The lag you’re seeing is packets traveling from you to Frankfurt and then to Heroku, vs just going direct to Heroku. ---
**Author:** ![mike1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mike1/32/421_2.png) [@mike1](https://community.fly.io/u/mike1)\ **Post date:** [April 26, 2021, 1:38am UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/7 "2021-04-26T01:38:03Z")
Great! Thank you for the fast followup. ---
**Author:** ![mike1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mike1/32/421_2.png) [@mike1](https://community.fly.io/u/mike1)\ **Post date:** [April 26, 2021, 1:53am UTC](https://community.fly.io/t/weird-traceroute-through-fly-io-reverse-nginx-proxy-really-slow/1255/8 "2021-04-26T01:53:28Z")
Yep. That did it. Should have checked the region earlier, I just thought where the app was spun up was all automatic, but this totally makes sense. Thank you again for the prompt response.