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
7d window · 2.2 days observed · generated 2026-08-27 01:02:02 UTC
| Metric | Tenderly | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 93.1 | 86.1 | 56.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.96% | 99.98% | 23.10% |
| p50 latency | 19.9 ms | 104.6 ms | 15.4 ms |
| p95 latency | 75.4 ms | 122.3 ms | 89.6 ms |
| p99 latency | 886.8 ms | 144.4 ms | 254.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.51 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 967 | 77 |
| Unsupported | 0 | 0 | 2,495 |
| Samples | 84,858 | 84,292 | 84,664 |
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
+7.0points
- Latency+7.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+37.1points
- Availability+29.7
- Head freshness*+9.4
- Correctness−2.2
- Latency+0.2
The parts add to +37.1, 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.