Report · May 17, 2026

State of Base RPC Providers — Q2 2026

Managed RPC for Base is a small, three-provider market when scoped to vendors with first-class Base documentation. This report normalizes free-tier shape, pricing model, network coverage, and supported API surface for Alchemy, QuickNode, and Infura so a buyer can compare them on the same fields rather than the marketing copy each vendor publishes.

Scope

Managed RPC providers documented for Base mainnet. Self-hosted nodes, Solana-only services, testnet-only services, and gateway aggregators were not evaluated. Pricing fields summarize the public tier shape as documented on each vendor site through May 2026 and are not negotiated rates.

Methodology details applicable across all Crypto.club reports are at /methodology/.

Key findings

1. Three vendors — Alchemy, QuickNode, and Infura — document first-class Base mainnet RPC support and all three publish a free tier.
2. Pricing model is the largest axis of comparison, not network coverage. Alchemy uses compute units, QuickNode uses flat-rate RPS or API credits, Infura uses request-based plans. Compare the model that matches the request mix you actually expect to send.
3. Network coverage overlaps heavily across Base, Ethereum, Polygon, Arbitrum, and Optimism for all three vendors. Differences appear at the edges: Alchemy and QuickNode list Solana; Infura lists Linea but not Solana.
4. None of the three provide user custody. All three operate as infrastructure providers; the API key holder is responsible for end-user safety in the calling application.
5. Public RPC endpoints (chainlist.org, sequencer URLs, and reference RPCs in main.net) are not interchangeable with the products in this report for production workloads. Treat them as developer convenience, not infrastructure.

Comparison matrix

Decision criteria

Pricing model fit

Calculate expected request mix (read-heavy vs. enhanced API vs. archive/debug) and price each vendor against that same workload. Free-tier ceilings rarely predict cost at production scale.

Enhanced API surface

If the app needs simulation, account abstraction, webhooks, or notifications, Alchemy and QuickNode both publish those products. Infura is RPC-and-keys-first; pair with separate tooling if you need richer APIs.

Existing tooling alignment

Teams already standardized on Consensys products (MetaMask SDK, Linea, Truffle deprecation paths) get integration value from Infura. Teams starting fresh have less reason to weight that.

Support and incident response

Production teams need to know the support SLA and incident-communication path before launch. All three vendors offer paid plans with named support; the free tiers do not.

Data export path

If the app may move providers later, prefer plain RPC endpoints over vendor-specific enhanced APIs. Vendor-specific APIs make migration harder than vendor-specific dashboards do.

Why these three

The Base ecosystem is young enough that "RPC provider with first-class Base documentation" is a smaller set than "RPC provider in general." Alchemy, QuickNode, and Infura each publish dedicated Base reference docs, ship Base in their managed-network selectors, and list Base in pricing tables. Vendors that support Base via a generic EVM template, without Base-specific docs, were not evaluated for this report — production buyers should not assume parity until a vendor commits to a documented support surface.

Pricing models compared

Alchemy bills in compute units: each method call has a unit cost and your plan caps total units per month. This matches workloads with steady, predictable request shapes. QuickNode publishes both a flat-rate RPS model and an API-credit model; the flat-rate model is preferred when your throughput is more predictable than your request mix. Infura publishes request-based plans with project-level keys and a daily request ceiling. A read-heavy app and an event-streaming app can pay very different totals at the same nominal request volume across these three; compare against your specific mix, not the headline.

Network coverage compared

All three vendors document Base, Ethereum, Polygon, Arbitrum, and Optimism. Alchemy and QuickNode both add Solana — relevant if the app spans EVM + Solana. Infura adds Linea (Consensys-operated L2) but not Solana. Network coverage alone rarely decides this category; teams pick by pricing fit and API surface, then verify their target networks are on the list.

Custody and operational posture

None of the three are user-custody products. They are infrastructure: the API caller owns key management, rate-limit handling, error budgets, and end-user wallet flows. A wallet provider in the catalog (MetaMask, Rabby, Safe) is the correct counterpart for custody questions. An RPC provider is the network access layer underneath that.

What this report does not answer

This report does not name a winner. It does not rank latency or uptime — those require measurement, not docs review. It does not evaluate provider behavior during chain incidents, sequencer outages, or major upgrades; that is incident-response work and belongs in a different artifact. And it does not cover token issuance, staking, or any user-facing crypto product. Crypto.club’s scope here is software selection, not capital allocation.

Limitations

• Only three vendors were evaluated. Ankr, Chainstack, NodeReal, BlockPI, and other regional or specialty RPC providers may also support Base; they were excluded because Crypto.club had not completed a documentation review for those vendors at time of writing.
• Pricing fields summarize public docs only. Negotiated enterprise rates, marketplace credits, and partner pricing are not reflected.
• Uptime, latency, and request-success-rate measurements are not part of this report. Those require continuous probing over a multi-week window and will appear in a separate report when the underlying data collection has run long enough to publish.
• Custody model is reported as the vendor documents it. Operational practices around key rotation, IP allowlists, and per-key rate limits are the API caller’s responsibility, not the vendor’s.

Sources

Each vendor row in the comparison matrix is supported by the vendor’s public documentation:

• Alchemy · Alchemy Base docs · Alchemy pricing docs
• QuickNode · QuickNode Base docs · QuickNode pricing · QuickNode flat rate RPS
• Infura · Infura infrastructure

Published May 17, 2026. Reports do not change after publication. If a vendor's public posture changes, a new report supersedes the old one and the old one stays available at its original URL.