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 · 47 hours observed · generated 2026-08-26 19:12:50 UTC
| Metric | Tenderly | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 88.0 | 85.5 | 64.0 |
| Status | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 88.84% |
| p50 latency | 20.0 ms | 104.5 ms | 189.3 ms |
| p95 latency | 103.1 ms | 122.5 ms | 2922.0 ms |
| p99 latency | 948.4 ms | 144.7 ms | 6561.8 ms |
| Correctness | 99.99% | 99.98% | 97.72% |
| Head lag | 0.51 blocks | 0.42 blocks | 0.90 blocks |
| Rate limited | 0 | 870 | 12,966 |
| Unsupported | 0 | 0 | 0 |
| Samples | 75,459 | 75,013 | 15,898 |
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
+2.5points
- Latency+2.6
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +2.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+24.0points
- Latency+18.7
- Availability+4.4
- Correctness+0.5
- Head freshness+0.4
The parts add to +24.0, exactly — the score is a weighted sum, so it comes apart.