Best Polygon RPC providers in 2026

Choose SolidRPC when historical state and debug_* matter and one provider should own routing, monitoring, failover, and recovery. Choose Blockmachine for standard-read-heavy traffic that benefits from lower published RU pricing or needs WebSocket. Use dRPC or another listed public endpoint for development and independent checks. Consider Alchemy or QuickNode when their wider platforms already fit your architecture.

Polygon's official RPC directory identifies chain ID 137, POL gas, dRPC as the default HTTP/WSS endpoint, and many public and paid providers. It is a directory, not a capability ranking, and warns that public RPCs may restrict traffic.

Build the shortlist from required outputs: wallet reads, subscriptions, log backfills, old eth_call, Bor methods, or debug_traceTransaction.

Polygon PoS has two clients. The official architecture overview describes Heimdall-v2 as consensus and Bor as execution/block production. Bor follows geth lineage; Heimdall-v2 uses Cosmos SDK and CometBFT.

Bor exposes eth_*, but node health depends on both clients. An operator must monitor their heads, peers, fork compatibility, Ethereum connectivity, storage, and recovery. A responsive Bor beside stalled consensus is not a healthy route.

“Archive” may mean old blocks, receipts/logs, historical state, or all three. debug_* also differs from Parity trace_*. Compare the oldest successful block for each required method, not an archive badge.

SolidRPC operates a Bor PBSS/PebbleDB archive with Heimdall-v2. The preferred path serves historical, standard, and supported geth-style debug_* calls. Dwellir is the external full-capacity fallback; do not assume deep history survives failover. Parity trace_* is unsupported end to end. See the Polygon archive guide for the retention boundary.

The application integrates once while SolidRPC owns upstream selection, routing, health, failover, monitoring, and recovery. Accountability does not mean capability equivalence: deep-history users should test preferred-path failure and plan for temporary archive reduction.

SolidRPC is HTTPS POST only, without WebSocket. The keyless https://rpc.solidrpc.io/public/evm/137 endpoint is for development/light traffic. Authenticated standard, archive, and debug calls share the response-unit model.

Blockmachine's Polygon page publishes keyless HTTP/WS, standard EVM, supported bor_*, filters, subscriptions, and geth-style debug methods. It is practical for wallets, frontends, bots, and low-cost head traffic.

Its history claim is narrower: deep historical and hash-indexed archive coverage is best-effort, and users should not assume every deep request works. That chain-specific qualification controls over the generic archive feature on its pricing page.

These are vendor claims reviewed August 31, 2026. Test an old balance, storage slot, contract call, receipt, log range, block-hash query, Bor extension, and exact debug tracer at your cutoff. A method count is not proof of the one depth and method you cannot lose.

For mostly 1-RU traffic, Blockmachine has the lower published price. Its plans are Standard $9/5 million RU, Pro $25/20 million, Business $125/100 million, and Enterprise $999/1 billion. The one-month promotion is excluded.

SolidRPC offers Free $0/10,000 units per UTC day, Builder $25/10 million monthly, Solid $349/150 million, and Rocksolid $999/600 million. Every billable call is one unit; debug_traceTransaction equals eth_blockNumber.

Blockmachine weights eth_getLogs at 3–25 RU, transaction/call debugging around 30 RU, and block tracing at 50 RU. One million 50-RU calls consumes 50 million Blockmachine RU versus one million SolidRPC units, so heavy traffic can reverse the comparison.

SolidRPC does not bill gateway rejects or upstream HTTP 5xx/timeouts, but bills node-reached JSON-RPC errors. Blockmachine says failed requests are free; ask how it categorizes those errors.

No. Stale guides recommend polygon-rpc.com or rpc-mainnet.polygon.technology, but Polygon retired its mainnet endpoints July 31, 2026; Amoy retired July 17. Today's “Polygon public RPC” means a listed third party, not Polygon-operated infrastructure.

The current directory defaults to dRPC and lists Tenderly, Allnodes, Tatum, Nodies, 1RPC, QuickNode, OnFinality, and others. They suit prototypes and independent checks, but keyless access proves neither capacity nor archive retention.

Alchemy or QuickNode fit teams already using their platforms; calculate their units from real Polygon methods. Chainstack may fit a managed dedicated-node path. Dwellir is another provider and SolidRPC's full-capacity fallback. Self-hosting maximizes control but adds Bor, Heimdall-v2, archive storage, upgrades, monitoring, and recovery. Compare that engineer load, not only servers.

Exercise Polygon-specific failures, not just eth_blockNumber:

1. Confirm eth_chainId is 0x89; compare latest block hash independently.
2. Test current and old balance, code, storage, and eth_call at documented blocks.
3. Query sparse/dense eth_getLogs, varying width and measuring bytes; include a state-sync log if relevant.
4. Run the exact debug_traceTransaction tracer on recent and old transactions; test Parity trace_* separately.
5. Call required bor_* methods.
6. Sustain expected concurrency through throttling, timeouts, and adaptive pagination.
7. Fail the preferred route and repeat old-state, log, and debug probes. Current-head continuity does not prove capability-preserving failover.
8. Calculate weighted units from methods, retries, batches, node errors, and overage.

Keep this as a synthetic check after client, pruning, or routing changes.

Test Blockmachine first for light standard traffic and WebSocket, while measuring its best-effort deep-history limit. Use SolidRPC for historical/debug-heavy HTTPS and one provider-owned route. Use dRPC or another listed public endpoint for development, and shortlist Alchemy, QuickNode, Chainstack, or Dwellir when their platform fit matters.

Choose from the oldest required state, log density, exact debug/Bor methods, transport, failover behavior, and weighted cost—not a generic request chart.