Endpoint Health Monitor
Continuously checks RPC providers for latency, timeouts, and stale blocks, automatically removing unhealthy endpoints so your Gateway stays stable and reliable.
Endpoint Health Monitor keeps your Gateway stable by automatically detecting unhealthy RPC endpoints and removing them from rotation before they cause failures. Instead of waiting for a node to go fully offline, the monitor continuously evaluates real-time behavior such as latency spikes, timeouts, and incomplete responses to ensure only healthy providers receive traffic.
With this PowerUp enabled, a single failing or degraded RPC provider cannot disrupt your application — ensuring consistent uptime, reliability, and resilience under all conditions.
Always safe: Endpoints are removed automatically when degraded, and re-added automatically when they recover no manual intervention required.
How to enable Endpoint Health Monitor?
Open your custom gateway
Open the custom gateway where you want to enable the Endpoint Health Monitor

Supported Networks
Endpoint Health Monitor is available for all chain gateways that are supported by Tatum, you can check all the supported chains on our dashboard here.
How Endpoint Health Monitor Works
Each endpoint is continuously evaluated across several reliability dimensions:
| Reliability Signal | What It Detects |
|---|---|
| Response time | Latency degradation |
| Connection Timeouts | Hanging / non-responsive nodes |
| Block freshness | Nodes falling behind chain tip |
Example — Gateway With Two Endpoints
| Endpoint | Status | Action |
|---|---|---|
| Provider A | Healthy | Actively used |
| Provider B | Unhealthy | Auto-removed until recovery |
This protects applications from intermittent provider failures — which are the most common cause of RPC downtime.
Request Usage
No request changes or parameters are required. Endpoint exclusion and reinstatement happen transparently.
curl -X POST https://ethereum-mainnet.gateway.tatum.io \
-H "x-api-key: {YOUR_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"id": 1,
"jsonrpc": "2.0",
"method": "eth_blockNumber",
"params": []
}'Even if one of your providers is failing — this request will always succeed by avoiding unhealthy nodes.
FAQs — Endpoint Health Monitor
How does an endpoint re-enter rotation?
Can the monitor be turned off?
Updated about 5 hours ago