> 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-bugsplat-handles-large-crash-volumes.md).

# How BugSplat handles large crash volumes

### Built to scale

BugSplat is built entirely on AWS and is scalable to any application size or crash submission rate. We process crashes for millions of installed applications around the world and have a [99.99%](http://stats.bugsplat.com/) application uptime.

### How users handle crashes at scale inside the app

A great example of how BugSplat handles crashes is the [**Dashboard**](https://app.bugsplat.com/v2/dashboard) page. This tool provides a view of the stability of your application in an easy-to-use line graph, visually helping you see how your software is performing for users.

To get more detailed information on crashes, use the [**Summary**](https://app.bugsplat.com/v2/summary) page to see your crash data organized by their crash signature (or StackKey).

By looking at the Count column, you can see exactly how many times a particular crash defect caused your software to crash. You can then drill into that crash defect to inspect all the individual crash reports that are associated with the StackKey.

Because your crashes are automatically organized, you don’t have to waste time guessing which crash defects need your attention. Whatever Stack Key’s are near the top of your [**Summary**](https://app.bugsplat.com/v2/summary) page should absolutely command your team’s attention.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.bugsplat.com/education/faq/how-bugsplat-handles-large-crash-volumes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.