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 22:18:21 UTC
| Metric | Tenderly | PublicNode | NodeReal |
|---|---|---|---|
| Rank | 1 | 2 | 4 |
| Score | 99.4 | 98.8 | 81.4 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 18.0 ms | 20.2 ms | 86.9 ms |
| p95 latency | 31.5 ms | 33.2 ms | 99.3 ms |
| p99 latency | 64.0 ms | 62.7 ms | 120.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.50 blocks | 0.33 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,606 | 1,607 | 1,563 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsPublicNode
+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.
TenderlyvsNodeReal
+18.0points
- Latency+18.2
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +18.0, exactly — the score is a weighted sum, so it comes apart.