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 05:34:35 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 85.7 | 83.8 | 77.5 |
| Status | Good | Good | Good |
| Availability | 99.63% | 99.99% | 100.00% |
| p50 latency | 87.6 ms | 103.7 ms | 104.3 ms |
| p95 latency | 98.8 ms | 117.3 ms | 198.1 ms |
| p99 latency | 114.6 ms | 142.9 ms | 274.4 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.34 blocks | 0.40 blocks | 0.55 blocks |
| Rate limited | 0 | 42 | 1,433 |
| Unsupported | 0 | 0 | 18 |
| Samples | 8,865 | 9,042 | 2,074 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsBlast API
+1.9points
- Latency+2.0
- Availability−0.1
- Head freshness+0.1
- Correctness+0.0
The parts add to +1.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+8.2points
- Latency+8.1
- Head freshness+0.3
- Availability−0.1
- Correctness+0.0
The parts add to +8.2, exactly — the score is a weighted sum, so it comes apart.