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
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 10:05:34 UTC
| Metric | Tenderly | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 78.2 | 50.2 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.99% | 23.11% |
| p50 latency | 19.1 ms | 105.6 ms | 13.9 ms |
| p95 latency | 34.1 ms | 121.9 ms | 79.4 ms |
| p99 latency | 138.8 ms | 150.6 ms | 116.5 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.41 blocks | no cohort |
| Rate limited | 0 | 131 | 19 |
| Unsupported | 0 | 0 | 243 |
| Samples | 8,235 | 8,232 | 8,265 |
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
+21.1points
- Latency+21.3
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+49.2points
- Availability+29.7
- Latency+12.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +49.2, 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.