> 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/missed-slot-alert-deprecated.md).

# Missed Slot 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 a slot has been missed by a Proof-of-Stake validator. For context, a slot represents an opportunity for a block producer (or validator) to create a block. If the validator fails to produce a block at the slot, it is considered missed and the blockchain progresses to the following slot.

Our methodology is designed to infer the number of missed slots on the basis of the time between blocks. If a block takes more than 15 seconds to arrive, it can be inferred that a slot has been missed as per Ethereum’s consensus rules. Note that if two slots are missed consecutively, we would still need to wait until a valid to arrive to capture it, as per the methodology.

**Dictionary**

| Name              | AlertID              | Category | Sub-category  | Type  | Unit  | Interval |
| ----------------- | -------------------- | -------- | ------------- | ----- | ----- | -------- |
| Missed Slot Alert | 1b\_slot\_missed\_hi | Alert    | ETH PoS Alert | Count | Slots | Ad hoc   |

**Interpretation**

A missed slot might be the result of a validator going offline, or connectivity issues impacting the communications between validators. In more concerning scenarios where the missed slot rate consistently upticks, it might indicative of a bug, or a large cohort of validators going offline.

**Potential Root Causes**

The validator responsible to produce a block at that height is unavailable or otherwise unable to do so. If persistent, this could also be a sign of a bug at the client level.

**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/missed-slot-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.