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 · 3.2 days observed · generated 2026-08-28 01:29:26 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 97.5 | 84.5 | 78.3 | 61.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.98% | 99.98% | 83.57% |
| p50 latency | 19.7 ms | 105.2 ms | 106.9 ms | 265.3 ms |
| p95 latency | 45.7 ms | 122.6 ms | 194.9 ms | 4975.4 ms |
| p99 latency | 679.1 ms | 148.1 ms | 243.7 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.38% |
| Head lag | 0.50 blocks | 0.42 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 0 | 1,262 | 19,991 | 21,347 |
| Unsupported | 0 | 0 | 242 | 0 |
| Samples | 124,488 | 123,909 | 28,927 | 26,220 |
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
+13.0points
- Latency+13.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+19.2points
- Latency+19.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +19.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+35.7points
- Latency+28.1
- Availability+6.6
- Correctness+0.5
- Head freshness+0.5
The parts add to +35.7, exactly — the score is a weighted sum, so it comes apart.