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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 02:37:08 UTC
| Metric | Tenderly | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 6 | 7 | 8 |
| Score | 99.3 | 77.8 | 76.6 | 60.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 99.92% | 79.94% |
| p50 latency | 18.3 ms | 106.1 ms | 121.1 ms | 1326.0 ms |
| p95 latency | 31.8 ms | 192.9 ms | 214.8 ms | 7406.7 ms |
| p99 latency | 55.1 ms | 278.7 ms | 231.4 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 99.99% | 96.96% |
| Head lag | 0.46 blocks | 0.44 blocks | 0.38 blocks | 0.94 blocks |
| Rate limited | 0 | 1,465 | 0 | 1,535 |
| Unsupported | 0 | 19 | 0 | 0 |
| Samples | 9,109 | 2,156 | 9,092 | 2,109 |
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.
TenderlyvsMerkle
+21.5points
- Latency+21.5
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+22.7points
- Latency+22.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.7, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+39.0points
- Latency+29.9
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +39.0, exactly — the score is a weighted sum, so it comes apart.