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
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 17:52:11 UTC
| Metric | Tenderly | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 7 |
| Score | 99.4 | 94.9 | 70.8 | 69.5 |
| Status | Excellent | Excellent | Degraded | Degraded |
| Availability | 99.98% | 100.00% | 100.00% | 99.89% |
| p50 latency | 20.2 ms | 25.5 ms | 110.7 ms | 125.1 ms |
| p95 latency | 33.4 ms | 50.5 ms | 191.8 ms | 217.5 ms |
| p99 latency | 65.4 ms | 113.1 ms | 235.0 ms | 242.3 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.55 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 1,510 | 0 |
| Unsupported | 0 | 0 | 20 | 0 |
| Samples | 9,520 | 9,588 | 2,224 | 9,479 |
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
+4.5points
- Latency+4.5
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.6points
- Latency+28.5
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +28.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+29.9points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.