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
1h window · 60 minutes observed · generated 2026-08-27 12:29:48 UTC
| Metric | dRPC | Merkle | 1RPC |
|---|---|---|---|
| Rank | 3 | 6 | 9 |
| Score | 84.6 | 70.5 | 0.0 |
| Status | Good | Degraded | Poor |
| Availability | 99.94% | 100.00% | 0.00% |
| p50 latency | 33.9 ms | 112.0 ms | 0.0 ms |
| p95 latency | 90.2 ms | 204.6 ms | 0.0 ms |
| p99 latency | 193.6 ms | 217.6 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.38 blocks | 0.20 blocks | no cohort |
| Rate limited | 9 | 253 | 273 |
| Unsupported | 0 | 2 | 0 |
| Samples | 1,587 | 368 | 315 |
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 dRPC, the highest scorer of those selected.
dRPCvsMerkle
+14.2points
- Latency+14.4
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+84.6points
- Availability+40.0
- Correctness*+20.0
- Latency*+15.1
- Head freshness*+9.5
The parts add to +84.6, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.