> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/application-performance-monitoring/network/debugging-network.md).
# Debugging Network
Debugging Network lets you see the list of failures on a network request, labeled by type: server-side or client-side errors.
Luciq lists every failure detected on a network request and labels it by type, so you can tell at a glance whether it is a **server-side** or a **client-side** failure.
To get there, open any network request from your dashboard and switch to the **Debugging** tab. You can narrow down the data using the filters at the top of the page, such as date, app version, device, OS version, country, radio, carrier, feature flags, response time, payload size, and trace attributes.
***
### Failures Timeline
The failures timeline gives you a quick view of which failures are currently happening and which ones have already stopped.
Each row represents a single failure and shows when it occurred over the selected period. Highlighted cells mark intervals with at least one failed occurrence, while unhighlighted cells had no failures or no recorded data.
***
### Failures List
The failures list shows all server-side and client-side failures on the request, along with the rate and impact of each one.
#### What Does Each Failure Show?
Every failure displays its **count** and **rate**, so you can quickly understand how much it impacts your users. Selecting a failure reveals three sections of details:
* **Outliers:** the segments where this failure occurs disproportionately often compared to the rest of its occurrences.
* **Poor occurrences:** the top 10 worst-performing occurrences of this failure, based on latency.
* **Patterns:** how this failure breaks down across each dimension, so you can see which segment of your users it affects most.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/application-performance-monitoring/network/debugging-network.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
