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-27 17:25:18 UTC
| Metric | PublicNode | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 98.2 | 83.9 | 78.0 | 57.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.99% | 100.00% | 73.97% |
| p50 latency | 20.3 ms | 106.1 ms | 107.2 ms | 2024.4 ms |
| p95 latency | 39.9 ms | 122.6 ms | 193.0 ms | 6590.4 ms |
| p99 latency | 96.0 ms | 149.8 ms | 235.0 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.51 blocks | 0.95 blocks |
| Rate limited | 0 | 323 | 5,978 | 6,511 |
| Unsupported | 0 | 0 | 74 | 0 |
| Samples | 38,270 | 37,785 | 8,634 | 7,819 |
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
+14.3points
- Latency+14.4
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +14.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.2points
- Latency+20.2
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+40.4points
- Latency+28.8
- Availability+10.4
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.4, exactly — the score is a weighted sum, so it comes apart.