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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 05:27:30 UTC
| Metric | PublicNode | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 8 |
| Score | 99.4 | 83.8 | 77.5 | 60.2 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.94% | 99.99% | 100.00% | 79.89% |
| p50 latency | 18.7 ms | 103.7 ms | 104.3 ms | 1317.0 ms |
| p95 latency | 29.8 ms | 117.2 ms | 198.1 ms | 7406.7 ms |
| p99 latency | 55.4 ms | 143.0 ms | 274.4 ms | 9776.0 ms |
| Correctness | 99.96% | 99.99% | 100.00% | 96.95% |
| Head lag | 0.49 blocks | 0.40 blocks | 0.56 blocks | 0.94 blocks |
| Rate limited | 0 | 42 | 1,407 | 1,488 |
| Unsupported | 0 | 0 | 17 | 0 |
| Samples | 8,916 | 8,851 | 2,037 | 2,052 |
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.6points
- Latency+15.7
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.9points
- Latency+21.8
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+39.1points
- Latency+30.0
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +39.1, exactly — the score is a weighted sum, so it comes apart.