Add your node in three steps
You only need your node's RPC URL. No account, no API key, no config file.
-
Open the bot in Telegram
Search for @MonadBeaconBot in Telegram or follow the direct link: t.me/MonadBeaconBot. Tap Start to begin.
-
Send your RPC URL with /add
Type
/addfollowed by your node's RPC endpoint. For example:/add http://YOUR_SERVER_IP:8080The URL must start with
http://orhttps://and be publicly reachable from the internet. Port 8080 is the default Monad RPC port. -
Wait for the first check
The bot confirms the node was added and runs the first check within 60 seconds. Silence means OK — you'll only hear from the bot when something needs your attention.
/status right after adding your node to see the first health
result as soon as it's available.
Ready to add your node? Tap the button to open the bot directly in Telegram.
Open @MonadBeaconBotHow the bot works
Every 60 seconds the bot runs three independent checks against each registered RPC URL:
-
Reachability check — sends an
eth_blockNumberJSON-RPC call. If the endpoint does not respond, the node is marked unreachable and you receive an alert. - Block progress check — tracks block height over time. If the block number has not changed in 3 minutes, the node is considered stuck.
- Lag check — compares your node's block height to the public Monad testnet RPC. If your node is more than 10 blocks behind, you receive a lag alert.
Each problem triggers exactly one alert. When the node recovers you receive a recovery notification.
Alert types
| Alert | Meaning | When you get it | |
|---|---|---|---|
| 🔴 | Node unreachable | RPC endpoint stopped responding | First failed check after a healthy period |
| 🟡 | Block not progressing | Block height unchanged for >3 minutes | When stuck window is exceeded |
| 🟡 | Node is lagging | Your node is 10+ blocks behind network tip | First check where lag threshold is crossed |
| ✅ | Node recovered | Node returned to healthy state | First clean check after any alert |
All commands
| Command | Description |
|---|---|
/start |
Introduction and quick-start instructions |
/add <rpc_url> |
Add a node to monitor. Example: /add http://1.2.3.4:8080
|
/remove <rpc_url> |
Stop monitoring a node and remove it from your list |
/status |
Show current health, status label, and block height for all your nodes |
/list |
List your registered node URLs |
/help |
Show the command reference |
FAQ
Does the bot need access to my server?
No. The bot only makes outbound HTTP requests to your node's public RPC endpoint. No SSH, no credentials, no agent installed on your server.
What RPC port does Monad use?
The default Monad testnet RPC port is 8080. Your URL will typically look like
http://YOUR_SERVER_IP:8080. Make sure port 8080 is open for inbound TCP.
My node RPC is behind a firewall — can I still use the bot?
The bot checks from outside your network, so the RPC port must be reachable from the internet. Open port 8080 (or whichever port your RPC listens on) for inbound TCP.
How many nodes can I monitor?
Up to 5 nodes per Telegram user. Use /remove to free a slot.
Will I get spammed if my node stays down?
No. One alert when the problem starts, one recovery message when it resolves. No repeated messages while the issue persists.
Start monitoring your node now. Under 30 seconds — no signup, no config.
Open @MonadBeaconBot