Increased latency of domain when I turn on "proxied" in Proxy Status in my DNS sett

I am running my production app api on this domain “prod.example.app”. I have noticed delays of roughly 100 to 200 ms when I enable Proxy Status to “Proxied”. I have verified this multiple ways.

I have even added cache rules/page rules to avoid all caching and it does show cache status as “DYNAMIC” which means it being bypassed but then why is the responses slow in general then ?

It just works fine of static content. Example: when I hit https://prod.example.app/folders/staticfile.jpg it just works fine and returns me the file in like < 200ms but then when I hit some GET API’s on the same domain like: https://prod.example.app/api/v1/news the response time increases to 300-400 which generally without the proxy status - “proxied” is like always < 250ms

Is this normal for CF to do this ?
I need to have “proxied” on since I want to hide the actual Cname record of my amazon load balancer

Hi @subs4

Since Cloudflare acts as a reverse proxy, we might affect the TTFB for a site. There are a few HTTP requests that add up to the total TTFB:

  1. Cloudflare successfully negotiating a connection with your origin.
  2. Cloudflare sending a request on the connection.
  3. The origin generating a response.
  4. Cloudflare receiving the response.

Essentially, you may see a larger TTFB because we don’t send data back until after we have connected to your web server and it has responded.
The difference is usually no more than a few milliseconds, but more details on Cloudflare and TTFB can be found here:
Are you measuring what matters? A fresh look at Time To First Byte

You can use Cloudflare Observatory to run tests and check the real user monitoring (RUM) data.
This page can help you understand the results of the tests.

If you’re seeing the TTFB is unusually high on dynamic resources (CF-Cache-Status is not HIT, see Cloudflare cache responses):

  1. Follow the customize the cache guide to make sure that any resource that can be cached appropriately is cached. You can review the Cache Analytics on the Cloudflare Dashboard to check for cache performance and potential improvements.
  2. Make sure your origin web server is performing well: you might need to check with your website administrator or hosting provider.

If you’re seeing a high TTFB on cached resources (CF-Cache-Status is HIT) or on resources hosted on Cloudflare (through Workers or Pages for example), please share the following information with us so we can further investigate:

  • The output from running the following command:
curl -svo /dev/null -w "Connect: %{time_connect} \n TTFB: %{time_starttransfer} \n Total time: %{time_total} \n" https://<HOSTNAME>
  • The output of the following webpage in a browser: http://kivano.kg/cdn-cgi/trace

  • A HAR file demonstrating the issue from your browser

  • An MTR or traceroute to <HOSTNAME> from an affected device

  • Any information from any other tools showing the high TTFB value: please provide details on how did you measure or where did you get the information