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-27 13:05:57 UTC
| Metric | dRPC | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 6 |
| Score | 87.8 | 82.7 | 78.6 | 70.1 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.94% | 100.00% | 100.00% | 100.00% |
| p50 latency | 33.5 ms | 87.8 ms | 107.6 ms | 108.0 ms |
| p95 latency | 74.5 ms | 99.6 ms | 124.8 ms | 200.3 ms |
| p99 latency | 177.9 ms | 123.9 ms | 153.7 ms | 231.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.34 blocks | 0.40 blocks | 0.49 blocks |
| Rate limited | 40 | 0 | 78 | 1,324 |
| Unsupported | 0 | 0 | 0 | 16 |
| Samples | 8,132 | 8,120 | 8,264 | 1,963 |
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.
dRPCvsNodeReal
+5.1points
- Latency+5.2
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +5.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+9.2points
- Latency+9.2
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +9.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.7points
- Latency+17.6
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +17.7, exactly — the score is a weighted sum, so it comes apart.