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 20:41:49 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 83.0 | 78.4 | 70.7 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.92% | 100.00% |
| p50 latency | 87.2 ms | 108.9 ms | 110.1 ms |
| p95 latency | 99.1 ms | 127.4 ms | 192.2 ms |
| p99 latency | 123.4 ms | 154.5 ms | 236.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.33 blocks | 0.41 blocks | 0.61 blocks |
| Rate limited | 0 | 67 | 1,481 |
| Unsupported | 0 | 0 | 18 |
| Samples | 9,071 | 9,215 | 2,194 |
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.7points
- Latency+4.5
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +4.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+12.3points
- Latency+12.0
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +12.3, exactly — the score is a weighted sum, so it comes apart.