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
24h window · 24 hours observed · generated 2026-08-28 05:30:17 UTC
| Metric | NodeReal | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 4 | 5 | 7 | 8 |
| Score | 86.6 | 83.8 | 76.8 | 59.0 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.90% | 99.97% | 99.93% | 76.74% |
| p50 latency | 87.5 ms | 106.4 ms | 122.3 ms | 1326.0 ms |
| p95 latency | 99.9 ms | 123.4 ms | 214.5 ms | 7406.7 ms |
| p99 latency | 127.8 ms | 150.9 ms | 235.3 ms | 9776.0 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 96.96% |
| Head lag | 0.34 blocks | 0.41 blocks | 0.40 blocks | 0.94 blocks |
| Rate limited | 0 | 257 | 1 | 6,527 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,427 | 38,063 | 38,038 | 7,829 |
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.7points
- Latency+2.7
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +2.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+9.8points
- Latency+9.7
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +9.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+27.6points
- Latency+17.0
- Availability+9.3
- Head freshness+0.7
- Correctness+0.6
The parts add to +27.6, exactly — the score is a weighted sum, so it comes apart.