> 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/ethereum-proof-of-stake-alerts-deprecated/decrease-in-total-block-fees-alert-deprecated.md).

# Decrease in Total Block Fees 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 Total Block Fees of a given block are lower than its 100-block predecessors. Total Block Fees represent the total fees associated with a block. In Ethereum, this is the sum of all Base Fees and Priority Fees in a block.

**Dictionary**

| Name                               | AlertID                    | Category | Sub-category  | Type | Unit | Interval |
| ---------------------------------- | -------------------------- | -------- | ------------- | ---- | ---- | -------- |
| Decrease in Total Block Fees Alert | block\_fees\_rsd\_100b\_lo | Alert    | ETH PoS Alert | Sum  | Gas  | Ad hoc   |

**Interpretation**

A consistent decrease in Total Block Fees might occur naturally as a result of a decrease in demand for block space. In some circumstances, it may indicative of outages at infrastructure providers that service cryptoasset wallets. For example, when Infura, a popular node-as-a-service provider faces downtime, this can usually be captured by a decrease in Total Block Fees.

**Potential Root Causes**

Organic decrease in demand for block space. Outage at a critical infrastructure provider preventing nodes from broadcasting transactions.

**Asset Coverage**

Ethereum (ETH)

\\

\\


---

# 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/ethereum-proof-of-stake-alerts-deprecated/decrease-in-total-block-fees-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.