Timing information about the response.

Fastly writes this header into responses. It is proprietary to Fastly.


{unixStartTimeSeconds} is a Unix timestamp for when the request was first received by Fastly. It is given in seconds but to microsecond precision.

The value {durationMilliseconds} is an integer number of whole milliseconds elapsed since the start time of the request. In the event of a cache hit, this will most likely be zero, since the time required to look up and serve a cached object is usually under a millisecond. For a cache MISS, the number represents the number of milliseconds it took to retrieve the data from your origin server and send the response back to the requester.

HINT: You can use VCL functions and variables to control dates and times.

User contributed notes


Do you see an error in this page? Do you have an interesting use case, example or edge case people should know about? Share your knowledge and help people who are reading this page! (Comments are moderated; for support, please contact Fastly support)