log-explorer: EdgeTimeToFirstByteMs
Hi,
I'm trying to debug a case where a client has had issues with a few requests; and the request in question where the client reported something wrong with the request the EdgeTimeToFirstByteMs is insanly high: 1752617168804, but both EdgeStartTimestamp and EdgeEndTimestamp are 2025-07-15T22:06:08Z with OriginResponseDurationMs: 67.
Looking at more requests, they all have EdgeTimeToFirstByteMs in the 55-year range: 1752617168804, 1752595075556, etc. Even if it was NanoSeconds it would still be in the 30minute range; so I don't think the values are any where near correct.
2 open questions:
1. Is there a way for us to determine if the client actually got a response via logs?
2. Whats causing the EdgeTimeToFirstByteMs to be so far off?
0 Replies