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
1h window · 60 minutes observed · generated 2026-08-27 20:23:22 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 82.9 | 78.5 | 71.3 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 87.0 ms | 108.7 ms | 108.7 ms |
| p95 latency | 98.9 ms | 124.7 ms | 181.6 ms |
| p99 latency | 121.6 ms | 152.8 ms | 194.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.42 blocks | 0.65 blocks |
| Rate limited | 0 | 16 | 275 |
| Unsupported | 0 | 0 | 2 |
| Samples | 1,564 | 1,604 | 396 |
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.4points
- Latency+4.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +4.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+11.5points
- Latency+11.2
- Head freshness+0.4
- Availability+0.0
- Correctness+0.0
The parts add to +11.5, exactly — the score is a weighted sum, so it comes apart.