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 06:17:53 UTC
| Metric | NodeReal | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 6 | 7 |
| Score | 81.0 | 70.1 | 69.5 |
| Status | Good | Degraded | Degraded |
| Availability | 99.99% | 100.00% | 99.92% |
| p50 latency | 87.1 ms | 104.8 ms | 118.6 ms |
| p95 latency | 99.5 ms | 193.2 ms | 207.0 ms |
| p99 latency | 129.1 ms | 283.4 ms | 224.9 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.50 blocks | 0.40 blocks |
| Rate limited | 0 | 1,339 | 0 |
| Unsupported | 0 | 18 | 0 |
| Samples | 8,453 | 1,900 | 8,547 |
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.8points
- Latency+10.7
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +10.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+11.5points
- Latency+11.4
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +11.5, exactly — the score is a weighted sum, so it comes apart.