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
7d window · 2.0 days observed · generated 2026-08-26 21:12:46 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 88.7 | 85.6 | 78.4 |
| Status | Good | Good | Good |
| Availability | 99.76% | 99.98% | 99.98% |
| p50 latency | 87.4 ms | 104.6 ms | 106.7 ms |
| p95 latency | 100.0 ms | 122.6 ms | 195.9 ms |
| p99 latency | 124.1 ms | 144.4 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.47 blocks |
| Rate limited | 0 | 915 | 12,728 |
| Unsupported | 0 | 0 | 155 |
| Samples | 77,302 | 78,165 | 18,341 |
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.1points
- Latency+3.1
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +3.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+10.3points
- Latency+10.2
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +10.3, exactly — the score is a weighted sum, so it comes apart.