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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 01:27:17 UTC
| Metric | NodeReal | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 4 | 5 | 7 | 8 |
| Score | 86.3 | 83.8 | 76.7 | 60.3 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.97% | 99.99% | 99.92% | 79.94% |
| p50 latency | 87.2 ms | 104.7 ms | 121.6 ms | 1326.0 ms |
| p95 latency | 98.8 ms | 120.6 ms | 215.3 ms | 7406.7 ms |
| p99 latency | 115.8 ms | 148.6 ms | 232.0 ms | 9776.0 ms |
| Correctness | 99.97% | 99.99% | 99.97% | 96.96% |
| Head lag | 0.34 blocks | 0.41 blocks | 0.39 blocks | 0.94 blocks |
| Rate limited | 0 | 34 | 0 | 1,491 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,673 | 8,829 | 8,828 | 2,056 |
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.5points
- Latency+2.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +2.5, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+9.6points
- Latency+9.5
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +9.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+26.0points
- Latency+16.7
- Availability+8.0
- Head freshness+0.7
- Correctness+0.6
The parts add to +26.0, exactly — the score is a weighted sum, so it comes apart.