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.
A private Scroll RPC endpoint on single-tenant NVMe bare metal. Full or archive l2geth nodes speak standard Ethereum JSON-RPC over HTTPS and WebSocket, with zero rate limits and no compute units.
$ rs deploy scroll --type full --region fra
allocating single-tenant bare metal
restoring l2geth snapshot
connecting ethereum l1 rpc
starting rollup-node coordinator
attaching DDoS shield + IP allowlist
private endpoint live · https + wss
A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.
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.
A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.
Talk to the engineers who run the metal. l2geth and rollup-node config, snapshot strategy, and the Ethereum L1 dependency, handled by people who run Scroll nodes daily.
Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.
Settle in crypto or fiat, ETH and SCR included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.
Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.
Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.
For dApps, wallets, bots & indexers
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 Scroll documentation.
View official Scroll node docs →For deep history, tracing & compliance
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 Scroll documentation.
View official Scroll node docs →Thanks. A Web3 engineer will spec your private endpoint and reach out shortly.
Something went wrong. Please try again or email sales@redswitches.com.
Shared Scroll RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Scroll node is your own private backbone: flat-priced, uncapped, and yours alone.
The chain IDs, clients, transports, and JSON-RPC namespaces your dedicated Scroll node ships with. Built to a standard so your existing tooling connects with no changes.
You control which namespaces are exposed. Enable debug and trace on archive builds, keep the rest private behind IP allowlisting.
Where a private, uncapped endpoint beats a shared RPC pool.
Power lending, trading, or staking apps with dedicated Scroll nodes built for high transaction volumes. Reserved CPU, RAM, and NVMe keep reads and submissions steady through volatility, with predictable low-latency RPC.
Mints and trades trigger repeated contract calls, allowance checks, and bot retry storms. A dedicated node keeps reads steady and WebSockets reliable during spikes, so listings and reveal pipelines stay online when shared endpoints throttle.
Bridging between Ethereum and Scroll depends on accurate event tracking and confirmation monitoring. When RPC lags, watchers miss events and transfers stall. Dedicated infrastructure keeps monitoring consistent and speeds up reconciliation.
Scroll's zkEVM relies on rapid proof generation and verification. High-capacity bandwidth and dedicated I/O support data availability without competing for shared cache, fitting teams running provers, sequencer feeds, and analytics.
Quoting and execution break when shared endpoints throttle bursty eth_call traffic. Dedicated Scroll RPC nodes keep routers, aggregators, and liquidity engines responsive, so p95 latency stays stable and slippage stays minimal during busy blocks.
Indexers need steady RPC for eth_getLogs, receipts, and backfills across large ranges. Archive-ready storage supports deeper historical reads, so ETL pipelines do not stall mid-run, fitting analytics, alerting, and monitoring systems.
Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.
Choose full or archive, and bring or host the Ethereum L1 RPC your rollup-node depends on. Pick the region closest to your users.
Your single-tenant l2geth + rollup-node deploys on dedicated NVMe, bootstrapped from a current snapshot, so you skip the long replay.
Receive a dedicated HTTPS + WSS RPC URL with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.
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.
Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your Scroll node in the region your traffic actually comes from, not wherever a shared pool happens to route you.
RPC latency is mostly physical distance. Running in the same region as the Scroll 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.
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.
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.
Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.
Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
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.
Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
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.
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.
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.
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.
Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
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.
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.
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.
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.
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.
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 is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
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.
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).
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.
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.
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.
"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.
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!
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.
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.
We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
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.
Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.
A Scroll RPC node is the infrastructure your app calls for on-chain data and transactions on Scroll, a zkEVM Layer 2 for Ethereum. It serves JSON-RPC reads like balances, logs, receipts, gas estimates, and contract calls, and supports transaction submission. Scroll validates transactions off-chain and submits cryptographic proofs to Ethereum, so your RPC quality affects app load time, swap success, and event-driven features.
A full node fits most production apps. It serves current chain state and standard calls like eth_getLogs, eth_call, and receipts. An archive node retains deep historical state, which supports older-block eth_call, long backfills, and compliance analytics. If you are unsure, start with a full node and upgrade when query depth demands it.
Not in the staking sense. Scroll is a zkEVM rollup with a centralized sequencer, so there is no permissionless, stake-to-earn validator like Ethereum or Solana. Block production and proof submission are operated by the Scroll team, not open to public staking. What we provision is a fast, dedicated full or archive RPC node (l2geth + rollup-node), which is what apps, indexers, and protocols actually need.
Yes. Scroll is an L2 that derives its state from Ethereum, so your node requires a fully synced Ethereum L1 node to set up the Scroll L2 on top. If that parent-chain endpoint is slow or falls behind, your Scroll node can stall, which shows up as stale reads and delayed indexing. L1 endpoint quality is part of Scroll reliability, so plan it alongside your L2 node.
You can bring your own Ethereum endpoint, or run an Ethereum node on dedicated servers with us to control rate limits and reliability. If you host both with RedSwitches, you can place them in the same region for tighter latency, which helps catch-up speed and reduces sync stalls. We will scope the setup based on your traffic and query depth.
For demanding RPC operations we recommend a multi-core processor (16 cores or more, AMD EPYC preferred), a minimum of 64 GB RAM to manage Scroll node state, and 2 x 3.84 TB NVMe enterprise drives so a single drive failure does not take the node down. A minimum 10 Gbps uplink keeps transaction and block propagation efficient. Archive nodes need more RAM and storage headroom as history grows.
Scroll's RPC API follows the Ethereum JSON-RPC specification, so you can use most common eth_ and net_ methods from the broader Ethereum ecosystem: eth_blockNumber, eth_getBlockByNumber, eth_call, eth_getBalance, eth_getLogs, eth_getTransactionReceipt, net_peerCount, and more. On a dedicated node you control which modules and ports you expose, and we recommend keeping the endpoint private by default.
We deliver servers fast and provision from current snapshots, so a full node is typically live and serving in minutes to hours rather than syncing from scratch for days. Go-live depends on node mode, snapshot initialization, and catch-up to head. If you have a deadline, we plan around it and can launch multiple nodes across regions, with a fully managed option where our engineers handle sync, updates, and monitoring.
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.
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.
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.
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.
Official Scroll resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.
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.
Unmetered options in the Equinix Paris data center. 10 min delivery.