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
30d window · 2.7 days observed · generated 2026-08-27 12:58:04 UTC
| Metric | PublicNode | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 4 | 5 | 6 |
| Score | 99.4 | 87.8 | 85.1 | 78.5 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.97% | 99.82% | 99.98% | 99.98% |
| p50 latency | 18.7 ms | 87.4 ms | 104.8 ms | 106.5 ms |
| p95 latency | 34.1 ms | 100.0 ms | 122.2 ms | 196.3 ms |
| p99 latency | 72.4 ms | 125.8 ms | 146.2 ms | 243.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 0 | 1,154 | 16,761 |
| Unsupported | 0 | 0 | 0 | 203 |
| Samples | 104,987 | 102,429 | 103,621 | 24,149 |
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.
PublicNodevsNodeReal
+11.6points
- Latency+11.7
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +11.6, exactly — the score is a weighted sum, so it comes apart.
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.9points
- Latency+20.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.