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-27 05:45:25 UTC
| Metric | PublicNode | Tenderly | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 5 | 6 |
| Score | 99.4 | 99.4 | 84.0 | 77.7 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.99% | 100.00% | 99.99% | 100.00% |
| p50 latency | 17.5 ms | 18.8 ms | 103.1 ms | 104.7 ms |
| p95 latency | 32.1 ms | 32.3 ms | 115.5 ms | 193.2 ms |
| p99 latency | 60.3 ms | 65.1 ms | 142.4 ms | 251.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.48 blocks | 0.42 blocks | 0.54 blocks |
| Rate limited | 0 | 0 | 78 | 1,475 |
| Unsupported | 0 | 0 | 0 | 20 |
| Samples | 9,408 | 9,314 | 9,324 | 2,089 |
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.
PublicNodevsTenderly
+0.0points
- Latency+0.1
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +0.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+15.4points
- Latency+15.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.7points
- Latency+21.7
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +21.7, exactly — the score is a weighted sum, so it comes apart.