Title: HTTP metrics
Author: WordPress VIP Documentation
Published: April 19, 2024
Last modified: February 5, 2026

---

 1. [Performance](https://docs.wpvip.com/performance/)
 2. [Insights & Metrics](https://docs.wpvip.com/performance/insights-metrics/)
 3. HTTP metrics

#  HTTP metrics

Insights into the performance of responses to HTTP requests that are made to an 
environment can be reviewed in [the **Insights & Metrics** panel](https://docs.wpvip.com/performance/insights-metrics/),
located in [the application view of the VIP Dashboard](https://docs.wpvip.com/vip-dashboard/application-view/).

Select the tab labeled “**HTTP**” to access data that provides insights into the
response times for requests, and the types and amounts of [HTTP response status codes](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status)
that are returned by the origin servers and edge cache servers.

 * **HTTP `2xx` responses** (e.g., `200`, `201`, `202`, `203`, `204`) indicate that
   the request succeeded.
 * **HTTP `3xx` responses** (e.g., `300`, `301`, `302`, `303`, `304`) indicate that
   the request was redirected.
 * **HTTP `4xx` responses** (e.g., `400`, `401`, `402`, `403`, `404`) indicate an
   error on the **client side**. Most of the time, they do not indicate critical
   issues affecting a site. For example, if a user requests a page that does not
   exist, they will see a `404 Not Found` error. Users who request access to an 
   application behind [IP restriction](https://docs.wpvip.com/ip-allow-list/) will
   see a `403 Forbidden` status if their IP address is not allowed. In some cases,
   a pattern of `404` responses may indicate a missing URL that needs to be redirected.
 * **HTTP `5xx` responses** (e.g., `500`, `501`, `502`, `503`, `504`) indicate an
   error on the **server side**. For example, a `500` response could result if an
   application’s server encounters a PHP fatal error and can no longer respond.

Possible causes for an increase in `5xx` status responses from an application:

 * An unexpected strain on the servers, caused by recently deployed code.
 * A sudden, substantial increase in site traffic.
 * A large number of site requests that are bypassing the [page cache](https://docs.wpvip.com/caching/page-cache/).
   Uncached SQL queries can overload the primary database, resulting in `503` responses
   being returned.
 * [Uncached WordPress functions](https://docs.wpvip.com/caching/uncached-functions/).
 * Plugins that generate [inefficient SQL queries](https://docs.wpvip.com/plugins/plugin-incompatibilities/#h-sql-query-intensive-plugins)
   or trigger SQL-intensive cron tasks that are not designed for a site that is 
   running at enterprise scale.

## Origin Response Time

The data in “Origin Response Time” indicates the duration of time it takes for [the origin server](https://docs.wpvip.com/origin-servers/)
to generate a response and send it back to [the page cache](https://docs.wpvip.com/caching/page-cache/).
The data also includes the response time for static assets when served from origin(
e.g., JavaScript, CSS, and image files in themes and plugins).

P50, P75, and P95 are percentile metrics for comparing the amount of time that was
required for some requests versus others made to the same environment to complete.

For example, P75 indicates that 75% of the requests on the environment had a response
time lower than the P75 value, while the remaining 25% had a higher response time.
This data represents the rate of change in the response times over time.

![](https://docs.wpvip.com/wp-content/uploads/sites/2/2025/07/origin-response-time-
legend-1024x601.png)

Example screenshot of data displayed in the Origin Response Time chart under the“
HTTP” tab of the Insights & Metrics panel of the VIP Dashboard.

## Origin Response Codes

Data in “Origin Response Codes” indicates the types of HTTP response status codes
with which the origin server responds to an HTTP request, and the average rate at
which they are returned.

Additional data highlighted in the upper right hand corner of the “Origin Response
Codes” panel:

 * **Average 4xx per minute**: The calculated average number of `4xx` responses 
   returned per minute by origin within the currently displayed range of time. Below
   the average number of `4xx` responses, the percent by which these responses have
   increased or decreased is also displayed.
 * **Average 5xx per minute**: The calculated average number of `5xx` responses 
   returned per minute by origin within the currently displayed range of time. Below
   the average number of `5xx` responses, the percent by which these responses have
   increased or decreased is also displayed.

A significant increase in the number of an application’s `5xx` responses are indicated
by [the **5xx Response Codes Rate** Anomaly Event Type](https://docs.wpvip.com/performance/insights-metrics/anomalies/#2-5xx-responses)
in the “Origin Response Codes” panel.

![](https://docs.wpvip.com/wp-content/uploads/sites/2/2025/07/Origin-Response-Codes-
1-1024x649.png)

Example screenshot of data displayed in the Origin Response Codes chart under the“
HTTP” tab of the Insights & Metrics panel of the VIP Dashboard.

## Origin 500 Response Rate

Data in “Origin 500 Response Rate” indicates the rate of `500` responses from origin
per 1,000 requests at the application level. High rates of `500` responses indicate
potential application issues that may impact functionality and should be investigated
and addressed as soon as possible.

In addition to the displayed chart, the calculated **Average Origin 500 Response
Rate** per 1,000 requests is displayed in the upper right hand corner of the panel.
Below the calculated average, the percent by which these average responses have 
increased or decreased is also displayed.

![](https://docs.wpvip.com/wp-content/uploads/sites/2/2025/07/Origin-500-Response-
Rate-1024x583.png)

Example screenshot of data displayed in the Origin 500 Response Rate chart under
the “HTTP” tab of the Insights & Metrics panel of the VIP Dashboard.

## Edge Response Codes

Data in “Edge Response Codes” indicates the types of HTTP response status code with
which [an edge cache CDN](https://docs.wpvip.com/vip-platform/edge-cache/) responds
to an HTTP request, and the rate at which they are returned.

A sudden and significant increase in the number of an application’s HTTP responses
with `429 Too Many Requests` response status codes are indicated by [the **Edge 429 Response Codes Rate** Anomaly Event Type](https://docs.wpvip.com/performance/insights-metrics/anomalies/#1-edge-429-response-rate)
in the “Edge Response Codes” panel.

![](https://docs.wpvip.com/wp-content/uploads/sites/2/2025/07/Edge-Response-Codes-
1024x615.png)

Example screenshot of data displayed in the Edge Response Codes chart under the “
HTTP” tab of the Insights & Metrics panel of the VIP Dashboard.

Last updated: February 05, 2026