Cache edge server taking 1+min to respond on a HIT

Website, Application, Performance
1

What is the name of the domain?

nottobemadepublic2332122.com

What is the error number?

noerror

What is the error message?

noerror

What is the issue you’re encountering

Edge server is taking over 1 minute to respond in some cases

What steps have you taken to resolve the issue?

Tried multiple break outs, checked ips etc

What are the steps to reproduce the issue?

Visit the main website. This doesnt help but the extract below is from the CF logs. Any hint as to what could caused the server to do this.

We notice the response to the client is instant on the headers but the content takes time to come through

"CacheCacheStatus": "hit",
"EdgeCFConnectingO2O": false,
"EdgeColoCode": "LHR",
"EdgeEndTimestamp": "2024-09-04T11:40:09Z",
"EdgeResponseBodyBytes": 244182,
"EdgeResponseBytes": 244765,
"EdgeResponseContentType": "image/jpeg",
"EdgeResponseStatus": 200,
"EdgeServerIP": "",
"EdgeStartTimestamp": "2024-09-04T11:39:09Z",
"EdgeTimeToFirstByteMs": 14,
"OriginDNSResponseTimeMs": 0,
2

That domain is not registered. A typo maybe?

4

Hi

I’ve tried to keep it private as its a restricted url so can’t be hit without auth. I was hoping the edge response times was a good indication. We are on the busuiness plan with no changes to cache. But seems odd the edge servers take 1min+ in some cases. This happens on a HIT but also when we do a forced bypass cache. Almost at the point we need to bypass CF but that presents other issues.

Thanks

5

All the log says it that it took a minute, but I would’ve believed you without the log.

There are about a hundred things that could be wrong. You’re in a much better position to find them than anyone else here if we can’t test anything.

1 Like