> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/new-alarms/es/informes-y-monitoreo/alarms-devices-bandwidth-usage.md).

# Uso de ancho de banda de los dispositivos de Alarmas

Uso de ancho de banda para los dispositivos de Alarmas de Verkada

{% hint style="success" %}
Este artículo es una guía para nuevas Alarmas. Consulte esto [artículo](/classic-alarms/es/monitorizacion-e-informes/classic-alarms-devices-bandwidth-usage.md) si tiene alarmas clásicas. Vea [Nuevas alarmas frente a Alarmas clásicas](/new-alarms/es/primeros-pasos/new-alarms-vs-classic-alarms.md) si no está seguro de qué versión de alarmas tiene.
{% endhint %}

## BP52 (panel de alarma)

* Tasa de salida de 5 minutos: 10 kps
* Tasa de entrada de 5 minutos: 10 bps

{% hint style="warning" %}
Estos números pueden ser más altos o más bajos dependiendo de cuántos sensores estén conectados a un panel determinado, ya sea con cable o inalámbrico, y de cuántos eventos generen estos sensores. Otros factores incluyen la actualización de BK22/BE32, ya que esto utilizará más ancho de banda de red.
{% endhint %}


---

# 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://help.verkada.com/new-alarms/es/informes-y-monitoreo/alarms-devices-bandwidth-usage.md?ask=<question>&goal=<user_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.