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.2 days observed · generated 2026-08-28 01:08:13 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 4 | 5 | 6 |
| Score | 97.5 | 87.3 | 84.5 | 78.3 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.97% | 99.85% | 99.98% | 99.98% |
| p50 latency | 19.7 ms | 87.4 ms | 105.2 ms | 106.9 ms |
| p95 latency | 45.9 ms | 99.9 ms | 122.7 ms | 194.8 ms |
| p99 latency | 681.4 ms | 125.0 ms | 148.2 ms | 243.3 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,256 | 19,907 |
| Unsupported | 0 | 0 | 0 | 241 |
| Samples | 123,922 | 121,812 | 123,326 | 28,791 |
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
+10.2points
- Latency+10.3
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.
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.