CF-Cache-Status is in MISS state for a long time

I refresh a page when it’s cache was expired, but the CF-Cache-Status is in MISS state for a long time,why?

example url:

Normally, if i refresh it several times, it will become HIT status。But now its performance is not stable.

Can you post your request headers, too?

[[email protected] ~]$ curl -v | head
 % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                Dload  Upload   Total   Spent    Left  Speed
 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* About to connect() to port 443 (#0)
*   Trying
* Connected to ( port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
 CApath: none
* SSL connection using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject:,O="CloudFlare, Inc.",L=San Francisco,ST=CA,C=US
*       start date: Feb 10 00:00:00 2019 GMT
*       expire date: Feb 10 12:00:00 2020 GMT
*       common name:
*       issuer: CN=CloudFlare Inc ECC CA-2,O="CloudFlare, Inc.",L=San Francisco,ST=CA,C=US
> GET /5047.html HTTP/1.1
> User-Agent: curl/7.29.0
> Host:
> Accept: */*
< HTTP/1.1 200 OK
< Date: Sat, 04 May 2019 02:34:24 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=d083cefc974f746ce4fff3455742b8c631556937264; expires=Sun, 03-May-20 02:34:24 GMT; path=/;; HttpOnly; Secure
< Expires: Sun, 03 May 2020 02:34:24 GMT
< X-Pingback:
< X-Cache: HIT
< X-Frame-Options: SAMEORIGIN
< X-Content-Type-Options: nosniff
< Content-Security-Policy: upgrade-insecure-requests
< Strict-Transport-Security: max-age=15552000; includeSubDomains; preload
< CF-Cache-Status: MISS
< Cache-Control: public, max-age=31536000
< Accept-Ranges: bytes
< Expect-CT: max-age=604800, report-uri=""
< Server: cloudflare
< CF-RAY: 4d17134ece582e25-NRT
{ [data not shown]
<!DOCTYPE html>

No, request headers are sent from your browser. They looks very similar to the response headers. Like this pair:

Sorry,I misunderstood it.

But some pages is right in HIT status,like this page:

If you got a HIT I think everything is in order…

Generally, to get a resource cached by a node:

  • resource has to be requested three times
  • in a certain amount of time
  • by the same node
1 Like

I got it …
Caches between nodes are not synchronized? Thus,The cache hit rate is very low.

I think in Biz and Ent plans you can synchronize nodes. But not in Free or Pro.

I think these conditions are met. but is can not cached as expected…
CDN node Always been 4d172ec2eac1d326-LAX , request too many times,but status always been MISS…

Uh… Now I understand everything.
Tks ~

You’re welcome!

This topic was automatically closed after 30 days. New replies are no longer allowed.