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 · 3.5 days observed · generated 2026-08-28 08:00:46 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 4 | 5 | 6 |
| Score | 98.0 | 87.0 | 84.3 | 78.2 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.97% | 99.84% | 99.98% | 99.99% |
| p50 latency | 19.6 ms | 87.4 ms | 105.1 ms | 106.7 ms |
| p95 latency | 42.8 ms | 100.1 ms | 122.2 ms | 195.0 ms |
| p99 latency | 631.5 ms | 129.0 ms | 147.4 ms | 244.6 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.34 blocks | 0.42 blocks | 0.49 blocks |
| Rate limited | 0 | 0 | 1,372 | 21,722 |
| Unsupported | 0 | 0 | 0 | 267 |
| Samples | 135,055 | 132,753 | 134,477 | 31,403 |
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.
TenderlyvsNodeReal
+11.0points
- Latency+11.1
- Head freshness−0.2
- Availability+0.1
- Correctness+0.0
The parts add to +11.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+13.6points
- Latency+13.7
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +13.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+19.8points
- Latency+19.8
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +19.8, exactly — the score is a weighted sum, so it comes apart.