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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 09:52:45 UTC
| Metric | Tenderly | dRPC | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 2 | 3 | 6 | 7 |
| Score | 99.3 | 88.0 | 70.1 | 69.5 |
| Status | Excellent | Good | Degraded | Degraded |
| Availability | 99.95% | 99.94% | 100.00% | 99.92% |
| p50 latency | 18.9 ms | 31.7 ms | 105.1 ms | 119.8 ms |
| p95 latency | 33.6 ms | 66.9 ms | 194.3 ms | 208.7 ms |
| p99 latency | 122.9 ms | 159.9 ms | 228.8 ms | 226.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.60 blocks | 0.42 blocks |
| Rate limited | 0 | 40 | 1,508 | 1 |
| Unsupported | 0 | 0 | 18 | 0 |
| Samples | 9,513 | 9,359 | 2,197 | 9,507 |
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.
TenderlyvsdRPC
+11.3points
- Latency+11.5
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +11.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.2points
- Latency+29.1
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +29.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+29.8points
- Latency+29.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +29.8, exactly — the score is a weighted sum, so it comes apart.