Question 1

What is a dedicated node?

Accepted Answer

A dedicated node is a blockchain node running on a private server reserved exclusively for you. Unlike shared infrastructure, you get the full throughput of the hardware, no rate limits, no noisy neighbours, and the ability to configure the node client to your workload — custom RPC methods, non-default namespaces, specific peer settings, or bespoke builds.

Question 2

Shared vs dedicated — when should I move?

Accepted Answer

Move to dedicated when any of these are true: you hit the 200 RPS ceiling on shared nodes, you need archive data or tracing (debug_*, trace_*), latency matters to your product (trading, MEV, real-time UX), you need a specific geography, you run workloads that require custom client configuration, or compliance requires isolated infrastructure. Below those thresholds, shared nodes are usually the right call.

Question 3

How do I migrate from Alchemy / QuickNode / Infura?

Accepted Answer

Most migrations are endpoint swaps — we expose the same JSON-RPC interface, so changing the base URL in your config is usually all the application-level work required. Our team assists with: endpoint compatibility mapping, request-pattern analysis to size the node, side-by-side running during cutover, and zero-downtime switchover. Typical migration time is one to three days end-to-end.

Question 4

Can I run GetBlock alongside my current provider as a fallback?

Accepted Answer

Yes. Many teams use GetBlock as their primary with an existing provider as secondary, or vice versa. We help set up health-check-based failover on your side — nothing proprietary to learn.

Question 5

What does Premium Support actually include?

Accepted Answer

A dedicated account manager, a direct Telegram / Slack / WhatsApp channel to GetBlock Senior Engineers, architecture reviews, debugging assistance, and on-demand optimization work. Response SLA is under 5 minutes, any timezone. Teams typically use it to offload what would otherwise be a senior DevOps hire.

Question 6

What latency can I actually expect?

Accepted Answer

Latency depends on the chain, region, and client setup. On our flagship deployments: 7ms on Solana and under 30ms on BSC — both verified by independent benchmarks (CompareNodes.com). For EVM chains like Ethereum, Polygon, and Arbitrum, typical RPC response times are 20–60ms from the nearest region. We'll share per-chain benchmarks on request and can run a latency test from your endpoint before you commit.

Question 7

What does your 99.99% uptime SLA actually cover?

Accepted Answer

Uptime is measured as the percentage of time the node responds successfully to RPC probes, excluding scheduled maintenance (announced 72h in advance). If we miss the SLA, service credits apply automatically — no claims forms. Geo-redundant deployments and 24/7 monitoring back the number; we don't rely on best-effort language.

Question 8

How do you handle chain reorgs, missed blocks, and node desync?

Accepted Answer

Every dedicated node is monitored for block height, peer count, and sync state against canonical chain data. On desync, the node is automatically re-peered or rebuilt from a recent snapshot. Reorgs are handled natively by the client — we don't filter or re-emit events, so your application sees the same chain state a self-hosted node would.

Question 9

Can I burst above my provisioned throughput?

Accepted Answer

There is no provisioned cap — the node is yours. Throughput is bounded only by the hardware tier you choose. If your workload grows, we resize the host before you hit a ceiling, usually within the same billing cycle.

Question 10

What happens if something breaks at 3am?

Accepted Answer

Your direct engineer channel is 24/7. The monitoring that flagged the issue has usually already paged us before you notice — in most incidents, the first message in the channel is from our side, not yours.

Question 11

Can I enable custom or non-default RPC methods?

Accepted Answer

Yes — including debug_*, trace_*, custom namespaces, and client-specific methods (e.g. Erigon-only endpoints, Geth admin APIs). If the client supports it, we can expose it. We also build custom node software for teams with specific requirements — see the Blockaid case study above for an example of a custom build achieving sub-7ms latency.

Question 12

Do you support archive nodes and mainnet forks?

Accepted Answer

Yes. Full archive is available on 130+ chains with no per-call surcharge. Mainnet forks (and custom chain forks) can be provisioned for staging, simulation, or replay testing — typical setup time is 24 to 72 hours depending on chain size.

Question 13

Can I colocate my own software on the same host as the node?

Accepted Answer

Yes. Common use cases: trading bots, MEV searchers, signal processors, and latency-sensitive indexers. Co-location eliminates the network hop between your code and the node, which saves single-digit milliseconds that compound into real P&L on high-frequency workloads.

Question 14

Can you deploy in a specific region, or on-prem inside our data center?

Accepted Answer

Yes to both. We deploy in any standard cloud region and on request in non-standard locations. On-prem deployment inside your data center is supported for teams with data residency, latency, or compliance requirements — we manage the node stack, you control the hardware.

Question 15

Can I connect the node privately to my AWS / GCP / Azure environment?

Accepted Answer

Yes. We support private networking (VPC peering, PrivateLink-equivalents) to keep RPC traffic off the public internet. This is the default for enterprise deployments.

Question 16

How is a dedicated node priced?

Accepted Answer

Pricing depends on the chain, network (mainnet / testnet / archive), client, region, and commitment length. Use the calculator on this page for a real-time quote. Monthly and annual commitments unlock built-in discounts; longer commitments are negotiable.

Question 17

Do you charge per request?

Accepted Answer

No. Dedicated nodes are flat-rate — unlimited requests, unlimited RPS, no per-call billing. You pay for the hardware tier, not for usage.

Question 18

Can I pay in crypto? Do you offer contract-based billing?

Accepted Answer

Yes to both. Crypto and fiat are supported. Enterprise contracts with custom terms, invoicing, and procurement integration are standard for dedicated infrastructure.

Question 19

What compliance standards do you align with?

Accepted Answer

Dedicated infrastructure is built and operated to SOC 2 Type II standards. We also support IP allowlisting, custom access controls, private networking, and transaction anonymization for compliance-sensitive workloads. DPA and custom security reviews are available on request.

Question 20

Who has access to my node?

Accepted Answer

Access is limited to the GetBlock SRE team on a least-privilege basis, gated by MFA and audit logging. We do not read application data, and the node is never shared with another tenant.

DedicatedBlockchain Nodes

Node observability

Custom node builds

Scalable node infrastructure

Resource and cost tuning

Banks and fintechs

GetBlock engineering, embedded in your team

Our infrastructure behind real-world products

In-depth insights for modern Web3 development

GetBlock Integrates bloXroute BDN for Faster and Safer BSC Transaction Execution

Fastest BSC RPC: GetBlock Achieves Top Speed in the Americas

Custom Node Software: What GetBlock Built for Blockaid

Take infrastructure off your critical path

Dedicated
Blockchain Nodes