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:54:05 UTC
| Metric | Tenderly | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 78.5 | 50.4 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 22.86% |
| p50 latency | 18.1 ms | 105.0 ms | 12.3 ms |
| p95 latency | 31.5 ms | 119.3 ms | 75.9 ms |
| p99 latency | 55.4 ms | 132.4 ms | 287.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.44 blocks | no cohort |
| Rate limited | 0 | 10 | 0 |
| Unsupported | 0 | 0 | 46 |
| Samples | 1,594 | 1,591 | 1,588 |
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.
TenderlyvsBlast API
+20.9points
- Latency+20.9
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+49.0points
- Availability+29.8
- Latency+11.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +49.0, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.