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.1 days observed · generated 2026-08-27 23:00:33 UTC
| Metric | Tenderly | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 5 | 8 |
| Score | 97.3 | 87.4 | 84.6 | 62.2 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.84% | 99.98% | 84.43% |
| p50 latency | 19.8 ms | 87.4 ms | 105.2 ms | 225.7 ms |
| p95 latency | 47.0 ms | 100.0 ms | 122.7 ms | 4391.3 ms |
| p99 latency | 698.4 ms | 125.6 ms | 148.2 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.48% |
| Head lag | 0.50 blocks | 0.34 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 0 | 1,237 | 20,693 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 120,466 | 118,434 | 119,882 | 25,121 |
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.0points
- Latency+10.1
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +10.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+12.8points
- Latency+12.9
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +12.8, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+35.2points
- Latency+28.0
- Availability+6.2
- Correctness+0.5
- Head freshness+0.5
The parts add to +35.2, exactly — the score is a weighted sum, so it comes apart.