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 · 44 hours observed · generated 2026-08-26 16:23:34 UTC
| Metric | NodeReal | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 88.5 | 78.4 | 77.5 |
| Status | Good | Good | Good |
| Availability | 99.74% | 99.97% | 99.87% |
| p50 latency | 87.5 ms | 106.5 ms | 118.1 ms |
| p95 latency | 100.0 ms | 196.8 ms | 208.7 ms |
| p99 latency | 123.7 ms | 245.4 ms | 233.0 ms |
| Correctness | 99.99% | 100.00% | 99.98% |
| Head lag | 0.35 blocks | 0.47 blocks | 0.39 blocks |
| Rate limited | 0 | 11,495 | 0 |
| Unsupported | 0 | 140 | 0 |
| Samples | 69,645 | 16,553 | 70,724 |
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.
NodeRealvsMerkle
+10.2points
- Latency+10.1
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+11.0points
- Latency+11.0
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +11.0, exactly — the score is a weighted sum, so it comes apart.