Origin analytics
Find slow origin responses and investigate origin errors.
Origin measurements
Open Speed > Origin analytics for your website. Select Last hour, Last 24 hours, or Last 7 days.
To inspect one endpoint, enter its exact path. Query strings are excluded. Recorded paths are limited to 128 bytes, so longer paths can share the same recorded prefix.
Measurements refresh every 30 seconds. Times use your browser's timezone.
Summary cards
| Measurement | Definition |
|---|---|
| Origin requested | Requests sent to an origin as a share of retained requests that support origin telemetry. |
| Response success rate | Measured origin attempts that received response headers, including HTTP 4xx and 5xx responses. |
| Response time (P95) | Time within which about 95% of measured origin responses returned headers. |
| Origin error rate | Measured origin attempts that returned HTTP 5xx or received no response headers. |
Cache hits and requests blocked before reaching an origin are excluded from origin attempts. A 5xx response counts in both response success rate and origin error rate: the server responded, but returned an error.
Response time and status codes
The response-time chart shows approximate P50, P95, and P99 values. These include connection setup, request transmission, retries, and the wait for response headers. They exclude the response body and browser rendering.
Status class distribution groups origin responses into 2xx, 3xx, 4xx, and 5xx. Select a class to inspect individual codes in Status code breakdown.
No response means Loclix did not receive response headers. Possible causes include cancellation, timeouts, and network failures. The status returned to the visitor can differ from the origin status.
Connection timing
| Phase | What it measures |
|---|---|
| TCP handshake | Time to establish a TCP connection. |
| TLS handshake | Time to establish encryption; for HTTP/3, the combined QUIC/TLS handshake. |
| Response wait | Time from sending the request to receiving response headers. |
A reused connection reports zero handshake time. HTTP/3 has no TCP handshake. Missing measurements appear as unavailable, including unsupported tunnel timings and origin phases for requests relayed through another edge.
Each phase shows a mean across the records available for that phase. Do not add these means to compare them with a response-time percentile. With retries, phases describe the final attempt while response time includes earlier attempts.
Endpoint comparison
Top endpoints lists up to 20 paths. Rank them by P95 response time, request count, or error rate. Select a path to filter the page. Measured shows how many origin requests have timing data.
Chart controls
Hover over a chart or tap it to inspect an interval. Use Left, Right, Home, or End with the chart focused. Select a legend item to hide or show a series.
Select Expand for a larger chart. Select Close or press Escape to return.
Requirements and coverage
The panel reports how much of the request history includes the required measurements. Metrics exclude unsupported records; an empty denominator shows Unavailable. Gaps mean missing data, not zero traffic.
Origin analytics uses retained request history for the selected range, beyond the latest-100 request lookup. Records are kept for seven days. Delayed or missing reports can leave history incomplete, and older records may lack timing fields.
If loading fails, select Retry. Contact support if measurements remain unavailable while your website is receiving origin traffic.
See Monitoring to find an individual request.