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 | Tenderly | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 2 | 5 |
| Score | 99.4 | 98.8 | 78.2 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.98% | 99.97% |
| p50 latency | 19.3 ms | 21.2 ms | 106.3 ms |
| p95 latency | 32.9 ms | 34.8 ms | 121.7 ms |
| p99 latency | 62.5 ms | 69.6 ms | 133.9 ms |
| Correctness | 99.98% | 99.98% | 99.98% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 175 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,104 | 9,184 | 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 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.
TenderlyvsBlast API
+21.2points
- Latency+21.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.