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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 08:34:16 UTC
| Metric | PublicNode | Tenderly | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 4 | 6 |
| Score | 99.4 | 98.8 | 80.0 | 70.0 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.99% | 99.98% | 100.00% | 100.00% |
| p50 latency | 18.3 ms | 18.4 ms | 87.7 ms | 104.7 ms |
| p95 latency | 30.3 ms | 32.2 ms | 105.1 ms | 192.8 ms |
| p99 latency | 61.5 ms | 82.6 ms | 139.8 ms | 251.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.36 blocks | 0.62 blocks |
| Rate limited | 0 | 0 | 0 | 1,415 |
| Unsupported | 0 | 0 | 0 | 15 |
| Samples | 9,090 | 9,012 | 8,891 | 2,023 |
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.6points
- Latency+0.6
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+19.4points
- Latency+19.5
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +19.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+29.4points
- Latency+29.2
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +29.4, exactly — the score is a weighted sum, so it comes apart.