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 16:09:28 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 7 |
| Score | 82.3 | 78.5 | 69.4 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.98% | 100.00% |
| p50 latency | 87.3 ms | 107.9 ms | 110.9 ms |
| p95 latency | 99.4 ms | 124.7 ms | 216.0 ms |
| p99 latency | 125.6 ms | 139.2 ms | 332.7 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.35 blocks | 0.41 blocks | 0.49 blocks |
| Rate limited | 0 | 1 | 1,352 |
| Unsupported | 0 | 0 | 14 |
| Samples | 8,217 | 8,360 | 1,918 |
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
+3.9points
- Latency+3.8
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +3.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+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.