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
24h window · 24 hours observed · generated 2026-08-27 09:29:35 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 86.4 | 83.8 | 77.8 |
| Status | Good | Good | Good |
| Availability | 100.00% | 99.99% | 100.00% |
| p50 latency | 87.2 ms | 105.3 ms | 107.1 ms |
| p95 latency | 100.3 ms | 122.4 ms | 195.4 ms |
| p99 latency | 128.7 ms | 146.2 ms | 239.8 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.34 blocks | 0.42 blocks | 0.51 blocks |
| Rate limited | 0 | 364 | 6,084 |
| Unsupported | 0 | 0 | 75 |
| Samples | 37,444 | 37,831 | 8,693 |
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
+2.6points
- Latency+2.5
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +2.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+8.6points
- Latency+8.4
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +8.6, exactly — the score is a weighted sum, so it comes apart.