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 14:29:33 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 82.9 | 78.6 | 70.5 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.99% | 100.00% |
| p50 latency | 87.7 ms | 108.1 ms | 108.3 ms |
| p95 latency | 99.4 ms | 125.7 ms | 197.2 ms |
| p99 latency | 126.4 ms | 153.2 ms | 231.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.33 blocks | 0.41 blocks | 0.45 blocks |
| Rate limited | 0 | 58 | 1,395 |
| Unsupported | 0 | 0 | 16 |
| Samples | 8,740 | 8,893 | 2,081 |
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
+4.3points
- Latency+4.2
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +4.3, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+12.5points
- Latency+12.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +12.5, exactly — the score is a weighted sum, so it comes apart.