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 03:33:17 UTC
| Metric | dRPC | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 6 |
| Score | 91.2 | 85.6 | 83.6 | 77.7 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.98% | 99.61% | 99.99% | 100.00% |
| p50 latency | 32.4 ms | 87.6 ms | 103.8 ms | 105.8 ms |
| p95 latency | 62.4 ms | 99.2 ms | 119.1 ms | 194.3 ms |
| p99 latency | 162.8 ms | 116.4 ms | 147.1 ms | 281.6 ms |
| Correctness | 99.98% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.34 blocks | 0.41 blocks | 0.47 blocks |
| Rate limited | 7 | 0 | 32 | 1,449 |
| Unsupported | 0 | 0 | 0 | 20 |
| Samples | 8,855 | 8,828 | 9,007 | 2,107 |
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.6points
- Latency+5.5
- Availability+0.1
- Head freshness−0.0
- Correctness−0.0
The parts add to +5.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+7.7points
- Latency+7.6
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +7.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.5points
- Latency+13.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.5, exactly — the score is a weighted sum, so it comes apart.