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
30d window · 3.9 days observed · generated 2026-08-28 18:44:08 UTC
| Metric | dRPC | Merkle | 1RPC |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 90.9 | 78.0 | 61.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.95% | 99.99% | 83.16% |
| p50 latency | 33.8 ms | 106.9 ms | 265.3 ms |
| p95 latency | 73.1 ms | 195.8 ms | 4975.4 ms |
| p99 latency | 175.2 ms | 245.5 ms | 8455.9 ms |
| Correctness | 99.99% | 100.00% | 97.38% |
| Head lag | 0.36 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 760 | 24,518 | 26,166 |
| Unsupported | 0 | 296 | 0 |
| Samples | 149,918 | 35,397 | 31,743 |
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
+12.9points
- Latency+12.8
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.2points
- Latency+21.3
- Availability+6.7
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.2, exactly — the score is a weighted sum, so it comes apart.