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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 19:58:09 UTC
| Metric | PublicNode | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 7 |
| Score | 94.5 | 78.3 | 70.9 | 69.5 |
| Status | Excellent | Good | Degraded | Degraded |
| Availability | 100.00% | 99.92% | 100.00% | 99.96% |
| p50 latency | 25.5 ms | 109.1 ms | 110.3 ms | 125.2 ms |
| p95 latency | 52.3 ms | 128.0 ms | 191.2 ms | 217.5 ms |
| p99 latency | 112.1 ms | 154.8 ms | 236.0 ms | 241.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.41 blocks | 0.56 blocks | 0.40 blocks |
| Rate limited | 0 | 72 | 1,497 | 0 |
| Unsupported | 0 | 0 | 22 | 0 |
| Samples | 9,756 | 9,658 | 2,231 | 9,651 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsBlast API
+16.2points
- Latency+16.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +16.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+23.6points
- Latency+23.5
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +23.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+25.0points
- Latency+25.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +25.0, exactly — the score is a weighted sum, so it comes apart.