Bug Fixed: 6+ second TTFB on certain assets and paths

Hi, @jmikrut, I’m not seeing this behavior in the logs for this site.

I do see large files (around 9.3 MiB) taking longer than six seconds to download, but that isn’t the same as the 6+ seconds time to first byte issue. Large files rarely stay in a CDN node’s cache and therefore do send at about 1 MiB/second with our service.

Are you seeing a slow time to first byte (TTFB) issue? If so, would you please send us a HAR file capture of this or the x-nf-request-id response header for a slow to respond request?

There more information about this header here:

If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:

  • the complete URL requested
  • the IP address for the system making the request
  • the IP address for the CDN node that responded
  • the day of the request
  • the time of the request
  • the timezone the time is in

With this information we’ll be able to research any high TTFB issues.