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-28 00:12:23 UTC
| Metric | PublicNode | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 9 |
| Score | 97.8 | 83.6 | 78.1 | 51.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.96% | 100.00% | 56.10% |
| p50 latency | 21.2 ms | 105.7 ms | 106.8 ms | 3241.1 ms |
| p95 latency | 39.9 ms | 122.9 ms | 188.6 ms | 9140.1 ms |
| p99 latency | 93.6 ms | 150.7 ms | 230.5 ms | 12423.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.52 blocks | 0.92 blocks |
| Rate limited | 0 | 19 | 1,387 | 1,400 |
| Unsupported | 0 | 0 | 16 | 0 |
| Samples | 8,516 | 8,424 | 2,036 | 1,688 |
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.2points
- Latency+14.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+19.7points
- Latency+19.6
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +19.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+46.4points
- Latency+28.3
- Availability+17.6
- Head freshness+0.5
- Correctness+0.0
The parts add to +46.4, exactly — the score is a weighted sum, so it comes apart.