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 · 48 hours observed · generated 2026-08-26 20:16:40 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 89.0 | 85.6 | 78.4 | 63.9 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.97% | 88.60% |
| p50 latency | 20.0 ms | 104.6 ms | 106.7 ms | 189.3 ms |
| p95 latency | 97.4 ms | 122.5 ms | 196.6 ms | 2922.0 ms |
| p99 latency | 934.9 ms | 144.5 ms | 243.2 ms | 6561.8 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.72% |
| Head lag | 0.51 blocks | 0.42 blocks | 0.46 blocks | 0.90 blocks |
| Rate limited | 0 | 915 | 12,468 | 13,260 |
| Unsupported | 0 | 0 | 152 | 0 |
| Samples | 77,184 | 76,655 | 17,961 | 16,237 |
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
+3.4points
- Latency+3.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +3.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+10.6points
- Latency+10.7
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +10.6, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+25.0points
- Latency+19.6
- Availability+4.5
- Correctness+0.5
- Head freshness+0.4
The parts add to +25.0, exactly — the score is a weighted sum, so it comes apart.