> 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/reports-and-monitoring/alarms-devices-bandwidth-usage.md).

# Alarms Devices Bandwidth Usage

Bandwidth usage for Verkada Alarms devices

{% hint style="success" %}
This article is a guide for new Alarms. Refer to this [article](/classic-alarms/monitoring-and-reports/classic-alarms-devices-bandwidth-usage.md) if you have classic Alarms. See [New Alarms vs Classic Alarms](/new-alarms/getting-started/new-alarms-vs-classic-alarms.md) if you are unsure which version of Alarms you have.
{% endhint %}

## BP52 (Alarm panel)

* 5 minute output rate: 10kps
* 5 minute input rate: 10bps

{% hint style="warning" %}
These numbers may be higher or lower depending on how many sensors are connected to a given panel either wired or wireless and how many events these sensors generate. Other factors include BK22/BE32’s updating as this will use more network bandwidth.
{% 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/reports-and-monitoring/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.