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 16:07:31 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 2 | 5 | 6 |
| Score | 98.5 | 83.5 | 77.4 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.97% | 100.00% |
| p50 latency | 21.2 ms | 105.5 ms | 107.4 ms |
| p95 latency | 36.6 ms | 121.8 ms | 196.1 ms |
| p99 latency | 77.5 ms | 145.6 ms | 265.9 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.41 blocks | 0.53 blocks |
| Rate limited | 0 | 352 | 6,027 |
| Unsupported | 0 | 0 | 70 |
| Samples | 37,816 | 37,469 | 8,736 |
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
+15.0points
- Latency+15.1
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.1points
- Latency+21.0
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.