# 🔍 Bridge Node Monitoring

This section demonstrates how to monitor the status of your Celestia **bridge node** using the **CelestiaUltraBot** in Telegram. Below are two example screenshots showing typical node states: a healthy synchronized node and a node experiencing synchronization issues.

#### ✅ Example: Healthy Bridge Node

<figure><img src="/files/pdtIqbroO4UfIXmNvC4l" alt="" width="375"><figcaption></figcaption></figure>

This screenshot shows a bridge node that is fully operational:

* Node is successfully synchronized with the network.
* It is connected to peers and actively exchanging P2P messages.
* Resource usage (RAM, threads, GC pause time) is within normal limits.
* The node has been running stably for over 24 hours.
* It is running a recent version of the bridge software.

Use this as a reference for what a **properly working node** should look like.

#### ⚠️ Example: Bridge Node with Sync Issues

<figure><img src="/files/TI8RHXeg0VenUInIU96N" alt="" width="375"><figcaption></figcaption></figure>

This screenshot shows a bridge node that is encountering **synchronization errors**:

* The bot reports failed sync attempts and shows how many blocks are missing.
* System load is significantly higher, including memory usage and GC pause time.
* Sync issues may be caused by high system load, poor network connectivity, or outdated software.

This example helps identify and understand the symptoms of a **malfunctioning or unsynchronized node**.


---

# Agent Instructions: 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:

```
GET https://services.validexis.com/celestiaultrabot/bridge-node-monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.