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
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 22:18:21 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 88.4 | 69.9 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 18.8 ms | 35.1 ms | 108.2 ms |
| p95 latency | 33.2 ms | 67.0 ms | 201.2 ms |
| p99 latency | 64.9 ms | 174.4 ms | 241.7 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.39 blocks | 0.46 blocks |
| Rate limited | 0 | 13 | 1,368 |
| Unsupported | 0 | 0 | 13 |
| Samples | 8,610 | 8,451 | 1,991 |
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.0points
- Latency+11.1
- Head freshness−0.1
- Correctness−0.0
- Availability+0.0
The parts add to +11.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.5points
- Latency+29.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +29.5, exactly — the score is a weighted sum, so it comes apart.