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 08:06:11 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 79.7 | 77.9 | 70.0 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.99% | 100.00% |
| p50 latency | 87.6 ms | 104.1 ms | 104.5 ms |
| p95 latency | 106.2 ms | 118.6 ms | 192.8 ms |
| p99 latency | 141.5 ms | 145.2 ms | 268.8 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.41 blocks | 0.60 blocks |
| Rate limited | 0 | 90 | 1,295 |
| Unsupported | 0 | 0 | 13 |
| Samples | 8,145 | 8,250 | 1,846 |
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.8points
- Latency+1.7
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +1.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+9.7points
- Latency+9.4
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +9.7, exactly — the score is a weighted sum, so it comes apart.