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.4 days observed · generated 2026-08-28 05:30:28 UTC
| Metric | Tenderly | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 5 | 8 |
| Score | 97.8 | 87.1 | 84.4 | 61.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.83% | 99.98% | 83.57% |
| p50 latency | 19.7 ms | 87.4 ms | 105.1 ms | 265.3 ms |
| p95 latency | 43.7 ms | 99.8 ms | 122.3 ms | 4975.4 ms |
| p99 latency | 647.7 ms | 124.6 ms | 147.6 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.38% |
| Head lag | 0.50 blocks | 0.34 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 0 | 1,279 | 22,469 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 131,003 | 128,767 | 130,414 | 27,501 |
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.7points
- Latency+10.8
- Head freshness−0.2
- Availability+0.1
- Correctness+0.0
The parts add to +10.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+13.4points
- Latency+13.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+36.0points
- Latency+28.4
- Availability+6.6
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.0, exactly — the score is a weighted sum, so it comes apart.