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
30d window · 4.1 days observed · generated 2026-08-28 22:17:18 UTC
| Metric | Tenderly | Blast API | 1RPC |
|---|---|---|---|
| Rank | 2 | 5 | 8 |
| Score | 98.6 | 84.1 | 61.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.98% | 83.08% |
| p50 latency | 19.6 ms | 105.2 ms | 265.3 ms |
| p95 latency | 39.7 ms | 122.5 ms | 4975.4 ms |
| p99 latency | 544.9 ms | 146.6 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 97.38% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 1,551 | 27,160 |
| Unsupported | 0 | 0 | 0 |
| Samples | 158,223 | 157,615 | 32,880 |
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
+14.4points
- Latency+14.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +14.4, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+36.9points
- Latency+29.2
- Availability+6.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.9, exactly — the score is a weighted sum, so it comes apart.