Provider at a glance
- Category
- RPC & Node Services
- Entity
- Not verified
- Official website
- drpc.org
Independent rankingchecked How it works
Details
Scored 78 out of 100 under methodology 2026.10.18, from the evidence read in October 2026.
dRPC
Routed multi-provider RPC
RPC & Node Services
#2 Overall
Ranked #2 of 9 RPC & node services in the published ranking
78
ChainChoice Score
The ChainChoice Score, shown against 100: published scores run from 41 to 99.- High evidence confidence
- $720 your cost/yr
Is dRPC right for you?
Right for you if these matter most
- Documented incident record and chain coverage7/10, the category best
- Archive debug and trace access6/10; the category best is 7
- Published throughput and self-serve ceiling8/10; the category best is 9
Look elsewhere if these come first
- Real cost per 1M identical calls8/10 here; BlockPI scores 10
Not yet tested for your country. Markets it lists: Global.
to test where you can use it.
The rank above is the published one, the same for every reader. Find my best RPC provider shows where it lands for you.
What will dRPC cost you?
$720 your cost/yr
- Usage per month
- 10
- Price per unit
- $6
- Plan fee
- $0
$389 above the median of 8 priced RPC & node services.
How this is calculatedHow safe is dRPC?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read October 2026.
- LicenceMiCA (EU): no register record on file here.
Alternatives to dRPC
Compare all 4- 1BlockPI3 points above · stronger on real cost per million calls (10 against 8)81$1.20
- 3ChainstackLevel on score · stronger on real cost per million calls (9 against 8)78$2,400
- 4Helius12 points below · weaker on reliability and coverage (4 against 7)66$600
For your setup
Find out if dRPC fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where dRPC lands for you, which criteria your answers weight up, and which stated needs the record does or does not meet. The published rank stays beside it.
- A few questions
- No account required
- Ranking-blind: no commercial input
- Personalised in under 60 seconds
Find my best RPC providerNothing is inferred from clicks, popularity or commercial value.
Why this rank
Why dRPC ranks #2
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (23.5 here) sit inside the score; availability, friction, trust record and measured data add the rest. Best in this ranking on 1 of 4.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
358+8.966.010#3/9Loading evidence…
206+3.845.07#2/9Loading evidence…
208+5.126.09#2/9Loading evidence…
257+5.605.07#1/9Loading evidence…
Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin−3behind BlockPI, #1
RobustnessOne point from changingacross a one-point change to each of its 4 criterion scores, the re-run scores 76–81 and ranks #2–#3
Evidence4 of 4 scored4 quoted, 4 with a source link
What would move the rank
Each line is the ranking run again with one of dRPC’s criterion scores changed and every other value held: the smallest whole-point change on that criterion that moves its rank, and where the re-run puts it. Up to 4 climbs and 3 falls are listed, smallest change first. Nothing here is a forecast.
Real cost per 1M identical calls 8 → 10 on its ladder · passes BlockPI+281#2 → #1
Documented incident record and chain coverage 7 → 9 on its ladder · passes BlockPI+281#2 → #1
Archive debug and trace access 6 → 9 on its ladder · passes BlockPI+381#2 → #1
Real cost per 1M identical calls 8 → 7 on its ladder · Chainstack passes it−176#2 → #3
Archive debug and trace access 6 → 5 on its ladder · Chainstack passes it−177#2 → #3
Published throughput and self-serve ceiling 8 → 7 on its ladder · Chainstack passes it−177#2 → #3
Smallest climb: real cost per 1M identical calls 8 → 10 passes BlockPI, #1.
Strengths
3 from the score dataWhere it leads
Best for readers who weight
- Documented incident record and chain coverage — 7/10, the category best
- Archive debug and trace access — 6/10, category best 7/10
- Published throughput and self-serve ceiling — 8/10, category best 9/10
Tradeoffs
1 from the score dataWhere it trails
Not for readers who put first
- Real cost per 1M identical calls — 8/10 against a category best of 10/10
Record watch-outs
- The flat 20 CU is a repricing, not a principle. Before 2 June 2025 dRPC charged 10 CU for eth_blockNumber and 60 CU for eth_getLogs; flattening to 20 CU doubled the cost of the cheapest, highest-frequency method on the same day the announcement was titled 'simple, transparent, fair'. If your traffic skews to light polling calls you got a price rise.
- The live Dwellir page states Alchemy $11.70, QuickNode $12.25, Infura $8.89, Chainstack $2.45, dRPC $5.98, Ankr $20.00. Only Ankr matches. (The conflict-of-interest framing IS confirmed — the page is published by Dwellir, an RPC provider, and its conclusion recommends Dwellir itself.) Either restate the correct numbers or drop the figures and keep only the conflict-of-interest note.
- SOURCING ERROR, not a factual one. The flat-pricing blog post states '20 CU per request – any method, any chain', '$6 per 1,000,000 requests' and 'Starting June 2, 2025' — all confirmed — but it does NOT state '$0.30 per 1M CU' (the compute-units docs page carries that: 'The cost is $0.30 for 1M CU.') and it does NOT contain the free-plan paragraph. The free-plan facts are all independently confirmed but originate from a different dRPC post effective 1 June 2025. Split the citation across the three dRPC pages.
Competitive position
Where dRPC leads and where it trails
Rank on every objective dimension among the rows scored on it. A criterion in the top third of its pool is listed as a lead, the bottom third as a trail; the middle is neither. Popularity, size and commercial terms are not dimensions.
Availability#1 / 914.0 of 20 · constant here
Published criteria#2 / 917.6 of 30 · best 18.6
Friction#1 / 92.7 of 10 · constant here
Trust record#1 / 93.2 of 8 · constant here
Measured data#1 / 98.3 of 18 · constant here
Where dRPC leads
- Real cost per 1M identical calls#3 / 9
- Archive debug and trace access#2 / 9
- Published throughput and self-serve ceiling#2 / 9
- Documented incident record and chain coverage#1 / 9
Where it trailsNo criterion in the bottom third of its pool.
Closest alternatives
The 3 nearest rows by score
Nearest by published score in either direction. Each card states the criteria on which the two rows differ and the cost difference under the same scenario inputs; the compare arithmetic below shows why the higher one ranks higher.
Chainstack#3 of 9 · score 78 · same score
dRPC leads on
- Archive debug and trace access6 vs 5
- Documented incident record and chain coverage7 vs 6
Chainstack leads on
- Real cost per 1M identical calls9 vs 8
Largest single reason dRPC is ahead: published criteria (+0.5 display points).Scenario cost: Chainstack is +$1,680 against dRPC.
BlockPI#1 of 9 · score 81 · 3.0 points ahead
dRPC leads on
- Documented incident record and chain coverage7 vs 5
BlockPI leads on
- Real cost per 1M identical calls10 vs 8
- Published throughput and self-serve ceiling9 vs 8
Largest single reason BlockPI is ahead: published criteria (+2.6 display points).Scenario cost: BlockPI is −$719 against dRPC.
Helius#4 of 9 · score 66 · 12.0 points behind
dRPC leads on
- Archive debug and trace access6 vs 3
- Published throughput and self-serve ceiling8 vs 5
- Documented incident record and chain coverage7 vs 4
Helius leads onNo scored criterion
Largest single reason dRPC is ahead: published criteria (+12.0 display points).Scenario cost: Helius is −$120 against dRPC.
Against the leader
81 vs 78 · gap 3.0Why BlockPI ranks above dRPC
The compare workspace's arithmetic applied to these two rows. Each dimension's share of the gap is its weight × the difference, on the displayed scale — it reproduces the displayed gap of 3.0 to within rounding.
DimensionThisBlockPIGap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight17.618.6−2.6, worse
Friction · 12% weight · constant here2.72.7same
Trust record · 9% weight · constant here3.23.2same
Measured data · 21% weight · constant here8.38.3same
Published criterionThisBlockPIPoints
Real cost per 1M identical calls · w35810−2.24, worse
Published throughput and self-serve ceiling · w2089−0.64, worse
Documented incident record and chain coverage · w2575+1.60, better
Net7881−3.0
Your scenario
What dRPC costs on your scenario
Metered usage beyond whatever the plan includes, for a year. Excludes egress, support tiers and enterprise minimums. Change an input and every figure recomputes from the published rate; the published rank does not move.
your cost/yr · default scenario — set your own
Usage per month · your input10
Price per unit · published rate$6
Plan fee · published rate$0
Rate read from the provider’s published pricing ↗ on 22 October 2026.
your cost/yrCost is stated as your cost/yr in USD; it is never a yield, never annualised, and it does not enter the score.
$720
Under the default inputs · USDCategory median$3328 of 9 rows priced · dRPC +$389 vs median
Cheapest priced$0.00 · Infura (Consensys)dRPC costs +$720 more · availability not applied — set your country to filterCompare with Infura (Consensys)
1 of 9 rows in this ranking have no verified rate for this scenario and are absent from the median, not counted as free.
Evidence
Evidence read 22 October 2026
One row per published criterion: the page each strength was read from, its source type by domain, the reading date and whether the file and the published table agree. Open a row for the quote and the receipt.
4 of 4 cells scored
Score evidenceVerified4 of 4 criteria reconstruct from receipts
4 of 4 criteria reconstruct from a quoted, sourced receipt equal to the published strength.Public receiptsReading…4 quoted with a source URL
The receipt file has not been read yet.Evidence confidenceHighcoverage and corroboration, never freshness
4/4 criteria scored, with 4 dated sources quoted.RobustnessOne point from changingrank #2 to #3 across one-point re-runs
Whether the position holds when one criterion score is changed by one point and the ranking is run again. It is always a re-run of the ranking, never an estimate.The newest evidence read on the platform is 3 November 2026; this category's reading is older. The scores stand as read on 22 October 2026.
Reading the evidence ledger…
CriterionSourceTypeReadFreshnessStatusReceipt
Real cost per 1M identical callsstrength 8 · weight 35Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Archive debug and trace accessstrength 6 · weight 20Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Published throughput and self-serve ceilingstrength 8 · weight 20Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Documented incident record and chain coveragestrength 7 · weight 25Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.How you can lose money here, and what the ranking scores
- Liveness failure (dRPC 7/10): the operator stops, censors you or loses data.Scored by Documented incident record and chain coverage · 25%
Not assessed by this ranking: Exit failure, Information failure. A high place says nothing about these; the Methodology tab says what each means. Also scored, as cost, quality or a summary of several families: Real cost per 1M identical calls (35%), Archive debug and trace access (20%), Published throughput and self-serve ceiling (20%).
Facts
facts, not scoresWhat the record publishes
- Pricing
- dRPC pricing page (drpc.org/pricing), read 22 October 2026 for the 21 October 2026 re-read; REPRICED since 14 September 2026 (new plans for accounts created after 19 October 2026). "$0.30/1M CU across Multi-Chain and Solana". Free "$0/mo": "Only Public nodes", "210M CU Pool Included", "Up to ~ 10M Requests", "100 RPS"; Archive Nodes, Debug and Trace API and Websocket marked unavailable. Pro "$49/mo": "163M CU Pool Included", "10M Multi-Chain Req · $4.8/1M Req", "Multi-Chain Overage: $6/1M", "300 RPS". Scale "$199/mo": "664M CU Pool Included", "47M Multi-Chain Req · $4.2/1M Req", "Multi-Chain Overage: $6/1M", "600 RPS". Solana "$3.9/1M Req"; Solana Mainnet gRPC "$60/TB". Enterprise "From $990/mo", unlimited RPS. "Pay as You Go $ 6 /1M Req · 100 RPS Limit · No Commitment" (existing customers keep their terms). Docs: "All RPC methods cost a flat 20 compute units. The cost is $0.30 for 1M CU."; on Pro 16 CU and on Scale 14 CU per Multi-Chain request from the plan pool, 20 CU beyond it. Rate-limit doc: Pay as You Go "100 RPS for accounts created after October 19, 2026"; free tier 210M CU per 30 days from registration, 120,000 CU per minute per IP.dRPC — official pricing page ↗ · 22 October 2026
- Prices published in
- USDdRPC — official pricing page ↗ · 22 October 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- Multi-chain
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- dRPC's Terms of Use (drpc.org/terms-of-use, read 22 October 2026) carry no sanctions or eligibility clause naming a country; the only mention of embargoes is the force-majeure line excusing performance caused by "political embargos". Global self-serve.
No confirmed legal entity is on file for this record. Nothing is inferred from the brand name.
If something goes wrong with dRPC: where to complain, and where to report a scam
Loading the routes for your country.
How this page is reviewed
Reviewed means this product in this category was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
History
What the record carries
Changes to published ranks are recorded in a ledger; every step and its cause is listed on the rank-history page. The entries below begin with the current verified snapshot, then the methodology versions whose changes applied to this category, newest first.
9 methodology entries
- 22 October 2026Current verified snapshot · methodology 2026.10.18Score 78, #2 of 9. 4 of 4 criteria scored. History starts here; earlier values are not interpolated.
- 10 October 2026
2026.10.8When nothing serves your country, the list shown for reference is the published ranking · platform-wide- fixed The reference list shown when nothing serves your country is the published order with the published scores, and a build check now fails any such list out of that order or with a score the ranking does not publish.
- fixed The explorer prints an overall rank only for a row the published ranking holds; a country entrant such as Coinbase Commerce for US merchants shows no overall rank.
- changed Published orders do not move. Country results change only where nothing serves the country: in India bill pay keeps Bitcoin Well first and now shows Strike second, as published; 35 such runs across all categories and countries now match the published list exactly.
- 10 October 2026
2026.10.6A criterion you require re-scores the rows that meet it · platform-wide- changed The explorer sends each criterion you require, at any band, as fit_required with your other answers; region, licence, chain and fact filters stay filters. On /best, a required criterion joins For you as a marked preference does, which needs your country; Overall stays the published ranking, filtered.
- added Every published criterion has a golden case as the explorer sends it (require:<criterion>), so the order a requirement gives is replayed and gated as the published order is, and a change to it needs an entry here.
- 16 September 2026
2026.09.15Dimension scores carry tenths, and eleven more categories are re-read from primary sources · platform-wide- changed Dimension scores resolve to tenths of a point (O-04b), and weightedTotal is rounded to six decimal places before the order is read. 518 published scores move across 107 categories that were not re-read; none of them moves by more than 4 points, and most move by 1.
- fixed 66 published scores change in the eleven re-read categories, against a verbatim source each. The largest moves are Reflexer RAI (−16), Beefy and Unrekt (−11), Aztec (−10) and Golem (+9) — all of them rows whose sources had moved since their last read.
- changed Published order moves in 38 of 119 categories and three #1s change: smart_contract_audits (Zellic → Certora) and travel_rule_compliance (Sumsub Travel Rule → CodeVASP) on the finer resolution, kyc_compliance (Veriff → Sumsub) on the re-read.
- added availabilitySource (O-04g): for a reader who states a country, a row whose availability in that country rests on a region tag its record gives no source for sorts below every sourced row. It is inert in every order published here, which states no country.
Methodology 2026.10.18, the same published run every visitor sees · receipt rpc_nodes:drpc:2026.10.18:a6f69a8367c9
Are you dRPC? Reply to this verdict, or send evidence, ask for a correction or claim the listing. Every message gets a public ticket number; none of it changes a rank unless a public page or a signed statement supports it.