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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 12:26:28 UTC
| Metric | PublicNode | dRPC | NodeReal |
|---|---|---|---|
| Rank | 2 | 3 | 4 |
| Score | 98.4 | 88.0 | 82.2 |
| Status | Excellent | Good | Good |
| Availability | 99.88% | 100.00% | 99.94% |
| p50 latency | 21.3 ms | 34.4 ms | 87.5 ms |
| p95 latency | 35.7 ms | 69.7 ms | 100.1 ms |
| p99 latency | 68.3 ms | 167.7 ms | 176.2 ms |
| Correctness | 99.88% | 100.00% | 99.94% |
| Head lag | 0.54 blocks | 0.38 blocks | 0.33 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,616 | 1,575 | 1,575 |
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.
PublicNodevsdRPC
+10.4points
- Latency+10.7
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +10.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+16.2points
- Latency+16.5
- Head freshness−0.3
- Availability−0.0
- Correctness−0.0
The parts add to +16.2, exactly — the score is a weighted sum, so it comes apart.