> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/education/faq/how-does-crash-rate-limiting-work.md).

# How Does Crash Rate Limiting Work?

BugSplat enforces rate limits on crash reports to prevent rapid exhaustion of your monthly crash allocation in a short period of time. This policy ensures consistent usage of your crash reporting capacity over the duration of your subscription period, avoiding sudden spikes that could cause you to exceed your monthly limit unexpectedly.

**How Rate Limiting Works:** Rate limiting is designed to control how many crash reports can be sent to BugSplat over short periods. This protects your monthly crash allowance from being quickly depleted by sudden spikes in crashes.

To determine the rate limit, BugSplat first calculates the average number of crashes per minute that your subscription allows. We then set the rate limit at **10x** this average value. This allows flexibility for temporary increases in crash volume while maintaining protection against sustained high-frequency bursts that could exhaust your limit prematurely.

For example, if your plan allows for **100,000 crashes per month**, BugSplat calculates the average number of crashes per minute based on that allowance. The rate limit is then set at **10 times** the average, ensuring that brief spikes in crash reports can be accommodated without exceeding your monthly limit too quickly.


---

# 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.bugsplat.com/education/faq/how-does-crash-rate-limiting-work.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.