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 · 2.2 days observed · generated 2026-08-27 01:18:14 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 6 |
| Score | 93.3 | 89.1 | 86.1 | 79.1 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.96% | 99.78% | 99.98% | 99.98% |
| p50 latency | 19.9 ms | 87.4 ms | 104.6 ms | 106.6 ms |
| p95 latency | 74.4 ms | 99.9 ms | 122.3 ms | 195.9 ms |
| p99 latency | 883.9 ms | 123.7 ms | 144.3 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.51 blocks | 0.35 blocks | 0.42 blocks | 0.47 blocks |
| Rate limited | 0 | 0 | 967 | 13,748 |
| Unsupported | 0 | 0 | 0 | 167 |
| Samples | 85,298 | 83,826 | 84,734 | 19,786 |
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
+4.2points
- Latency+4.3
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +4.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+7.2points
- Latency+7.3
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+14.2points
- Latency+14.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.