Tenderly Gateway leads on 1 of 3 shared benchmarks, Thyme Gate on 2. Tenderly Gateway wins on Optimism RPC endpoints (101 ms vs 111 ms). Thyme Gate wins on Ethereum RPC endpoints (83 ms vs 105 ms), Polygon RPC endpoints (93 ms vs 95 ms). Data as of 2026-11-11 UTC.
Tenderly's public gateway exposes a no-key JSON-RPC endpoint per chain at `gateway.tenderly.co/public/<slug>`. Covers Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, Linea, Scroll and Mantle. The same Tenderly platform behind the keyed Web3 dev suite.
Thyme Labs operates keyless public RPC on its own nodes with a 22-unit/s per-IP limit (one unit per call; eth_getLogs and eth_getBlockReceipts cost four), batches of up to 10 calls and no paid-provider fallback.
Tenderly Gateway
Trails105 ms
Thyme Gate
Leads83 ms
Per region
| Region | Tenderly Gateway | Thyme Gate |
|---|---|---|
| US-East | 28 ms | 85 ms |
| EU-West | 32 ms | 8 ms |
| Singapore | 254 ms | 157 ms |
Tenderly Gateway
Leads101 ms
Thyme Gate
Trails111 ms
Per region
| Region | Tenderly Gateway | Thyme Gate |
|---|---|---|
| US-East | 26 ms | 112 ms |
| EU-West | 29 ms | 37 ms |
| Singapore | 249 ms | 184 ms |
Tenderly Gateway
Trails95 ms
Thyme Gate
Leads93 ms
Per region
| Region | Tenderly Gateway | Thyme Gate |
|---|---|---|
| US-East | 13 ms | 94 ms |
| EU-West | 29 ms | 17 ms |
| Singapore | 244 ms | 167 ms |
Tenderly Gateway and Thyme Gate are compared on 3 shared OpenChainBench benchmarks. Tenderly Gateway leads on Optimism RPC endpoints. Thyme Gate leads on Ethereum RPC endpoints. See the live table on this page for every metric.
On the Optimism RPC endpoints benchmark, Tenderly Gateway leads at 101 ms versus Thyme Gate at 111 ms. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing; panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.