Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on Ethereum
- Tenderly
- PublicNode
- NodeReal
- dRPC
- Blast API
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 09:12:39 UTC
| Metric | Tenderly | PublicNode | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 7 |
| Score | 99.4 | 99.0 | 69.3 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.94% | 100.00% | 100.00% |
| p50 latency | 18.6 ms | 20.9 ms | 109.3 ms |
| p95 latency | 32.9 ms | 34.3 ms | 205.5 ms |
| p99 latency | 58.4 ms | 70.2 ms | 250.3 ms |
| Correctness | 99.94% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.47 blocks | 0.58 blocks |
| Rate limited | 0 | 0 | 259 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,612 | 1,612 | 382 |
9 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against Tenderly, the highest scorer of those selected.
TenderlyvsPublicNode
+0.4points
- Latency+0.4
- Availability−0.0
- Correctness−0.0
- Head freshness+0.0
The parts add to +0.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+30.1points
- Latency+30.0
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +30.1, exactly — the score is a weighted sum, so it comes apart.