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
- NodeReal
- dRPC
- Blast API
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 13:37:15 UTC
| Metric | PublicNode | NodeReal | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 98.8 | 81.6 | 78.2 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.99% | 99.97% |
| p50 latency | 21.2 ms | 87.3 ms | 106.3 ms |
| p95 latency | 34.8 ms | 99.5 ms | 121.7 ms |
| p99 latency | 69.6 ms | 125.8 ms | 133.9 ms |
| Correctness | 99.98% | 99.99% | 99.98% |
| Head lag | 0.49 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 175 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,184 | 8,964 | 9,110 |
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
+17.2points
- Latency+17.4
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +17.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+20.6points
- Latency+20.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +20.6, exactly — the score is a weighted sum, so it comes apart.