Polygon RPC endpoints: free public URLs and private API-key providers by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Polygon RPC endpoint (probed every 60 seconds) and, under the Access selector (Private), against the API-key endpoints of Alchemy, Chainstack, GetBlock and QuickNode (every 120 seconds), from 3 regions. The two cohorts are ranked separately, never against each other.
TL;DR. As of , dRPC has the lowest median latency of the 2 free public Polygon RPC endpoints measured above the 50 % success floor (3 listed), 28 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/polygon-rpc. Chain ID 137. 3 public endpoints, no key: polygon.drpc.org, gateway.tenderly.co, polygon-bor-rpc.publicnode.com. Full URLs with their 24h median are listed below; Alchemy, Chainstack, GetBlock, QuickNode (private, API key) are ranked apart under the Private tab.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Polygon has no chain-official endpoint in the free tier, so this is the purest gateway-versus-gateway comparison in the cluster: 3 gateways (the endpoints table names them), all answering the same `eth_getBlockByNumber` probe every 60 seconds from three regions. With no house endpoint to anchor expectations, the regional flips between gateways decide the ranking, and they flip often.
Methodology
Polygon: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. dRPC leads at 28 ms. The same page carries the private cohort (API key), Alchemy, Chainstack, GetBlock and QuickNode on their keyed Polygon endpoints every 120 seconds: switch the Access selector; GetBlock leads it at 9 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Polygon endpoint that sustains continuous probing, 3 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Polygon-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Polygon RPC endpoints measured, 2 ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | dRPC | 28 ms | 44 ms | 155 ms | 99.98% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | Tenderly | 105 ms | 113 ms | 163 ms | 100.00% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Measured, not ranked: sample below the ranking floor | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| not ranked | PublicNode | 1.10 s | 4.65 s | 6.05 s | 43.07% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Public Polygon RPC endpoints measured
Chain ID 137, currency POL. The 3 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is listed last. Paste one into a wallet or a client as is: no signup, no key. Alchemy, Chainstack, GetBlock and QuickNode, private endpoints that need an API key, are ranked separately under the Private tab; keyed URLs are never listed.
dRPChttps://polygon.drpc.org28 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/polygon105 ms100.0%
PublicNodehttps://polygon-bor-rpc.publicnode.com1.10 s43.1% ▾
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Not listed on Polygon
- Ankr: public endpoint requires an API key
- NodeReal: requires an API key
- 1RPC: delisted for reliability: under 13 % success at one probe per minute (since 2026-07-09)
- gateway.fm: 29 requests per IP budget, too small for continuous probing
- LlamaRPC: Cloudflare 521 from the probe regions
- BlockPI: Cloudflare 521 from the probe regions
- OmniaTech: Cloudflare 521 from the probe regions
- Alchemy demo: rate-limited public demo endpoint; Alchemy's keyed endpoint is in the private cohort on this page
Frequently asked
Which Polygon RPCs work without an API key?
The 3 providers on this page are listed with their URLs in the endpoints table above. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Why is there no official Polygon RPC in this benchmark?
Polygon's historically documented public endpoint (`polygon-rpc.com`) is operated by a third party and has moved in and out of key-gating and rate-limit regimes that break our 60-second probe cadence. The bench includes only endpoints that sustain continuous no-key probing; the multi-chain gateways above all pass that bar on Polygon.
Which Polygon RPC provider is fastest with an API key?
Per the live data: GetBlock at 9 ms (eth_getBlockByNumber p50 over 24h, averaged across us-east, eu-west and Singapore); Alchemy measures 32 ms, Chainstack 101 ms and QuickNode 26 ms; GetBlock measures 9 ms. On the free cohort dRPC leads at 28 ms, measured on the same call from the same three regions; the two cohorts are never ranked in one table (shared gateways at 60 s against metered endpoints at 120 s). Switch the Access selector to Private for the region tabs and the p99 column; plan tiers are disclosed in the methodology.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities