# 2.5 HTTP Status Statistics

<figure><img src="/files/IHZBDEDJhdVxtFg5Csyk" alt=""><figcaption></figcaption></figure>

### ⚠️ HTTP Status Statistics

#### 🎯 Purpose

This panel breaks down HTTP response codes to assess website performance, stability, and user experience.

#### 📌 Key Components

* **Success (2xx)**: Indicates functional routes and services.
* **Redirects (3xx)**: Shows navigation flows and redirection behavior.
* **Client Errors (4xx)**: Typically caused by bad requests (e.g., 404, 403).
* **Server Errors (5xx)**: Usually reflect backend problems or overloads (e.g., 500, 503).

#### 📈 Visual Indicators

* Donut or pie chart distribution of status codes.
* Highlight of the most frequent status code.
* Each code includes total count and percentage share.

#### ✅ Use Cases

* Monitor for increasing 4xx/5xx errors.
* Detect broken links or misconfigured services.
* Ensure high 2xx ratio for healthy performance.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.shieldsguard.com/getting-started/2.-overview/2.5-http-status-statistics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.