Skip to content

Providers

CloudflarePoor

Cloudflare's public Ethereum gateway. Serves core methods but does not implement the full JSON-RPC surface.

public · rank 11 of 12

Website (opens in a new tab)Documentation (opens in a new tab)

Measured performance

6h window · 6.0 hours observed · 1 chain

Composite score

46.2

Rank 11 of 12

8,705 samples

Availability

23.10%

Rate limits and unsupported methods excluded

Latency p95

113.6ms

p50 18.8 · p99 143.2

Correctness

100.00%

1,869 responses judged

8 of 8355 requests were rate limited; excluded from availability

12 providers scored against each other.

Score breakdown

How the composite score is composed
ComponentWeightMeasuredScore
Availability40%23.10 %23.1
Latency30%113.56 ms41.1
Correctness20%100.00 %100.0
Head freshness0%not applicable—

Outcome breakdown

Failures are classified rather than collapsed into one count. Our own failures are shown for transparency but are never counted against the provider.

Request outcomes and how each is treated
OutcomeCountShare
Successful1,86921.47%
Provider failure6,48574.50%
Network failure10.01%
Rate limited80.09%
Unsupported method2572.95%
Agent error00.00%
Measurement error3504.02%

What it says it permits

The only figures on this site that are not measurements. A limit is a claim the operator makes, so it is quoted with the page it came from and the day it was read — never inferred from a refused request, which would put a number against a company that never stated it.

Cloudflare does not publish a numeric limit that could be found in its own documentation. Several public endpoints state only that a request may be refused — which is worth knowing before depending on one, and is why this says so rather than showing nothing.

What it promises about staying up

The status page judges every provider against an objective this site publishes. That is not an SLA, and a provider that misses it has not broken a promise — so what it actually promised, where it promised anything, belongs here in its own words. The objective

Cloudflare does not publish an availability commitment that could be found in its own documentation. That is the common case for a public endpoint and is worth knowing before depending on one: the availability figures on this site are measurements against a bar this platform set, not against anything Cloudflare agreed to.

Reliability record

An availability percentage has no shape. This is the shape: what departed from this provider’s own normal behaviour, and what its normal behaviour already is. How an incident is decided

Departures from normal · last 30 days

  • Throttledeth_estimateGason Ethereum2026-10-08 00:2810m
  • Throttledeth_syncingon Ethereum2026-10-08 00:2515m
  • Throttledeth_estimateGason Ethereum2026-10-07 23:3626m
  • Throttledeth_chainIdon Ethereum2026-10-07 23:3232m
  • Throttledeth_syncingon Ethereum2026-10-07 22:2545m
  • Throttledeth_estimateGason Ethereum2026-10-07 22:0279m
  • Throttledeth_chainIdon Ethereum2026-10-07 21:5517m

Persistent conditions

Calls that fail, or are refused, at about the same rate every day. These are not events — they are what this provider does — and none of them will be different tomorrow.

  • Outageeth_blockNumberon Ethereumsucceeds 0.0%
  • Outageeth_blockNumberon Ethereumsucceeds 0.0%
  • Outageeth_blockNumberon Ethereumsucceeds 0.0%
  • Outageeth_callon Ethereumsucceeds 0.0%2% refused
  • Outageeth_gasPriceon Ethereumsucceeds 0.0%
  • Outageeth_callon Ethereumsucceeds 0.0%
  • Outageeth_gasPriceon Ethereumsucceeds 0.0%
  • Outageeth_getBalanceon Ethereumsucceeds 0.0%
  • Outageeth_getBlockByNumberon Ethereumsucceeds 0.0%
  • Outageeth_getBlockByNumberon Ethereumsucceeds 0.0%
  • Outageeth_callon Ethereumsucceeds 0.0%
  • Outageeth_gasPriceon Ethereumsucceeds 0.0%
  • Outageeth_getBalanceon Ethereumsucceeds 0.0%
  • Outageeth_getBalanceon Ethereumsucceeds 0.0%
  • Outageeth_callon Ethereumsucceeds 0.0%
  • Outageeth_feeHistoryon Ethereumsucceeds 0.0%
  • Outageeth_getTransactionCounton Ethereumsucceeds 0.0%
  • Outageeth_getTransactionCounton Ethereumsucceeds 0.0%
  • Outageeth_feeHistoryon Ethereumsucceeds 0.0%
  • Outageeth_feeHistoryon Ethereumsucceeds 0.0%
  • Outageeth_getTransactionCounton Ethereumsucceeds 0.0%6% refused
  • Outageeth_blockNumberon Ethereumsucceeds 0.0%1% refused
  • Outageeth_gasPriceon Ethereumsucceeds 0.0%3% refused
  • Outageeth_feeHistoryon Ethereumsucceeds 0.0%5% refused
  • Outageeth_getBlockByNumberon Ethereumsucceeds 0.0%2% refused
  • Outageeth_getBalanceon Ethereumsucceeds 0.0%2% refused
  • Outageeth_getBlockByNumberon Ethereumsucceeds 0.0%
  • Throttledeth_maxPriorityFeePerGason Ethereumnever answered100% refused

From each region

The same measurements, grouped by the vantage point they were taken from. Latency is a property of a network path, so a provider fast from one region is not necessarily fast from another — and the composite score above is an average across whichever regions are reporting.

4 regions

Cloudflare broken out by region
RegionMedianp95SuccessSamples
Coventry28.6 ms111 ms21.6%2,185
Frankfurt17.2 ms101 ms21.5%2,156
Amsterdam17.1 ms65.8 ms21.4%2,189
Virginia15.4 ms134 ms21.4%2,175

Percentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.

Endpoints under measurement

1 endpoint

Endpoints measured for this provider
ChainTransportURLStatus
Ethereumhttp_jsonrpchttps://cloudflare-eth.com

Embed this

A live badge for Cloudflare on Ethereum, free to use. It renders from the current measurement each time it loads, so it cannot be frozen at a good day — which is what makes it worth putting in a README. Every badge and parameter

Cloudflare score badgescore

The composite score, coloured by band.

Markdown

[![Cloudflare on RPCNode.IO](https://rpcnode.io/badge/provider/cloudflare.svg?chain=ethereum)](https://rpcnode.io/providers/cloudflare)

HTML

<a href="https://rpcnode.io/providers/cloudflare"><img src="https://rpcnode.io/badge/provider/cloudflare.svg?chain=ethereum" alt="Cloudflare on RPCNode.IO"></a>