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-28 00:15:56 UTC
| Metric | Tenderly | PublicNode | dRPC | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 9 |
| Score | 99.4 | 97.8 | 91.9 | 53.2 |
| Status | Excellent | Excellent | Excellent | Degraded |
| Availability | 100.00% | 100.00% | 99.99% | 61.54% |
| p50 latency | 18.3 ms | 21.1 ms | 32.8 ms | 2668.5 ms |
| p95 latency | 31.7 ms | 39.7 ms | 64.1 ms | 8458.8 ms |
| p99 latency | 54.2 ms | 93.6 ms | 166.6 ms | 12423.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 98.77% |
| Head lag | 0.46 blocks | 0.48 blocks | 0.36 blocks | 0.96 blocks |
| Rate limited | 0 | 0 | 11 | 1,403 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,536 | 8,614 | 8,382 | 1,739 |
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
+1.6points
- Latency+1.6
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +1.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+7.6points
- Latency+7.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+46.2points
- Latency+30.0
- Availability+15.4
- Head freshness+0.6
- Correctness+0.2
The parts add to +46.2, exactly — the score is a weighted sum, so it comes apart.