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
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 17:30:58 UTC
| Metric | Tenderly | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 2 | 5 |
| Score | 99.4 | 98.6 | 83.5 |
| Status | Excellent | Excellent | Good |
| Availability | 99.99% | 99.98% | 99.97% |
| p50 latency | 18.8 ms | 21.0 ms | 105.4 ms |
| p95 latency | 32.4 ms | 36.1 ms | 121.9 ms |
| p99 latency | 60.3 ms | 75.9 ms | 145.0 ms |
| Correctness | 99.99% | 99.98% | 99.99% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 353 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,131 | 38,456 | 38,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.8points
- Latency+0.8
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.9points
- Latency+16.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.9, exactly — the score is a weighted sum, so it comes apart.