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
30d window · 2.7 days observed · generated 2026-08-27 14:19:00 UTC
| Metric | NodeReal | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 87.7 | 85.0 | 78.5 |
| Status | Good | Good | Good |
| Availability | 99.83% | 99.98% | 99.98% |
| p50 latency | 87.4 ms | 104.9 ms | 106.6 ms |
| p95 latency | 100.1 ms | 122.3 ms | 196.1 ms |
| p99 latency | 126.0 ms | 146.3 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 1,154 | 17,095 |
| Unsupported | 0 | 0 | 207 |
| Samples | 104,578 | 105,809 | 24,635 |
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.7
- 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.2
- 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.