Polygon (POL)
Polygon PoS is served by Tessellate from Bor and Heimdall node pools, with blocks about every 2 seconds.
Polygon RPC is planned for launch in Q1 2027. Only Polygon PoS is in launch scope. It uses the same Envoy gateway, router, cache and plan limits as every other Tessellate chain.
Talk to Us About Polygon RPC
Block time
Availability target
Execution client
WebSocket subscriptions
Snapshot cadence
Head lag target
Reorg window
Debug and trace methods
*Targets are measured at our edge, per region, each month, and published on the status page. Contact our team to discuss committed capacity.
Why connect to Polygon with Tessellate?
-
Status: Launch, Q1 2027
-
Bor and Heimdall node pools behind one gateway
-
Blocks about every 2 seconds, with head lag targeted within two blocks
-
A cache keyed by block hash; latest is never cached beyond one block time
-
The same plans, limits and status page as every other chain
Explore insights from our engineers
Polygon RPC FAQ
Send JSON-RPC requests to https://polygon.rpc.thetessellatelabs.com with your API key. Endpoints need an API key created in the Tessellate dashboard.
Bor and Heimdall, in per-chain node pools.
Backend selection is health-weighted by head lag, error rate and latency.
Archive depth for Polygon will be published at launch.
The cache holds immutable data only, keyed by block hash. latest and pending are never cached beyond one block time. Head lag is targeted within two blocks of canonical for 99.9% of minutes. Finality guidance for Polygon will be published at launch.
No. Wallets are out of scope. Tessellate provides RPC access and never holds customer keys or assets.
eth_getLogs accepts a block range of 2,000 on Developer and Build, 10,000 on Scale, and a configurable range (default 50,000) on Dedicated and Enterprise.
10,000 logs on Developer and Build, 20,000 on Scale and 100,000 on Dedicated and Enterprise.
WebSocket subscriptions are available from the Build plan, at 10, 50 or 500 per API key depending on plan.
Limits apply per API key: 25 requests per second on Developer, 150 on Build and 800 on Scale. Archive reads are weighted 5x on Build and 3x on Scale. Dedicated plans are not metered.
JSON-RPC batches are 25 requests on Developer and Build, 100 on Scale and 500 on Dedicated and Enterprise. Responses are capped at 10 MB, 25 MB and 150 MB by plan.
The target is 99.9% availability on shared tiers, measured at our edge per region per month and published on status.thetessellatelabs.com, including the months we miss.
Not at launch. We route to a partner such as Flashbots Protect on request.
Questions about this chain? Contact [email protected].
Explore additional chains
Tessellate supports twelve EVM chains by month twelve. Learn how to connect.
Meet With Us
Bring reliable infrastructure to your organisation.
Tessellate respects your privacy. By submitting this form, you are acknowledging that you have read and agree to our Privacy Policy, which details how we collect and use your information.