Unlimited RPS & Responses
One node, unlimited requests and responses. No compute units, no rate caps, no overage bills. A flat monthly price, run as hard as the hardware allows.
// dedicated polygon zkevm rpc node
Private Polygon zkEVM RPC Endpoints on a Dedicated Node
A private Polygon zkEVM RPC endpoint on single-tenant NVMe bare metal. Full or archive cdk-erigon nodes serving HTTPS and WebSocket JSON-RPC, with zero rate limits and no compute units.
- Private Endpoint, Zero Rate Limits
- No Compute Units, Unlimited Requests
- Full & Archive cdk-erigon Builds
- EVM JSON-RPC With zkevm_ Methods
- Dedicated 10 / 25 Gbps Network
- 20+ Global Tier III Locations
deploy.shlive
$ rs deploy polygon-zkevm --type full --region fra
allocating single-tenant bare metal
restoring cdk-erigon snapshot
connecting ethereum l1 rpc
syncing zkevm state from l1
attaching DDoS shield + IP allowlist
private endpoint live · https + wss
- UnlimitedRequests
- ZeroRate Limits
- 100%Isolation
// why redswitches
Why Teams Run Polygon zkEVM Nodes With RedSwitches
A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.
Dedicated Account Manager
A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.
Direct Engineering Access
Talk to the engineers who run the metal. cdk-erigon config on Polygon CDK, the Ethereum L1 RPC dependency, snapshot strategy, and zkevm_ namespace tuning, handled by people who run Polygon zkEVM nodes daily.
20+ Global Data Centers
Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.
Pay In Crypto
Settle in crypto or fiat. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.
Tailored Load Balancing
Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.
// request your endpoint
Configure Your Polygon zkEVM Node
Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.
1 Dedicated Node = Unlimited RequestsNo Compute Units$0 Overages, Guaranteed
Polygon zkEVM Full Node
For dApps, wallets, bots & backend APIs
- CPU
- 8–16 high-clock cores
- RAM
- 32–64 GB
- Storage
- 1–2 TB NVMe (grows with chain state)
- Network
- 10/25 Gbps uplink, metered or unmetered
- Stack
- cdk-erigon (Polygon CDK) + an Ethereum L1 JSON-RPC
Best for
- eth_call, eth_getLogs, receipts, and contract reads
- HTTPS JSON-RPC and WebSocket subscriptions
- Needs an Ethereum L1 endpoint (bring or host with us)
Included with every node
- Unlimited RPS, no rate limits
- HTTPS & WebSocket (WSS)
- 99.99% uptime SLA
- Multi-region endpoints
- Private networking + IP allowlisting
- 24/7 Web3 engineering support
From$199/moflat, no compute units
Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.
Node specs above are based on the official Polygon zkEVM documentation.
View official Polygon zkEVM node docs →Polygon zkEVM Archive Node
For indexers, analytics & deep tracing
- CPU
- 24+ high-clock cores (up to 128)
- RAM
- 128–256 GB
- Storage
- 4–8 TB NVMe (dual), grows continuously
- Network
- 10/25 Gbps uplink, unmetered available
- Stack
- cdk-erigon archive + an Ethereum L1 JSON-RPC
Best for
- Older-block eth_call and long-range backfills
- Forensics, audits, and deep historical reads
- Needs an Ethereum L1 endpoint for L1 reads & bridge verification
Included with every node
- Unlimited RPS, no rate limits
- HTTPS & WebSocket (WSS)
- 99.99% uptime SLA
- Multi-region endpoints
- Private networking + IP allowlisting
- 24/7 Web3 engineering support
From$199/moflat, no compute units
Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.
Node specs above are based on the official Polygon zkEVM documentation.
View official Polygon zkEVM node docs →Request Sent
Thanks. A Web3 engineer will spec your private endpoint and reach out shortly.
Something went wrong. Please try again or email sales@redswitches.com.
// why dedicated
Stop Fighting For Bandwidth On Shared Polygon zkEVM RPC
Shared Polygon zkEVM RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Polygon zkEVM node is your own private backbone: flat-priced, uncapped, and yours alone.
CapabilityShared RPC PoolRedSwitches Dedicated
Request limitsHard rate caps and compute-unit quotas throttle your Polygon zkEVM calls the moment traffic spikesZero rate limits, your Polygon zkEVM node serves unlimited requests up to what the hardware can push
ResourcesA noisy-neighbor pool where another tenant's mint or airdrop steals the throughput you paid for100% single-tenant CPU, RAM, and NVMe, reserved for your Polygon zkEVM workload alone
BillingPer-compute-unit metering with surprise overage bills at the end of the monthOne flat monthly price for the whole node, $0 overages and no usage math
NetworkShared, throttled bandwidth you can neither see nor controlA dedicated 10 / 25 Gbps port, metered or unmetered, that is yours alone
PrivacyA public, pooled endpoint with a wide, shared attack surfaceA private Polygon zkEVM endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Polygon zkEVM archive with custom RAM and disk, sized to your query depth
ControlNo server access, the provider picks the client, version, and configFull root, KVM, and IPMI, run the Polygon zkEVM client and tuning you choose
// network details
Polygon zkEVM Node Specifications
The chain IDs, clients, transports, and JSON-RPC namespaces your dedicated Polygon zkEVM node ships with. Built to a standard so your existing tooling connects with no changes.
Chain Parameters
- Networks
- Mainnet, Cardona Testnet
- Chain IDs
- Mainnet 1101 · Cardona 2442
- Native token
- ETH
- Stack
- zkEVM ZK rollup built with Polygon CDK, settles to Ethereum L1
- Execution
- EVM-equivalent
- Finality
- After ZK validity proof verified on Ethereum L1
- Transports
- HTTPS and WebSocket JSON-RPC
- Archive
- Full historical state (cdk-erigon archive)
- Dependency
- Requires an Ethereum L1 RPC endpoint
- Explorer
- zkevm.polygonscan.com
Supported Clients
Node client
- cdk-erigon (Polygon CDK)
JSON-RPC Namespaces
- eth_
- net_
- web3_
- debug_
- txpool_
- zkevm_
You control which namespaces are exposed. Enable debug and trace on archive builds, keep the rest private behind IP allowlisting.
// use cases
What Teams Build On Polygon zkEVM Nodes
Where a private, uncapped endpoint beats a shared RPC pool.
Production dApp Backends
User traffic is unforgiving. Your backend needs consistent reads and reliable transaction submission during launches and spikes. A dedicated Polygon zkEVM RPC node removes shared throttling and keeps your app responsive as usage climbs.
DeFi Execution Systems
Swaps, lending, and liquidation flows depend on fast state reads and accurate contract calls under volatility. A dedicated Polygon zkEVM node with headroom for heavy eth_call and log activity reduces timeouts and failed broadcasts.
Wallets And Payments
Wallet UX depends on fast balance reads, allowance checks, and dependable broadcasts. Your Polygon zkEVM RPC stays responsive at peak, and you can gate transaction submission so abuse never overwhelms write capacity.
Indexers And Analytics
Indexers and analytics pipelines pull logs, receipts, and events continuously. You need sustained throughput for backfills and long-range queries without random slowdowns, steady ingestion for dashboards, alerting, and reporting.
Bridges And Relayers
Bridges and relayers rely on event watching, confirmation tracking, and transaction relays. Stable log streaming and predictable reads keep deposit and withdrawal workflows from missing events during busy periods, improving cross-chain reliability.
Bots And Automation
Automation agents run frequent calls and time-sensitive execution. Stable responses during high activity keep arbitrage, liquidation bots, and operational jobs from stalling on noisy public infrastructure during critical windows.
// how it works
From Polygon zkEVM To Private Endpoint In 3 Steps
Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.
- 01
Pick Your Polygon zkEVM Node
Choose full or archive cdk-erigon, and bring or host the Ethereum L1 RPC your zkNode depends on. Pick the region closest to your users.
- 02
We Provision Bare Metal
Your single-tenant cdk-erigon node deploys on dedicated NVMe, bootstrapped from a current snapshot and syncing zkEVM state from L1, so you skip the long replay.
- 03
Get Your Private Endpoint
Receive a dedicated HTTPS + WSS JSON-RPC endpoint with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.
// latency & locations
Put Your Node Where Milliseconds Are Won
RPC latency is mostly a function of distance. A dedicated node lets you choose the exact region, so you sit next to the traffic that matters instead of fighting for routing on a shared, far-away endpoint.
Place It Where Your Users Are
Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your Polygon zkEVM node in the region your traffic actually comes from, not wherever a shared pool happens to route you.
Cut The Round Trips
RPC latency is mostly physical distance. Running in the same region as the Polygon zkEVM sequencer shaves the round-trips a far-away, shared endpoint can never give back, which is what high-frequency reads and transaction submission live or die on.
Multi-Region By Design
Run a primary node plus regional read replicas for fast reads everywhere and built-in redundancy. Split public read endpoints from private admin, debug, and trace endpoints.
Need a node within a target latency budget of a specific region or venue? Tell us the endpoint and we'll recommend the closest facility.
// supported chains
One Backbone For Every Major Chain
Run validators, RPC, and archive nodes across the chains your stack depends on, all on the same dedicated bare metal, with the same isolation, speed, and control.
Ethereum
Solana
Polygon PoS
BNB Chain
Avalanche
Cardano
Cosmos
NEAR
Sui
Aptos
TRON
Polkadot
Kusama
Algorand
Tezos
TON
Fantom
XRP Ledger
Hedera
0G
Berachain
Celestia
Flare
Flow
Gnosis Chain
Hyperliquid
Injective
Japan Open Chain
Kaia
Monad
Nomina
Osmosis
peaq
Plasma
Ronin
Sahara AI
Sei
Sonic
Stellar
Story
Vana
Cronos
ZetaChain
XDC Network
PulseChain
Filecoin
IoTeX
Chiliz
Viction
Tempo
Stable
SORA
Waves
Moonbeam
Moonriver
Moonbase Alpha
Astar
Shiden
Aleph Zero EVM
Darwinia
Manta Atlantic
Acala
Karura
Bifrost
Hydration
Basilisk
Centrifuge
Interlay
Phala
Aleph Zero
Bittensor
Enjin
Nodle
Frequency
Humanode
Crust Network
Robonomics
Integritee
NeuroWeb
Tangle
Mythos
Pendulum
Amplitude
Aventus
Acurast
Energy Web X
Heima
Krest
Liberland
BalanceAI
Zeitgeist
xx network
Hyperbridge
Polkadot Asset Hub
Polkadot Bridge Hub
Polkadot Collectives
Polkadot Coretime
Kusama People
Polkadot People
Westend People
Paseo
Arbitrum
Base
Optimism
Polygon zkEVM
Linea
Scroll
zkSync Era
Starknet
Abstract
Arbitrum Nova
B3
Blast
Celo
Cyber
Fluent
Fraxtal
Fuel
Gravity
Hemi
Immutable zkEVM
Ink
Lens
Lisk
Mantle
Mode
Morph
Movement
Soneium
Sophon
Stacks
Taiko
Unichain
World Chain
Xai
Zora
opBNB
Manta Pacific
Boba Network
MegaETH
Bitcoin
Dogecoin
Litecoin
// customer reviews
Trusted To Run Production Nodes
Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.
- 25Gbps Bare Metal
Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
- VPN Operations
Network has been rock solid. They’ve got Tier 1 carriers like Arelion, GTT, and TATA… We just ping them on Telegram and they sort things out quickly.
- Validators
Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
- Full Root Access
As a sysadmin, I care more about control than flashy dashboards. RedSwitches gives me root access, IPMI, and actual hardware specs I can configure. Good for serious users.
- Enterprise Uptime
We were searching for a truly reliable and stable hosting provider with maximum uptime and a powerful network infrastructure to ensure the lowest possible latency. RedSwitches not only met but exceeded our expectations.
- Cloud Exit
RedSwitches gave us full control over our infrastructure without the vendor lock-in we kept running into with cloud hosts. Customizable builds, fast provisioning, and actual humans handling support tickets. It’s refreshing.
- 99.99% Uptime
My website works smoothly, thanks to their 99.99% uptime guarantee. The support team is another plus for me, as I always have been able to get help whenever I needed it in just 5 minutes on average.
- ETH & BTC Nodes
Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
- 10Gbps RPC
They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
- Streaming
I am using their 10gbps streaming server for last 6 months and I have no complaints. Extremely quick live chat support and I love that they accept crypto.
- Bare Metal
A really great hosting provider - what stands out the most is the stability of the network connection and the wide selection of bare metal servers. We’re very satisfied, and RedSwitches covers all of our needs.
- AI Workloads
Pros: Extremely reliable hardware, low-latency network, transparent billing… Great choice if you need raw power without cloud complexity. Works well for our dev environment and some AI workloads.
- Switched Provider
I have worked with OVH and Contabo in the past, but RedSwitches hit a better balance of price vs. support. Not the cheapest, but I get better performance and faster help.
- Game Servers
Been using RedSwitches for 6 months now for my small game server biz. Uptime has been great, and I haven’t run into any hidden charges.
- AI Storage
Using the storage servers to archive logs and snapshots from our AI pipeline… I also love that I could pick the datacenter closest to our team.
- Support
Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
- Instant Delivery
They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
- Fast Provisioning
A dedicated server has been installed within 30 minutes. Thirty minutes. It takes DAYS for some famous providers out there, but these guys do their work right.
- 5+ Years
I have been using their services for over 5+ years… Uptime: 10/10, Network: 10/10, Hardware Quality: 10/10, Customer Support: 20/10 (No, That’s Not A Typo).
- 1 to 14 Servers
They offer top quality hardware, excellent uptime and very responsive support… They helped us scale our business exponentially and we went from 1 server to 14 dedicated servers in less than a year.
- Reliability
Great hardware, non congested network and excellent service. Already using them for over a year and would definitely recommend Redswitches if you are looking for a reliable hosting provider.
- Global Locations
With servers available in numerous strategic locations, RedSwitches offers exceptional versatility and performance for our company’s diverse hosting needs. Plus, their no setup fee policy really helps keep costs down.
- Exam Platform
"Your server is ready" - I read this message within 30 mins of starting the chat with their Sales Team… Excellent DELL Hardware and 100% Uptime.
- Bare Metal Cloud
The dedicated server I got from RedSwitches has been incredibly reliable and fast. Their bare metal cloud solutions offer excellent performance, and the cloud VPS options are perfect for scaling. Highly recommended!
- Zero Downtime
I have been using their dedicated server from 9 months now. Starting from pre-sales till today I have not experienced downtime or lack of support.
- 24/7 Support
First of all, all services work as expected - secondly - support is outstanding, no matter when you start the conversation with colleagues at support they have knowledge to help you out.
- Since 2021
We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
- Easy Onboarding
Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
- Bare Metal
Very good experience using their bare metal servers. Their customer service is one of the finest I have experienced - always prompt at resolving troubles. Highly recommend.
// faqs
Frequently Asked Questions
Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.
What is a dedicated Polygon zkEVM RPC node and when do you need one instead of shared RPC?
A dedicated Polygon zkEVM RPC node runs on single-tenant hardware that serves only your workloads. You stop competing with other tenants for CPU, RAM, storage IOPS, and request budgets. Choose it when you see throttling, unpredictable latency, WebSocket drops, or failed broadcasts on shared endpoints. It also fits teams that want stricter access control, predictable scaling, and infrastructure ownership from a Polygon zkEVM RPC node provider.
Can I run a Polygon zkEVM validator node?
Not in the staking sense. Polygon zkEVM is a ZK rollup with a centralized sequencer, so there is no permissionless, stake-to-earn validator like Ethereum or Solana. Sequencing and proving are operated by the protocol, not by independent stakers earning yield. What we provision is a fast, dedicated full or archive zkNode RPC endpoint, which is what dApps, indexers, and bridges actually need. Protocol-level responsibilities such as keys and governance stay with you, while we provide the single-tenant hardware and networking.
Do I need Ethereum L1 access to run a Polygon zkEVM RPC node?
Yes. A Polygon zkEVM zkNode derives and verifies state against Ethereum, so it needs an Ethereum L1 JSON-RPC endpoint for L1 contract reads and bridge verification used by zkEVM workflows. If that parent-chain endpoint is slow or rate-limited, your node can fall behind, which shows up as stale reads and delayed indexing. L1 endpoint quality is part of Polygon zkEVM reliability, so plan for a dependable Ethereum RPC alongside your node.
Which networks do you support: Polygon zkEVM mainnet and Cardona testnet?
We deploy Polygon zkEVM RPC for mainnet. We can also deploy Cardona testnet for staging and QA on request. Many teams run both so they can test contract calls, events, and wallet flows before production. If your product needs a separate environment for release testing, a second Polygon zkEVM RPC node server keeps staging realistic without risking production stability.
How do you connect over HTTPS and WebSocket, and what endpoints do you provide?
You get an HTTPS endpoint for standard JSON-RPC requests and a WebSocket endpoint for subscriptions. Most teams point MetaMask, ethers.js, web3.js, Hardhat, or Foundry directly at the Polygon zkEVM RPC node endpoints. If you want clean traffic separation, you can run multiple endpoints and route them through your own gateway rules to keep reads and writes apart.
Do you support standard Ethereum JSON-RPC methods, and are any zkevm_ methods available?
Yes. A Polygon zkEVM RPC node is EVM-compatible, so you can use standard Ethereum JSON-RPC methods for reads, contract calls, logs, receipts, and transaction submission. Builds also expose chain-specific zkevm_ namespace methods, such as zkevm_consolidatedBlockNumber and zkevm_isBlockVirtualized, depending on the client version you run. If your stack depends on a specific call set, we validate method support during setup so your integrations behave as expected.
Can you separate endpoints into public read RPC and restricted write RPC?
Yes, and you should. A common production pattern is a public read endpoint for your app and a restricted write endpoint for transaction submission. You can lock down the write path with firewall rules, IP allowlists, and your own auth layer. This keeps your Polygon zkEVM RPC node server usable for real users while reducing abuse risk on broadcasts.
How long does initial sync usually take, and do you offer sync-aware provisioning?
Sync time depends on network conditions, node type (full or archive), and hardware, and it can range from hours to days as chain data grows. We provision the server fast, then your node syncs based on chain state and resources. We also support deploy-according-to-sync-time workflows, so your go-live timing stays realistic. Many teams start syncing early, validate endpoints, then cut over once the node is fully caught up.
Do you charge per request or per compute unit?
No. Unlike shared RPC providers that bill per "compute unit" and throttle you past a quota, a dedicated node is a flat monthly price with unlimited requests and zero overages. One node equals all the throughput your hardware can serve. That makes budgeting predictable and removes the surprise bills that come with usage-based RPC pricing.
How is this different from a shared RPC endpoint?
Shared RPC pools serve thousands of customers from pooled infrastructure, so you inherit rate limits, noisy-neighbor latency, and compute-unit billing. A RedSwitches node runs on single-tenant bare metal that is yours alone: reserved CPU, RAM, and NVMe, a dedicated 10/25 Gbps port, and a private endpoint you control. Performance tracks your hardware, not another tenant's traffic.
Do I have to sync the node myself, or wait days for it?
No. We provision from current snapshots so your node is live in hours rather than syncing from genesis for days. You can run it yourself with full root access, or choose our fully managed option where our engineers handle the sync, updates, and monitoring. Either way you receive a working private endpoint, not an empty server.
Can I deploy close to a specific region or sequencer?
Yes. With 20+ Tier III locations across the US, EU, Asia, and Australia you can place your node in the same region as your users or a chain's sequencer to cut round-trip latency. Tell us your target region and we will recommend the closest facility. You can also run multi-region nodes for redundancy and split read and write endpoints.
// developer resources
Polygon zkEVM Developer Resources
Official Polygon zkEVM resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.
// launch your node
Launch Your Private Polygon zkEVM Node
From $199/mo flat, sized to your chain's node specs and typically 30-40% below other providers. Snapshot-ready provisioning, zero setup fees, 24/7 Web3 engineers, no compute units, no rate limits.