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.9 days observed · generated 2026-08-27 18:57:44 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 87.6 | 84.8 | 78.4 |
| Status | Good | Good | Good |
| Availability | 99.84% | 99.98% | 99.98% |
| p50 latency | 87.4 ms | 105.2 ms | 106.9 ms |
| p95 latency | 100.0 ms | 122.7 ms | 195.7 ms |
| p99 latency | 125.9 ms | 147.7 ms | 243.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.34 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 1,218 | 18,275 |
| Unsupported | 0 | 0 | 223 |
| Samples | 111,986 | 113,323 | 26,386 |
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.8points
- Latency+2.8
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +2.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+9.2points
- Latency+9.1
- Head freshness+0.2
- Availability−0.1
- Correctness−0.0
The parts add to +9.2, exactly — the score is a weighted sum, so it comes apart.