> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-alerts-deprecated/mempool-alerts-deprecated/mempool-congestion-alert-deprecated.md).

# Mempool Congestion Alert - DEPRECATED

<mark style="color:red;">**THIS ENDPOINT HAS BEEN DEPRECATED AND WILL NO LONGER BE ACTIVELY MAINTAINED, UPDATED OR SUPPORTED**</mark>

**Alert Definition**

Alerts if the virtual size (vsize) of all mempool transactions exceeds 300,000,000 vBytes.

**Dictionary**

| Name                     | AlertID            | Category | Sub-category   | Type | Unit  | Interval |
| ------------------------ | ------------------ | -------- | -------------- | ---- | ----- | -------- |
| Mempool Congestion Alert | mempool\_vsize\_hi | Alert    | Mempool Alerts | Sum  | vsize | Ad hoc   |

**Interpretation**

By default, the nodes of a cryptonetwork have a dedicated area to store unprocessed transactions, the mempool. Since mempools rely on local storage, their capacity to store unprocessed transactions must be limited. Otherwise, the mempool could be exploited by an attacker flooding it with transactions. If a mempool has reached 300M vB, nodes may begin discarding transactions to free up space, which can cause disruptions.

**Potential Root Causes**

Increase demand for block space leading to congestion, often caused by market volatility.

A mempool flood attack, a type of DDoS attack whereby the mempool is spammed with transactions.

**Available Assets**

Bitcoin (BTC)

\\


---

# 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://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-alerts-deprecated/mempool-alerts-deprecated/mempool-congestion-alert-deprecated.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.