Traffic quality report: protocols, errors, cache and origin health
The Traffic quality page shows how your traffic looks at the edge over the last 24 hours, 7 days or 30 days: requests and data, the share served from cache, HTTP/3 and IPv6, 4xx and 5xx rates, who produced each error, and how your origin answers.
Analytics and reports
Traffic quality report: protocols, errors, cache and origin health
The Traffic quality page shows how your traffic looks at the edge over the last 24 hours, 7 days or 30 days: requests and data, the share served from cache, HTTP/3 and IPv6, 4xx and 5xx rates, who produced each error, and how your origin answers.
An account whose traffic is served through the CDN.
A role that can see Data Consumption.
Step-by-step guide
1
Check a release
Compare the period around the change.
Open Traffic quality and choose Last 24 hours.
In Over time, find the hour of the release and compare the 5xx dots before and after.
In Who produced the error and Origin health, see whether the change is on your server or at the edge.
Expected result: You know whether errors changed, and on which side.
Use cases
After a release you want to see whether errors went up, whether they came from your server or from your security rules, and how much of the traffic the cache absorbed.
Quick workflow
Open Traffic quality in the account menu, under Observability.
Choose the Period: Last 24 hours, Last 7 days or Last 30 days.
Read the cards at the top: Requests, Data served from cache, HTTP/3 share, IPv6 share, 4xx rate, 5xx rate, Origin response time and Origin connection errors.
Use Over time to see when something changed, then Status codes and Who produced the error to see what changed.
Look at Cache and Origin health to see what reached your server and how it answered.
Checks
The numbers are collected on our edge servers every 5 minutes, for the account you have selected.
Who produced the error splits 4xx and 5xx answers in two: Edge (WAF and security rules, access blocks, rate limits, redirect rules) and Origin / cache (error responses from your server, or served from cache).
Cache lists HIT, MISS, EXPIRED, STALE, UPDATING, REVALIDATED, BYPASS and NOCACHE, and how much data came from cache and how much from your origin. STALE means a cached copy was served while your origin was slow or failing.
Origin health shows requests to your origin, the retry share, connection errors (502/504), your origin's 5xx and 4xx rates, the average time to first byte and the data received from your origin.
Protocol shows HTTP/1.x, HTTP/2 and HTTP/3 by requests and by data, the IPv6 share and how many encrypted connections used TLS 1.3.
Aborted counts requests the visitor closed before the response finished, for example by skipping ahead in a video. They are not counted in any status class.
Frequently asked questions
The 5xx rate went up. Is it my server?
Look at Who produced the error first. If the errors are on the Origin side, Origin health tells you more: connection errors (502/504) mean the edge could not reach your server or waited too long for it. The 502 Bad Gateway and 504 Gateway Timeout guides walk through the causes.
How do I find which URLs return the errors?
The report shows totals. For the individual requests, turn on access log delivery and search the log lines by status code: see Access logs.
What are "Other 4xx (incl. 412)"?
4xx codes without a counter of their own. They are mostly 412 answers to cache purge requests for objects that were not in cache, and they do not affect your visitors.
Why is the request count a little higher than in older reports?
Traffic quality also counts the requests the edge answers itself, such as redirects and WAF blocks.
Who can open the report?
Everyone on the account who can see Data Consumption.